From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>,
Ingo Molnar <mingo@elte.hu>, Dor Laor <dor.laor@qumranet.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Refactor hypercall infrastructure
Date: Fri, 14 Sep 2007 13:53:26 -0700 [thread overview]
Message-ID: <46EAF4C6.8090903@goop.org> (raw)
In-Reply-To: <11897991353793-git-send-email-aliguori@us.ibm.com>
Anthony Liguori wrote:
> This patch refactors the current hypercall infrastructure to better support live
> migration and SMP. It eliminates the hypercall page by trapping the UD
> exception that would occur if you used the wrong hypercall instruction for the
> underlying architecture and replacing it with the right one lazily.
>
I guess it would be pretty rude/unlikely for these opcodes to get reused
in other implementations... But couldn't you make the page trap
instead, rather than relying on an instruction fault?
> It also introduces the infrastructure to probe for hypercall available via
> CPUID leaves 0x40000002. CPUID leaf 0x40000003 should be filled out by
> userspace.
>
Is this compatible with Xen's (and other's) use of cpuid? That is,
0x40000000 returns a hypervisor-specific signature in e[bcd]x, and eax
has the max hypervisor leaf.
J
next prev parent reply other threads:[~2007-09-14 20:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 19:45 [PATCH] Refactor hypercall infrastructure Anthony Liguori
2007-09-14 20:53 ` Jeremy Fitzhardinge [this message]
2007-09-14 21:02 ` [kvm-devel] " Anthony Liguori
2007-09-14 21:20 ` Zachary Amsden
2007-09-14 21:44 ` Anthony Liguori
2007-09-15 3:37 ` Zachary Amsden
2007-09-15 8:08 ` Avi Kivity
2007-09-15 17:33 ` Anthony Liguori
2007-09-14 21:22 ` Jeremy Fitzhardinge
2007-09-14 21:46 ` Anthony Liguori
2007-09-14 21:52 ` Jeremy Fitzhardinge
2007-09-14 22:08 ` Anthony Liguori
2007-09-14 22:40 ` Nakajima, Jun
2007-09-14 23:00 ` Jeremy Fitzhardinge
2007-09-15 0:10 ` Nakajima, Jun
2007-09-15 0:28 ` Jeremy Fitzhardinge
2007-09-15 1:04 ` Nakajima, Jun
2007-09-15 4:53 ` Jeremy Fitzhardinge
2007-09-15 6:11 ` Nakajima, Jun
2007-09-15 18:23 ` Anthony Liguori
2007-09-17 18:14 ` Nakajima, Jun
2007-09-17 18:27 ` Anthony Liguori
2007-09-17 19:15 ` Jeremy Fitzhardinge
2007-09-17 19:33 ` Anthony Liguori
2007-09-17 19:15 ` Jeremy Fitzhardinge
2007-09-17 20:52 ` Nakajima, Jun
2007-09-15 8:00 ` Avi Kivity
2007-09-15 7:53 ` Avi Kivity
2007-09-15 2:35 ` Rusty Russell
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=46EAF4C6.8090903@goop.org \
--to=jeremy@goop.org \
--cc=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).