All of lore.kernel.org
 help / color / mirror / Atom feed
From: Toshi Kani <toshi.kani@hpe.com>
To: Borislav Petkov <bp@suse.de>
Cc: jgross@suse.com, mcgrof@suse.com, x86@kernel.org,
	linux-kernel@vger.kernel.org, paul.gortmaker@windriver.com,
	hpa@zytor.com, xen-devel@lists.xenproject.org,
	tglx@linutronix.de, mingo@kernel.org, elliott@hpe.com
Subject: Re: [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled
Date: Tue, 22 Mar 2016 16:02:13 -0600	[thread overview]
Message-ID: <1458684133.6393.630.camel__2511.52405185184$1458681076$gmane$org@hpe.com> (raw)
In-Reply-To: <20160322170135.GE5656@pd.tnic>

On Tue, 2016-03-22 at 18:01 +0100, Borislav Petkov wrote:
> Subject: [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is
> disabled
> 
> s/ MSR//

Will do.

> On Wed, Mar 16, 2016 at 06:46:57PM -0600, Toshi Kani wrote:
> > get_mtrr_state() calls pat_init() on BSP even if MTRR is disabled
> > by its MSR.
> 
> s/by its MSR//

Will do.

> > This causes pat_init() to be called on BSP only since APs do not call
> 
> This doesn't cause that - get_mtrr_state() is called only on the BSP by
> mtrr_bp_init().

Right, I will change it to "results" or something.

> > pat_init() when MTRR is disabled. This inconsistency between BSP and
> > APs leads undefined behavior.
> 
>       leads to

Will do.

> > Move BSP's PAT init code from get_mtrr_state() to mtrr_bp_pat_init().
> > Change mtrr_bp_init() to call mtrr_bp_pat_init() if MTRR is enabled.
> 
> No need for those.

OK.

> > This keeps BSP's calling condition to pat_init() consistent with AP's,
> > mtrr_ap_init() and mtrr_aps_init().
> 
> This one is fine.

:-)

Thanks,
-Toshi

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-03-22 21:09 UTC|newest]

Thread overview: 40+ 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 ` 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 17:00   ` Borislav Petkov
2016-03-22 21:53     ` Toshi Kani
2016-03-23  8:44       ` Borislav Petkov
2016-03-23  8:44       ` Borislav Petkov
2016-03-23 15:53         ` Toshi Kani
2016-03-23 15:53         ` Toshi Kani
2016-03-23 21:47           ` Toshi Kani
2016-03-23 21:47           ` Toshi Kani
2016-03-22 21:53     ` Toshi Kani
2016-03-17  0:46 ` 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-17  0:46 ` Toshi Kani
2016-03-22 17:01   ` Borislav Petkov
2016-03-22 22:02     ` Toshi Kani
2016-03-22 22:02     ` Toshi Kani [this message]
2016-03-22 17:01   ` Borislav Petkov
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   ` [PATCH v2 5/6] x86/xen, pat: " Borislav Petkov
2016-03-22 17:02   ` [PATCH v2 5/6] x86/xen,pat: " Borislav Petkov
2016-03-23  6:08     ` [PATCH v2 5/6] x86/xen, pat: " Juergen Gross
2016-03-23  6:08     ` [PATCH v2 5/6] x86/xen,pat: " Juergen Gross
2016-03-17  0:46 ` [PATCH v2 5/6] x86/xen, pat: " Toshi Kani
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 17:02   ` Borislav Petkov
2016-03-22 22:15     ` Toshi Kani
2016-03-22 22:15     ` Toshi Kani
2016-03-17  0:46 ` Toshi Kani
2016-03-22 16:59 ` [PATCH v2 2/6] x86/mm/pat: Add pat_disable() interface Borislav Petkov
2016-03-22 16:59 ` Borislav Petkov
2016-03-22 21:40   ` Toshi Kani
2016-03-23  8:51     ` Borislav Petkov
2016-03-23 15:49       ` Toshi Kani
2016-03-23 15:49       ` Toshi Kani
2016-03-23  8:51     ` Borislav Petkov
2016-03-22 21:40   ` 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='1458684133.6393.630.camel__2511.52405185184$1458681076$gmane$org@hpe.com' \
    --to=toshi.kani@hpe.com \
    --cc=bp@suse.de \
    --cc=elliott@hpe.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.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 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.