mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH v5 07/15] x86/mtrr: replace vendor tests in MTRR code
Date: Wed, 12 Apr 2023 12:25:01 +0200	[thread overview]
Message-ID: <5e75d8ed-6950-1c16-02eb-1894b90bfffc@suse.com> (raw)
In-Reply-To: <20230412084541.GIZDZvtcMnWYJ7Kh6a@fat_crate.local>


[-- Attachment #1.1.1: Type: text/plain, Size: 1813 bytes --]

On 12.04.23 10:45, Borislav Petkov wrote:
> On Sat, Apr 01, 2023 at 08:36:44AM +0200, Juergen Gross wrote:
>> Modern CPUs all share the same MTRR interface implemented via
>> generic_mtrr_ops.
>>
>> At several places in MTRR code this generic interface is deduced via
>> is_cpu(INTEL) tests, which is only working due to X86_VENDOR_INTEL
>> being 0 (the is_cpu() macro is testing mtrr_if->vendor, which isn't
>> explicitly set in generic_mtrr_ops).
>>
>> Fix that by replacing the is_cpu(INTEL) tests with testing for mtrr_if
>> to be &generic_mtrr_ops.
> 
> Replace with:
> 
> "Test the generic CPU feature X86_FEATURE_MTRR instead."
> 
>> diff --git a/arch/x86/kernel/cpu/mtrr/mtrr.c b/arch/x86/kernel/cpu/mtrr/mtrr.c
>> index 1c19d67ddab3..46aae69d259e 100644
>> --- a/arch/x86/kernel/cpu/mtrr/mtrr.c
>> +++ b/arch/x86/kernel/cpu/mtrr/mtrr.c
>> @@ -108,14 +108,12 @@ static int have_wrcomb(void)
>>   /*  This function returns the number of variable MTRRs  */
>>   static void __init set_num_var_ranges(bool use_generic)
>>   {
>> -	unsigned long config = 0, dummy;
>> +	unsigned long config, dummy;
>>   
>>   	if (use_generic)
>>   		rdmsr(MSR_MTRRcap, config, dummy);
>> -	else if (is_cpu(AMD) || is_cpu(HYGON))
>> -		config = 2;
>> -	else if (is_cpu(CYRIX) || is_cpu(CENTAUR))
>> -		config = 8;
>> +	else
>> +		config = mtrr_if->var_regs;
>>   
>>   	num_var_ranges = config & MTRR_CONFIG_NUM_VAR_MASK;
>>   }
> 
>  From previous review which you've missed to incorporate:
> 
> "Since you're touching this function, you might simply expand its body in
> its only call site in mtrr_bp_init(), put a comment above the expanded
> code and remove that function.
> 
> That is, if we're going to do the ->var_regs thing."
> 

Oh, sorry. Will do it.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2023-04-12 10:25 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01  6:36 [PATCH v5 00/15] x86/mtrr: fix handling with PAT but without MTRR Juergen Gross
2023-04-01  6:36 ` [PATCH v5 01/15] x86/mtrr: split off physical address size calculation Juergen Gross
2023-04-01  6:36 ` [PATCH v5 02/15] x86/mtrr: optimize mtrr_calc_physbits() Juergen Gross
2023-04-01  6:36 ` [PATCH v5 03/15] x86/mtrr: replace some constants with defines Juergen Gross
2023-04-03 16:03   ` Borislav Petkov
2023-04-05  7:55     ` Juergen Gross
2023-04-05 20:26       ` Borislav Petkov
2023-04-11 13:32         ` Juergen Gross
2023-04-01  6:36 ` [PATCH v5 04/15] x86/mtrr: support setting MTRR state for software defined MTRRs Juergen Gross
2023-04-03  2:25   ` Huang, Kai
2023-04-03  7:10     ` Juergen Gross
2023-04-03  9:27       ` Huang, Kai
2023-04-03  9:35         ` Juergen Gross
2023-04-03  9:44           ` Huang, Kai
2023-04-03  9:43         ` Huang, Kai
2023-04-11 13:20   ` Borislav Petkov
2023-04-11 13:31     ` Juergen Gross
2023-04-11 17:14       ` Borislav Petkov
2023-04-11 13:59     ` Michael Kelley (LINUX)
2023-04-11 14:04       ` Juergen Gross
2023-04-11 14:26         ` Borislav Petkov
2023-04-11 15:57           ` Juergen Gross
2023-04-11 17:15             ` Borislav Petkov
2023-04-12  8:30               ` Juergen Gross
2023-04-11 14:25       ` Borislav Petkov
2023-04-01  6:36 ` [PATCH v5 05/15] x86/hyperv: set MTRR state when running as SEV-SNP Hyper-V guest Juergen Gross
2023-04-02  2:36   ` Michael Kelley (LINUX)
2023-04-01  6:36 ` [PATCH v5 06/15] x86/xen: set MTRR state when running as Xen PV initial domain Juergen Gross
2023-04-01  6:36 ` [PATCH v5 07/15] x86/mtrr: replace vendor tests in MTRR code Juergen Gross
2023-04-12  8:45   ` Borislav Petkov
2023-04-12 10:25     ` Juergen Gross [this message]
2023-04-01  6:36 ` [PATCH v5 08/15] x86/mtrr: have only one set_mtrr() variant Juergen Gross
2023-04-12 12:30   ` Borislav Petkov
2023-04-12 12:56     ` Juergen Gross
2023-04-12 20:09       ` Borislav Petkov
2023-04-01  6:36 ` [PATCH v5 09/15] x86/mtrr: allocate mtrr_value array dynamically Juergen Gross
2023-04-12 21:11   ` Borislav Petkov
2023-04-13 10:07     ` Juergen Gross
2023-04-01  6:36 ` [PATCH v5 10/15] x86/mtrr: add get_effective_type() service function Juergen Gross
2023-04-01  6:36 ` [PATCH v5 11/15] x86/mtrr: construct a memory map with cache modes Juergen Gross
2023-04-20 12:15   ` Borislav Petkov
2023-04-20 12:30     ` Juergen Gross
2023-04-20 12:30       ` Juergen Gross
2023-04-20 13:01       ` Borislav Petkov
2023-04-20 13:57         ` Juergen Gross
2023-04-20 14:54           ` Borislav Petkov
2023-04-20 15:10             ` Juergen Gross
2023-04-21 11:23               ` Borislav Petkov
2023-04-21 14:35                 ` Juergen Gross
2023-04-01  6:36 ` [PATCH v5 12/15] x86/mtrr: use new cache_map in mtrr_type_lookup() Juergen Gross
2023-04-01  6:36 ` [PATCH v5 13/15] x86/mtrr: don't let mtrr_type_lookup() return MTRR_TYPE_INVALID Juergen Gross
2023-04-01  6:36 ` [PATCH v5 14/15] x86/mm: only check uniform after calling mtrr_type_lookup() Juergen Gross
2023-04-01  6:36 ` [PATCH v5 15/15] x86/mtrr: remove unused code Juergen Gross

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=5e75d8ed-6950-1c16-02eb-1894b90bfffc@suse.com \
    --to=jgross@suse.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®