From: "H. Peter Anvin" <hpa@zytor.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: New CPUID/MSR driver; virtualization hooks
Date: Thu, 05 Apr 2007 11:03:11 -0700 [thread overview]
Message-ID: <461539DF.6010502@zytor.com> (raw)
In-Reply-To: <4614867C.4060506@vmware.com>
Zachary Amsden wrote:
> H. Peter Anvin wrote:
>> http://www.kernel.org/pub/linux/kernel/people/hpa/new-cpuid-msr.patch
>
> The requested URL /pub/linux/kernel/people/hpa/new-cpuid-msr.patch
was > not found on this server.
Fixed.
>> It's not *quite* that easy. The assembly code around this is pretty
>> extensive, because it has to stand on its head in order to present the
>> proper register image.
>
> Having just stood on my head for 55 breaths, might I suggest we
> implement a binary equivalent CPUID paravirt-ops wrapper; then the
> assembly code can just call CPUID and we can redefine it to call to a
> stub, which makes the pv-ops CPUID call, the puts the outputs back in
> the proper registers.
>
> The VMI ROM CPUID is binary identical in register format with the native
> instruction, so it need not do a headstand. For the others,
>
[snip]
This code is almost entirely identical to the setgpr_wrapper in the
patch (except for the fact that setgpr_wrapper sets and captures *ALL*
the GPRs), and it seems rather pointless to use another wrapper. It
takes a pointer to an entrypoint (default to "cpuid; ret" in the CPUID
case), so it should do what you need.
-hpa
next prev parent reply other threads:[~2007-04-05 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 0:50 New CPUID/MSR driver; virtualization hooks H. Peter Anvin
2007-04-05 1:16 ` Chris Wright
2007-04-05 1:23 ` H. Peter Anvin
2007-04-05 5:17 ` Zachary Amsden
2007-04-05 18:03 ` H. Peter Anvin [this message]
2007-04-05 21:09 ` Zachary Amsden
2007-04-05 21:09 ` H. Peter Anvin
2007-04-05 21:25 ` Zachary Amsden
2007-04-05 21:17 ` H. Peter Anvin
2007-04-05 21:27 ` Zachary Amsden
2007-04-05 21:40 ` H. Peter Anvin
2007-04-05 21:43 ` Jeremy Fitzhardinge
2007-04-05 21:43 ` Zachary Amsden
2007-04-05 21:49 ` Jeremy Fitzhardinge
2007-04-05 21:59 ` H. Peter Anvin
2007-04-05 22:19 ` Jeremy Fitzhardinge
2007-04-05 22:31 ` H. Peter Anvin
2007-04-05 21:54 ` Chris Wright
2007-04-05 1:48 ` Tony Breeds
2007-04-05 5:00 ` Zachary Amsden
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=461539DF.6010502@zytor.com \
--to=hpa@zytor.com \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.