linux-kernel - Re: [PATCH] kvm: only allow one gsi per fd

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20100120115911.GA9761@redhat.com>
Date:	Wed, 20 Jan 2010 13:59:11 +0200
From:	"Michael S. Tsirkin" <mst@...hat.com>
To:	Avi Kivity <avi@...hat.com>
Cc:	Marcelo Tosatti <mtosatti@...hat.com>,
	Gregory Haskins <ghaskins@...ell.com>,
	Gleb Natapov <gleb@...hat.com>, Julia Lawall <julia@...u.dk>,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kvm: only allow one gsi per fd

On Wed, Jan 20, 2010 at 01:52:00PM +0200, Avi Kivity wrote:
> On 01/20/2010 01:36 PM, Michael S. Tsirkin wrote:
>> On Sun, Jan 17, 2010 at 02:40:13PM +0200, Avi Kivity wrote:
>>    
>>> On 01/13/2010 06:58 PM, Michael S. Tsirkin wrote:
>>>      
>>>> Looks like repeatedly binding same fd to multiple gsi's with irqfd can
>>>> use up a ton of kernel memory for irqfd structures.
>>>>
>>>> A simple fix is to allow each fd to only trigger one gsi: triggering a
>>>> srorm of interrupts in guest is likely useless anyway, and we can do it
>>>> by binding a single gsi to many interrupts if we really want to.
>>>>
>>>>        
>>> Applied and queued, thanks.
>>>      
>> I'm guessing we need this for 2.6.32 stable and 2.6.33 as well?
>>    
>
> That's what 'queued' means.

Aha. Which git branch is used for these?

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