From: Toshi Kani <toshi.kani@hpe.com>
To: Borislav Petkov <bp@suse.de>
Cc: mingo@kernel.org, hpa@zytor.com, tglx@linutronix.de,
mcgrof@suse.com, jgross@suse.com, paul.gortmaker@windriver.com,
konrad.wilk@oracle.com, elliott@hpe.com, x86@kernel.org,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] x86/pat: Document PAT initializations
Date: Tue, 22 Mar 2016 16:15:38 -0600 [thread overview]
Message-ID: <1458684938.6393.636.camel@hpe.com> (raw)
In-Reply-To: <20160322170222.GG5656@pd.tnic>
On Tue, 2016-03-22 at 18:02 +0100, Borislav Petkov wrote:
> On Wed, Mar 16, 2016 at 06:46:59PM -0600, Toshi Kani wrote:
> > Update PAT documentation to describe how PAT is initialized under
> > various configurations.
> >
:
> >
> > +PAT Initialization
> > +------------------
> > +
> > +The following table describes how PAT is initialized under various
> > +configurations. PAT must be set to enable to initialize PAT MSR in
> > order
>
> Err "PAT MSR must be updated by Linux in order to support WC and WT" ...
> or so?
Right. Will do.
> > +to support WC and WT attributes. Otherwise, PAT keeps PAT MSR value
> > set
> > +by BIOS.
>
> "Otherwise, the PAT MSR has the value programmed in it by the firmware."
Will do.
> > Note, Xen enables WC attribute in BIOS setup for guests.
> > +
> > + MTRR PAT Call Sequence PAT State PAT MSR
> > + =========================================================
> > + E E MTRR -> pat_init() Enable OS
>
> s/Enable/Enabled/
Will do.
> MTRR->pat_init() - either use function names for both or do pseudo like
> so:
>
> MTRR init -> PAT init
OK, I will change all to pseudo. MTRR has multiple caller functions, and
we do not have enough space to write them all.
> > + E D MTRR -> pat_init() Disable -
>
> s/Disable/Disabled/. Ditto for the rest.
Will do.
> > + D E MTRR -> pat_disable() Disable BIOS
> > + D D MTRR -> pat_disable() Disable -
> > + - np/E nopat() -> pat_disable() Disable BIOS
> > + - np/D nopat() -> pat_disable() Disable -
> > + E !P/E MTRR -> pat_init() Disable BIOS
> > + D !P/E MTRR -> pat_disable() Disable BIOS
> > + !M !P/E MTRR stub -> pat_disable() Disable BIOS
> > +
> > + Legend
> > + ------------------------------------------------
> > + E Feature enabled in CPU
> > + D Feature disabled/unsupported in CPU
> > + np "nopat" boot option specified
> > + !P CONFIG_X86_PAT option unset
> > + !M CONFIG_MTRR option unset
> > + Enable PAT state set to enable
> > + Disable PAT state set to disable
> > + OS PAT initializes PAT MSR with OS setup
> > + BIOS PAT keeps PAT MSR with BIOS setup
> > +
Thanks,
-Toshi
next prev parent reply other threads:[~2016-03-22 21:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 0:46 [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface Toshi Kani
2016-03-17 0:46 ` [PATCH v2 3/6] x86/mtrr: Fix Xorg crashes in Qemu sessions Toshi Kani
2016-03-22 17:00 ` Borislav Petkov
2016-03-22 21:53 ` Toshi Kani
2016-03-23 8:44 ` Borislav Petkov
2016-03-23 15:53 ` Toshi Kani
2016-03-23 21:47 ` Toshi Kani
2016-03-17 0:46 ` [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled Toshi Kani
2016-03-22 17:01 ` Borislav Petkov
2016-03-22 22:02 ` Toshi Kani
2016-03-17 0:46 ` [PATCH v2 5/6] x86/xen,pat: Remove PAT table init code from Xen Toshi Kani
2016-03-22 17:02 ` Borislav Petkov
2016-03-23 6:08 ` Juergen Gross
2016-03-17 0:46 ` [PATCH v2 6/6] x86/pat: Document PAT initializations Toshi Kani
2016-03-22 17:02 ` Borislav Petkov
2016-03-22 22:15 ` Toshi Kani [this message]
2016-03-22 16:59 ` [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface Borislav Petkov
2016-03-22 21:40 ` Toshi Kani
2016-03-23 8:51 ` Borislav Petkov
2016-03-23 15:49 ` Toshi Kani
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=1458684938.6393.636.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=bp@suse.de \
--cc=elliott@hpe.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®