linux-kernel - Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33

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]

Message-ID: <4B3115C1.4070303@redhat.com>
Date:	Tue, 22 Dec 2009 20:53:53 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Gregory Haskins <gregory.haskins@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, kvm@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org,
	"alacrityvm-devel@...ts.sourceforge.net" 
	<alacrityvm-devel@...ts.sourceforge.net>
Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33

On 12/22/2009 07:36 PM, Gregory Haskins wrote:
>
>> Gregory, it would be nice if you worked _much_ harder with the KVM folks
>> before giving up.
>>      
> I think the 5+ months that I politely tried to convince the KVM folks
> that this was a good idea was pretty generous of my employer.  The KVM
> maintainers have ultimately made it clear they are not interested in
> directly supporting this concept (which is their prerogative), but are
> perhaps willing to support the peripheral logic needed to allow it to
> easily interface with KVM.  I can accept that, and thus AlacrityVM was born.
>    

Review pointed out locking issues with xinterface which I have not seen 
addressed.  I asked why the irqfd/ioeventfd mechanisms are insufficient, 
and you did not reply.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

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