linux-kernel - Re: [PATCH 0/3, v2] x86: xor-block handling adjustments

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: <5102DD08.9080204@zytor.com>
Date:	Fri, 25 Jan 2013 11:29:12 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jan Beulich <JBeulich@...e.com>
CC:	mingo@...e.hu, Ingo Molnar <mingo@...nel.org>, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3, v2] x86: xor-block handling adjustments

On 01/25/2013 12:21 AM, Jan Beulich wrote:
>>
>> I don't see anything wrong, except that I can't *find* patch 3/3 either
>> in my inbox nor on LKML...
> 
> I can certainly resend the whole set, but our email system even
> got a delivery confirmation from yours on patch 3 (other than
> e.g. from Ingo's, and all of this identical to 0...2).
> 
> Or see https://patchwork.kernel.org/patch/1688991/, according
> to which you even responded to it (which is the concern Ingo was
> referring to).
> 

Ah yes, now I have the context.

And with that, I have to NAK the patch.  I did talk to the KVM people
and they confirmed that this is NOT something they want.  They do not
program VT-x to VMEXIT on CR0 changes.

So this is Xen-specific, and penalizing other hypervisors is wrong.

	-hpa


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