From: Jeremy Fitzhardinge <jeremy-TSDbQ3PG+2Y@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
akpm-3NddpPZAyC0@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] KVM: Avoid using vmx instruction directly
Date: Wed, 22 Nov 2006 01:10:58 -0800 [thread overview]
Message-ID: <45641422.5090601@goop.org> (raw)
In-Reply-To: <4563F158.3060209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-11-22 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 11:08 [PATCH] KVM: Avoid using vmx instruction directly Avi Kivity
2006-11-09 13:29 ` Arnd Bergmann
[not found] ` <200611091429.42040.arnd-r2nGTMty4D4@public.gmane.org>
2006-11-09 13:36 ` Avi Kivity
[not found] ` <45532EE3.4000104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-09 14:42 ` Arnd Bergmann
2006-11-09 14:52 ` [kvm-devel] " Avi Kivity
2006-11-09 16:37 ` Arnd Bergmann
2006-11-09 16:51 ` Avi Kivity
2006-11-09 23:39 ` Jeremy Fitzhardinge
2006-11-10 12:46 ` Martin Schwidefsky
[not found] ` <6e0cfd1d0611100446j77a27b29jc23f76a515451377-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-11-10 19:38 ` Jeremy Fitzhardinge
[not found] ` <4553BC18.6090207-TSDbQ3PG+2Y@public.gmane.org>
2006-11-21 18:35 ` H. Peter Anvin
[not found] ` <45634704.8020407-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2006-11-21 19:41 ` Avi Kivity
2006-11-21 20:50 ` Jeremy Fitzhardinge
[not found] ` <4563667B.2060209-TSDbQ3PG+2Y@public.gmane.org>
2006-11-22 6:42 ` Avi Kivity
[not found] ` <4563F158.3060209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-22 9:10 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45641422.5090601@goop.org \
--to=jeremy-tsdbq3pg+2y@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox