All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: New CPUID/MSR driver; virtualization hooks
Date: Wed, 04 Apr 2007 22:00:45 -0700	[thread overview]
Message-ID: <4614827D.9090805@vmware.com> (raw)
In-Reply-To: <461447F2.9010807@zytor.com>

H. Peter Anvin wrote:
> I have finally gotten off the pot and finished writing up my new 
> CPUID/MSR driver, which contains support for registers that need 
> arbitrary GPRs touched.  For i386 vs x86-64 compatibility, both use an 
> x86-64 register image (16 64-bit register fields); this allows 32-bit 
> userspace to access the full 64-bit image if the kernel is 64 bits.
>
> Anyway, this presumably requires new paravirtualization hooks.  The 
> patch is at:
>
> 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.

> ... and a git tree is at ...
>
> http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-cpuidmsr.git;a=summary
>
> I'm posting this here to give the paravirt maintainers an opportunity to 
> comment.  Presumably the functions that need to be paravirtualized are 
> the ones represented by the functions do_cpuid(), do_rdmsr() and
>   

rdmsr / wrmsr can be dropped from paravirt-ops; at least for us (they 
will trap and emulate just fine, and this driver is not performance 
critical), and I think for the others as well.  CPUID, however, does 
require a hook.

Zach

      parent reply	other threads:[~2007-04-05  5:00 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
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 [this message]

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=4614827D.9090805@vmware.com \
    --to=zach@vmware.com \
    --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 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.