From: Borislav Petkov <bp@suse.de>
To: Toshi Kani <toshi.kani@hpe.com>
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 1/6] x86/mm/pat: Change PAT to support non-default PAT MSR
Date: Wed, 23 Mar 2016 09:43:05 +0100 [thread overview]
Message-ID: <20160323084305.GA8031@pd.tnic> (raw)
In-Reply-To: <1458671719.6393.565.camel@hpe.com>
On Tue, Mar 22, 2016 at 12:35:19PM -0600, Toshi Kani wrote:
> Right. Will change to "Add support of non-default PAT MSR setting at
> handoff".
Please remove this "handoff" notion from the text. Every hw register is
being handed off to the OS once the kernel takes over so there's no need
to make it special here.
> I'd like to make it clear that this function does not set PAT MSR, unlike
> what pat_init() does. When CPU supports PAT, it keeps PAT MSR in whatever
> the setting at handoff, and initializes PAT table to match with this
> setting.
>
> I am open to a better name, but I am afraid that setup_pat() can be
> confusing as if it sets PAT MSR.
So call it init_cache_modes() and rename the current
pat_init_cache_modes() to __init_cache_modes() to denote it is a lower
level helper of the init_cache_modes() one. The init_cache_modes() one
deals with the higher level figuring out of whether PAT is enabled and
if not, preparing the attr bits for emulation. In the end, it calls
__init_cache_modes(). All nice and easy.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-03-23 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 0:44 [PATCH 0/6] Enhance PAT init to fix Xorg crashes Toshi Kani
2016-03-17 0:44 ` [PATCH v2 1/6] x86/mm/pat: Change PAT to support non-default PAT MSR Toshi Kani
2016-03-22 16:57 ` Borislav Petkov
2016-03-22 18:35 ` Toshi Kani
2016-03-23 8:43 ` Borislav Petkov [this message]
2016-03-23 15:46 ` Toshi Kani
2016-03-22 19:17 ` Thomas Gleixner
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=20160323084305.GA8031@pd.tnic \
--to=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=toshi.kani@hpe.com \
--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