Re: [Xen-devel] [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled

2016-03-22 Thread Toshi Kani
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 disable

Re: [Xen-devel] [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled

2016-03-22 Thread Borislav Petkov
Subject: [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled s/ MSR// 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// > This causes pat_init() to be called on BSP o

[Xen-devel] [PATCH v2 4/6] x86/mtrr: Fix PAT init handling when MTRR MSR is disabled

2016-03-19 Thread Toshi Kani
get_mtrr_state() calls pat_init() on BSP even if MTRR is disabled by its MSR. This causes pat_init() to be called on BSP only since APs do not call pat_init() when MTRR is disabled. This inconsistency between BSP and APs leads undefined behavior. Move BSP's PAT init code from get_mtrr_state() to