| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20120816170100.GC22518@redhat.com> Date: Thu, 16 Aug 2012 20:01:00 +0300 From: "Michael S. Tsirkin" <mst@...hat.com> To: Avi Kivity <avi@...hat.com> Cc: Alex Williamson <alex.williamson@...hat.com>, gleb@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v8 0/6] kvm: level irqfd support On Thu, Aug 16, 2012 at 07:54:04PM +0300, Avi Kivity wrote: > On 08/16/2012 07:54 PM, Michael S. Tsirkin wrote: > > On Thu, Aug 16, 2012 at 07:39:35PM +0300, Avi Kivity wrote: > >> On 08/16/2012 07:36 PM, Michael S. Tsirkin wrote: > >> > >> >> What if a level irqfd shares a line with a KVM_IRQ_LINE ioctl? Then an > >> >> EOI can de-assert the irqfd source, but the line is kept high by the > >> >> last KVM_IRQ_LINE invocation. > >> > > >> > Exactly. So 1 ID for userspace and 1 for irqfd. > >> > >> Gaa, this mess belongs in userspace. > > > > Not sure I understand what you refer to. > > > > I meant simply > > #define KVM_IRQFD_IRQ_SOURCE_ID 1 > > request it at kvm init. > > > > As opposed to using KVM_USERSPACE_IRQ_SOURCE_ID like we do now > > for edge. > > Does this seem acceptable to you? > > I meant the pic/ioapic, not this particular bit. :) > > -- > error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists