From: Andi Kleen <ak@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alexey Dobriyan <adobriyan@openvz.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
davej@codemonkey.org.uk, devel@vger.kernel.org
Subject: Re: [PATCH] rdmsr_on_cpu, wrmsr_on_cpu
Date: Fri, 19 Jan 2007 10:21:16 +1100 [thread overview]
Message-ID: <200701191021.16706.ak@suse.de> (raw)
In-Reply-To: <45AFF12D.2070901@zytor.com>
> HOWEVER -- and this is where things get gnarly -- the CPUID and MSR
> drivers would really like to be able to execute CPUID, WRMSR and RDMSR
> with the entire GPR register set (except the stack pointer) pre-set and
> post-captured, since it's highly likely that there are going to be
> nonstandard MSRs and CPUID levels (already witness Intel breaking the
> CPUID architecture by introducing %ecx dependencies.)
That looks like such a specialized requirement that I would suggest
you keep that in the drivers. The interface for most users would be just
too ugly
-Andi
next prev parent reply other threads:[~2007-01-18 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 14:45 [PATCH] rdmsr_on_cpu, wrmsr_on_cpu Alexey Dobriyan
2007-01-18 22:14 ` H. Peter Anvin
2007-01-18 23:21 ` Andi Kleen [this message]
2007-01-18 23:40 ` H. Peter Anvin
2007-01-19 0:40 ` Andi Kleen
2007-01-19 0:45 ` H. Peter Anvin
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=200701191021.16706.ak@suse.de \
--to=ak@suse.de \
--cc=adobriyan@openvz.org \
--cc=akpm@osdl.org \
--cc=davej@codemonkey.org.uk \
--cc=devel@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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