From: Chris Wilson <chris@chris-wilson.co.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>,
Venkatesh Pallipadi <venki@google.com>
Subject: Re: Loss of PAT-WC after resume on i5
Date: Mon, 03 Jan 2011 16:21:09 +0000 [thread overview]
Message-ID: <1bdc18$j527vf@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <4D21F2C1.30500@zytor.com>
On Mon, 03 Jan 2011 08:01:05 -0800, "H. Peter Anvin" <hpa@zytor.com> wrote:
> Sounds like it. It sounds based on your description that it's something
> more fundamental than just the state of the PAT MSR being lost, too,
> although perhaps that's the first thing to check...
Right, I should have mentioned that a rdmsr(MSR_ISA32_CR_PAT) showed no
change across a dysfunctional resume. And that
/sys/kernel/debug/x86/pat_memtype_list had the same contents (just the
first entries reversed upon resume).
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-03 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <849307$b076ne@azsmga001.ch.intel.com>
2011-01-03 16:01 ` Loss of PAT-WC after resume on i5 H. Peter Anvin
2011-01-03 16:21 ` Chris Wilson [this message]
2011-01-03 17:29 ` 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='1bdc18$j527vf@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=venki@google.com \
/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