Re: [kvm-devel] [RFC] Deferred interrupt handling.

> IMO the only reasonable solution is to disallow interrupt forwarding
> with shared irqs.  If someone later comes up with a bright idea, we can

Which means you are back to ISA bus devices. Even checking if an IRQ is
currently unshared isn't simple as with hotplug this may change.

> implement it.  Otherwise the problem will solve itself with hardware
> moving to msi.

Only if MSI ever works properly on the bridges and hardware 8(
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [kvm-devel] [RFC] Deferred interrupt handling.
    • From: Avi Kivity <[email protected]>

• References:
  • [RFC] Deferred interrupt handling.
    • From: "Or Sagi" <[email protected]>
  • Re: [RFC] Deferred interrupt handling.
    • From: Alan Cox <[email protected]>
  • RE: [kvm-devel] [RFC] Deferred interrupt handling.
    • From: "Dor Laor" <[email protected]>
  • Re: [kvm-devel] [RFC] Deferred interrupt handling.
    • From: Alan Cox <[email protected]>
  • Re: [kvm-devel] [RFC] Deferred interrupt handling.
    • From: Avi Kivity <[email protected]>

• Prev by Date: Re: [PATCH] sysfs: kill an extra put in sysfs_create_link() failure path
• Next by Date: RE: [kvm-devel] [RFC] Deferred interrupt handling.
• Previous by thread: Re: [kvm-devel] [RFC] Deferred interrupt handling.
• Next by thread: Re: [kvm-devel] [RFC] Deferred interrupt handling.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]