From: Toshi Kani <toshi.kani@hp.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: hpa@zytor.com, mingo@redhat.com, akpm@linux-foundation.org,
arnd@arndb.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-nvdimm@ml01.01.org, jgross@suse.com,
stefan.bader@canonical.com, luto@amacapital.net, hmh@hmh.eng.br,
yigal@plexistor.com, konrad.wilk@oracle.com, Elliott@hp.com,
mcgrof@suse.com, hch@lst.de
Subject: Re: [PATCH v9 9/10] x86, mm, pat: Refactor !pat_enabled handling
Date: Fri, 22 May 2015 10:27:27 -0600 [thread overview]
Message-ID: <1432312047.1428.34.camel@misato.fc.hp.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1505220958050.5457@nanos>
On Fri, 2015-05-22 at 10:34 +0200, Thomas Gleixner wrote:
> On Wed, 13 May 2015, Toshi Kani wrote:
>
> > --- a/arch/x86/mm/pat.c
> > +++ b/arch/x86/mm/pat.c
> > @@ -182,7 +182,11 @@ void pat_init_cache_modes(void)
> > char pat_msg[33];
> > u64 pat;
> >
> > - rdmsrl(MSR_IA32_CR_PAT, pat);
> > + if (pat_enabled)
> > + rdmsrl(MSR_IA32_CR_PAT, pat);
> > + else
> > + pat = boot_pat_state;
>
> boot_pat_state is 0 if pat is disabled, but this boot_pat_state multi
> purpose usage is really horrible. We do 5 things at once with it and
> of course all of it completely undocumented.
boot_pat_state is set even if pat is disabled so that this case can be
handled in the same framework.
:
if (!pat_enabled) {
/*
* No PAT. Emulate the PAT table that corresponds to the two
:
pat = PAT(0, WB) | PAT(1, WT) | PAT(2, UC_MINUS) | PAT(3, UC) |
PAT(4, WB) | PAT(5, WT) | PAT(6, UC_MINUS) | PAT(7, UC);
if (!boot_pat_state)
boot_pat_state = pat;
:
That said, yes, I agree that the use of boot_pat_state is overloaded.
> pat_msg[32] = 0;
> > for (i = 7; i >= 0; i--) {
> > cache = pat_get_cache_mode((pat >> (i * 8)) & 7,
> > @@ -200,28 +204,58 @@ void pat_init(void)
> > bool boot_cpu = !boot_pat_state;
>
> The crap starts here and this really wants to be distangled.
Agreed.
> void pat_init(void)
> {
> static bool boot_done;
>
> if (!boot_done) {
> if (!cpu_has_pat)
> pat_disable("PAT not supported by CPU.");
>
> if (pat_enabled) {
> rdmsrl(MSR_IA32_CR_PAT, boot_pat_state);
> if (!boot_pat_state)
> pat_disable("PAT read returns always zero, disabled.");
> }
> } else if (!cpu_has_pat && pat_enabled) {
> /*
> * If this happens we are on a secondary CPU, but
> * switched to PAT on the boot CPU. We have no way to
> * undo PAT.
> */
> pr_err("PAT enabled but not supported by secondary CPU\n");
> BUG();
> }
>
>
> if (!pat_enabled) {
> .....
> } else {
> .....
> }
>
> if (!boot_done) {
> ....
> boot_done = true;
> }
> }
>
> And this cleanup wants to be done as a seperate patch before you do
> this other stuff.
Yes, this looks much better! Will add a patch for this clean up.
> > @@ -275,16 +309,8 @@ void pat_init(void)
> > PAT(4, WB) | PAT(5, WC) | PAT(6, UC_MINUS) | PAT(7, WT);
> > }
> >
> > - /* Boot CPU check */
> > - if (!boot_pat_state) {
> > - rdmsrl(MSR_IA32_CR_PAT, boot_pat_state);
> > - if (!boot_pat_state) {
> > - pat_disable("PAT read returns always zero, disabled.");
> > - return;
> > - }
> > - }
> > -
> > - wrmsrl(MSR_IA32_CR_PAT, pat);
> > + if (pat_enabled)
> > + wrmsrl(MSR_IA32_CR_PAT, pat);
>
> Sigh.
Yeah...
>
> if (!pat_enabled) {
> ....
> } else {
> ....
> }
>
> + if (pat_enabled)
>
> Thanks,
Thanks a lot!
-Toshi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-05-22 16:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 21:05 [PATCH v9 0/10] Support Write-Through mapping on x86 Toshi Kani
2015-05-13 21:05 ` [PATCH v9 1/10] x86, mm, pat: Set WT to PA7 slot of PAT MSR Toshi Kani
2015-05-22 6:55 ` Thomas Gleixner
2015-05-13 21:05 ` [PATCH v9 2/10] x86, mm, pat: Change reserve_memtype() for WT Toshi Kani
2015-05-22 7:01 ` Thomas Gleixner
2015-05-13 21:05 ` [PATCH v9 3/10] x86, asm: Change is_new_memtype_allowed() " Toshi Kani
2015-05-22 7:02 ` Thomas Gleixner
2015-05-13 21:05 ` [PATCH v9 4/10] x86, mm, asm-gen: Add ioremap_wt() " Toshi Kani
2015-05-22 7:08 ` Thomas Gleixner
2015-05-13 21:05 ` [PATCH v9 5/10] arch/*/asm/io.h: Add ioremap_wt() to all architectures Toshi Kani
2015-05-22 7:15 ` Thomas Gleixner
2015-05-22 14:08 ` Toshi Kani
2015-05-13 21:05 ` [PATCH v9 6/10] x86, mm, pat: Add pgprot_writethrough() for WT Toshi Kani
2015-05-22 7:16 ` Thomas Gleixner
2015-05-13 21:05 ` [PATCH v9 7/10] x86, mm, asm: Add WT support to set_page_memtype() Toshi Kani
2015-05-22 7:35 ` Thomas Gleixner
2015-05-22 15:04 ` Toshi Kani
2015-05-13 21:05 ` [PATCH v9 8/10] x86, mm: Add set_memory_wt() for WT Toshi Kani
2015-05-22 7:48 ` Thomas Gleixner
2015-05-22 15:30 ` Toshi Kani
2015-05-13 21:05 ` [PATCH v9 9/10] x86, mm, pat: Refactor !pat_enabled handling Toshi Kani
2015-05-22 8:34 ` Thomas Gleixner
2015-05-22 16:27 ` Toshi Kani [this message]
2015-05-13 21:05 ` [PATCH v9 10/10] drivers/block/pmem: Map NVDIMM with ioremap_wt() Toshi Kani
2015-05-14 21:52 ` Dan Williams
2015-05-14 22:20 ` 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=1432312047.1428.34.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=Elliott@hp.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yigal@plexistor.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