From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: use of scratchpad registers
Date: Mon, 25 Mar 2013 10:12:57 -0400 [thread overview]
Message-ID: <20130325141257.GH11546@phenom.dumpdata.com> (raw)
In-Reply-To: <51502FEA02000078000C8088@nat28.tlf.novell.com>
On Mon, Mar 25, 2013 at 10:07:22AM +0000, Jan Beulich wrote:
> Konrad,
>
> in a response on thread "High CPU temp, suspend problem - xen
> 4.1.5-pre, linux 3.7.x", you say
>
> "There are some BIOSes out there that I know that use the
> scratchpad registers in IOH (so depending on the platform that
> can be 0:0e.1 , Reg 0x84). If Xen or Linux touch it then the
> P-states and C-states that the BIOS generates are buggy",
>
> which makes me assume you have knowledge on why and where
> Xen or Linux would touch these registers. It is my understanding
> that these registers should be left alone by Xen, and be used by
> Linux only in ways consistent between native and running on top
> of Xen (i.e. through the same specific driver).
>
> However, we've been having a report of there being a difference
> in behavior, which so far we weren't able to narrow down the
> origin of. Hence, if you know details here, I'd very much
> appreciate if you could share them.
Of course. Let me email the group that had let me know about this
scratchpad registers and see if they narrowed down _who_ was
poking at that. Once I get that information - or if they are
comfortable responding in a public forum, I will post it
here ASAP.
>
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
prev parent reply other threads:[~2013-03-25 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:07 use of scratchpad registers Jan Beulich
2013-03-25 14:12 ` Konrad Rzeszutek Wilk [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=20130325141257.GH11546@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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.