From: "H. Peter Anvin" <hpa@zytor.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: New CPUID/MSR driver; virtualization hooks
Date: Wed, 04 Apr 2007 18:23:50 -0700 [thread overview]
Message-ID: <46144FA6.1000802@zytor.com> (raw)
In-Reply-To: <20070405011640.GL19575@sequoia.sous-sol.org>
Chris Wright wrote:
>>
>> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-cpuidmsr.git;a=summary
>
> Bleah, and gitweb is unhappy ATM too.
>
??? Works for me?
> Without having seen the patch yet, you'll need to make sure
> that the final point which is issuing asm("cpuid") is wrapped
> and split to CONFIG_PARAVIRT and non CONFIG_PARAVIRT modes.
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.
Pretty much as far as I can see it, there are two possible points where
one can break out CONFIG_PARAVIRT:
a) int do_foo(int cpu, const u64 ireg[16], u64 oreg[16]);
b) int foo_everything(const u64 ireg[16], u64 oreg[16]);
The difference, of course, is that the former is invoked on the
originating CPU and the latter on the target CPU at interrupt level.
Those are pretty much the choices.
-hpa
next prev parent reply other threads:[~2007-04-05 1:23 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 [this message]
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
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=46144FA6.1000802@zytor.com \
--to=hpa@zytor.com \
--cc=chrisw@sous-sol.org \
--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).