From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
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:59:34 -0700 [thread overview]
Message-ID: <46157146.1090406@zytor.com> (raw)
In-Reply-To: <46156EDC.8080403@goop.org>
Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>> Or implement anything useful at all ... perhaps it might be useful to
>> simply wrap them with an -ENOSYS in some cases.
>>
>> Rusty, Jeremy. Chris - any feedback on MSR support?
>
> I've looked at hpa's patch a bit, but I don't quite get what the point
> is yet. Is it that rdmsr/wrmsr can use multiple random registers, so
> its necessary to haul them all around? And that cpuid might use more
> beyond the current eax-edx?
>
Yes, pretty much. There are enough evidence that you can't trust CPU
architecture to stay sane. Inside Transmeta it was a constant battle,
and we were a small company.
> Xen will trap and emulate any rd/wrmsr instructions, so I don't think it
> needs anything beyond native support.
If that's true for all hypervisors, then that's obviously the easiest
all around.
-hpa
next prev parent reply other threads:[~2007-04-05 21:59 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
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 [this message]
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=46157146.1090406@zytor.com \
--to=hpa@zytor.com \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.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).