linux-kernel - Re: [PATCH 0/5] Important fixes for KVM-AMD

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: <4BE28304.9090005@redhat.com>
Date:	Thu, 06 May 2010 11:51:16 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joerg.roedel@....com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Important fixes for KVM-AMD

On 05/05/2010 05:04 PM, Joerg Roedel wrote:
> Hi Avi, Marcelo,
>
> here is a set of patches which fix problems in kvm-amd. Patch 1 fixes a
> stupid problem with the event-reinjection introduced by me in my
> previous patchset.  Patch 2 was a helper to find the bug patch 3 fixes.
> I kept it in the patchset because it may be helpful in the future to
> debug other problems too. Patch 3 is the most important fix because it
> makes kvm-amd on 32 bit hosts work again.  Without this patch the first
> vmrum fails with exit-reason VMEXIT_INVALID. Patch 4 fixes the Xen 4.0
> shipped with SLES11 in nested svm. The last patch in this series fixes a
> potential l2-guest breakout scenario because it may be possible for the
> l2-guest to issue hypercalls directly to the host if the l1-hypervisor
> does not intercept VMMCALL.
>    

All applied, thanks.

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