linux-kernel - Re: [PATCH RFC] kvm: enable irq injection from interrupt context

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Sep 2010 11:25:53 +0200
From:	Gleb Natapov <gleb@...hat.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	Avi Kivity <avi@...hat.com>, Marcelo Tosatti <mtosatti@...hat.com>,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] kvm: enable irq injection from interrupt context

On Thu, Sep 16, 2010 at 11:10:55AM +0200, Michael S. Tsirkin wrote:
> On Thu, Sep 16, 2010 at 11:02:56AM +0200, Gleb Natapov wrote:
> > On Wed, Sep 15, 2010 at 08:54:17PM +0200, Michael S. Tsirkin wrote:
> > > To avoid bouncing irqfd injection out to workqueue context,
> > > we must support injecting irqs from local interrupt
> > > context. Doing this seems to only require disabling
> > > irqs locally.
> > > 
> > > RFC, completely untested, x86 only.
> > > 
> > > Thoughts?
> > > 
> > We do not want to disable irqs for a long time and some of code paths
> > under lock involve looping over all cpus. For MSI injection path is
> > lockless and this is the only case that matters,
> 
> MSI only appeared in rhel6, older guests still use level interrupts.
So they are already slow for other reasons.

> Which paths require looping over all cpus? Do PCI interrupts
> need this?
> 
All interrupts need it. IOAPIC has a loop to find dst cpu for interrupt.
Pic has a loop to find cpu in virtual wire mode.

--
			Gleb.
--
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/