linux-kernel - Re: [PATCH 0/11] Another set of nested svm fixes and optimizations

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] [day] [month] [year] [list]

Date:	Thu, 25 Feb 2010 12:32:37 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joerg.roedel@....com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>,
	Alexander Graf <agraf@...e.de>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/11] Another set of nested svm fixes and optimizations

On 02/24/2010 07:59 PM, Joerg Roedel wrote:
> Hi,
>
> here is another set of patches I collected in the last days while trying
> to get Hyper-V running with nested svm. I was not successful yet but the
> patches in this set make sense anyway :-)
> The patches fix coding style issues which annoyed me for some time
> because my vim shows all c-space-errors with red color. Other patches in
> this set make nested svm more complete (nmi and selective cr0 related).
> The vm_cr and hwcr.ignne patches are related to Hyper-V tests. This
> hypervisor expects to write to those msrs.
> The most interesting thing is patch 11 which reduces the amount of
> memory which is touched in the vmrun emulation for merging the msrpms
> from 24kb to 48 bytes.  Please review and comment (or apply if
> perfect ;-) ) these patches.
>    

1-10 applied.  11 had about 32 suggestions for improvement, please pick 
one and resubmit.

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