[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc5e9175-e609-d5f8-da33-65e97d4fd813@intel.com>
Date: Tue, 24 May 2022 11:41:19 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kohei Tarumizu <tarumizu.kohei@...itsu.com>, fenghua.yu@...el.com,
reinette.chatre@...el.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/resctrl: Fix to restore to original value when
re-enabling hardware prefetch register
On 5/17/22 21:55, Kohei Tarumizu wrote:
> The current pseudo_lock.c code overwrites the value of the
> MSR_MISC_FEATURE_CONTROL to 0 even if the original value is not 0.
> Therefore, modify it to save and restore the original values.
>
> Fixes: 018961ae5579 ("x86/intel_rdt: Pseudo-lock region creation/removal core")
> Fixes: 443810fe6160 ("x86/intel_rdt: Create debugfs files for pseudo-locking testing")
> Fixes: 8a2fc0e1bc0c ("x86/intel_rdt: More precise L2 hit/miss measurements")
> Signed-off-by: Kohei Tarumizu <tarumizu.kohei@...itsu.com>
Those commits are pretty old. Is there any reason this is not stable@
material?
Powered by blists - more mailing lists