linux-kernel - Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly

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]

Message-ID: <45641422.5090601@goop.org>
Date:	Wed, 22 Nov 2006 01:10:58 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Avi Kivity <avi@...ranet.com>
CC:	"H. Peter Anvin" <hpa@...or.com>, Arnd Bergmann <arnd@...db.de>,
	kvm-devel@...ts.sourceforge.net, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [PATCH] KVM: Avoid using vmx instruction directly

Avi Kivity wrote:
> Very interesting.
>
> Will it work on load/store architectures?  Since all memory access is
> through a register, won't the constraint generate a useless register
> load (and a use of the variable)?

Don't know; interesting question.  It might be worth lobbying the gcc
folks for an asm() constraint which means "pretend this is being
read/written, but don't generate any code, and raise an error if the asm
actually tries to use it".  Or perhaps there's some way to do that already.

On the other hand, load/store archs tend to have lots of registers
anyway, so maybe it isn't a big deal.

    J

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