From: Zachary Amsden <zach@vmware.com>
To: "H. Peter Anvin" <hpa@zytor.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 14:27:19 -0700 [thread overview]
Message-ID: <461569B7.7060008@vmware.com> (raw)
In-Reply-To: <46156783.9030501@zytor.com>
H. Peter Anvin wrote:
>
> It seems to me that perhaps this is the way to do it:
>
> - Add cpuid_everything, rdmsr_everything and wrmsr_everything
> entrypoints;
Yes, although I think we can omit rdmsr / wrmsr.
>
> - Provide compatibility wrappers that simply invoke the cpuid, rdmsr,
> and wrmsr entrypoints with appropriate parameter marshalling;
>
> - On hardware, point them to the functions which invoke setgpr_wrapper.
>
> What do you think?
Well it is more work than the hack, but it is more maintainable and
makes for less assembly code - we could do all the parameter juggling in
C for the paravirt-ops case.
Zach
next prev parent reply other threads:[~2007-04-05 21:27 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
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 [this message]
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=461569B7.7060008@vmware.com \
--to=zach@vmware.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).