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>
Subject: Re: [PATCH v4 09/12] x86/mtrr: construct a memory map with cache modes
Date: Fri, 31 Mar 2023 15:35:07 +0200 [thread overview]
Message-ID: <73226c11-4443-1e52-4566-5799d21e4ccb@suse.com> (raw)
In-Reply-To: <20230331125740.GCZCbYxFkJOg8hIl6C@fat_crate.local>
[-- Attachment #1.1.1: Type: text/plain, Size: 1159 bytes --]
On 31.03.23 14:57, Borislav Petkov wrote:
> On Mon, Mar 06, 2023 at 05:34:22PM +0100, Juergen Gross wrote:
>> +/* Build the cache_map containing the cache modes per memory range. */
>> +void mtrr_build_map(void)
>> +{
>> + unsigned int i;
>> + u64 start, end, size;
>> + u8 type;
>> +
>> + if (!mtrr_state.enabled)
> ^^^^^^^^^^^^^^^^^^^
>
>> + return;
>> +
>> + /* Add fixed MTRRs, optimize for adjacent entries with same type. */
>> + if (mtrr_state.enabled & MTRR_STATE_MTRR_FIXED_ENABLED) {
> ^^^^^^^^^^^^^^^^^^
>
> First check can go.
Hmm, this makes it much harder to see that the code really does nothing
if enabled isn't set.
>
>> + start = 0;
>> + end = size = 0x10000;
>> + type = mtrr_state.fixed_ranges[0];
>> +
>> + for (i = 1; i < MTRR_NUM_FIXED_RANGES; i++) {
>
> Loops starts at 1. Comment explaining why pls.
Okay.
>
>> + if (i == 8 || i == 24)
>
> Magic numbers.
I'll add more comments.
>
> Ok, I'll stop here.
>
> Please send a new version with the review comments incorporated. I need
> to look more at that map thing more.
Will do.
Thanks,
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 --]
next prev parent reply other threads:[~2023-03-31 13:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 16:34 [PATCH v4 00/12] x86/mtrr: fix handling with PAT but without MTRR Juergen Gross
2023-03-06 16:34 ` [PATCH v4 01/12] x86/mtrr: split off physical address size calculation Juergen Gross
2023-03-06 16:34 ` [PATCH v4 02/12] x86/mtrr: optimize mtrr_calc_physbits() Juergen Gross
2023-03-20 12:50 ` Borislav Petkov
2023-03-06 16:34 ` [PATCH v4 03/12] x86/mtrr: support setting MTRR state for software defined MTRRs Juergen Gross
2023-03-20 12:59 ` Huang, Kai
2023-03-20 13:47 ` Juergen Gross
2023-03-20 21:34 ` Huang, Kai
2023-03-20 22:42 ` Borislav Petkov
2023-03-21 6:01 ` Juergen Gross
2023-03-20 19:05 ` Borislav Petkov
2023-03-21 6:00 ` Juergen Gross
2023-03-21 10:30 ` Borislav Petkov
2023-03-21 15:49 ` Juergen Gross
2023-03-06 16:34 ` [PATCH v4 04/12] x86/hyperv: set MTRR state when running as SEV-SNP Hyper-V guest Juergen Gross
2023-03-06 16:34 ` [PATCH v4 05/12] x86/xen: set MTRR state when running as Xen PV initial domain Juergen Gross
2023-03-07 21:47 ` Boris Ostrovsky
2023-03-23 12:43 ` Borislav Petkov
2023-03-06 16:34 ` [PATCH v4 06/12] x86/mtrr: replace vendor tests in MTRR code Juergen Gross
2023-03-24 16:56 ` Borislav Petkov
2023-03-27 5:43 ` Juergen Gross
2023-03-27 7:14 ` Borislav Petkov
2023-03-06 16:34 ` [PATCH v4 07/12] x86/mtrr: allocate mtrr_value array dynamically Juergen Gross
2023-03-20 12:25 ` Huang, Kai
2023-03-20 13:49 ` Juergen Gross
2023-03-20 15:31 ` Dave Hansen
2023-03-20 15:49 ` Juergen Gross
2023-03-26 22:05 ` Borislav Petkov
2023-03-27 5:44 ` Juergen Gross
2023-03-06 16:34 ` [PATCH v4 08/12] x86/mtrr: add get_effective_type() service function Juergen Gross
2023-03-06 16:34 ` [PATCH v4 09/12] x86/mtrr: construct a memory map with cache modes Juergen Gross
2023-03-29 12:51 ` Borislav Petkov
2023-03-29 13:39 ` Juergen Gross
2023-03-31 12:55 ` Borislav Petkov
2023-03-31 13:23 ` Juergen Gross
2023-04-01 14:24 ` Borislav Petkov
2023-04-03 6:57 ` Juergen Gross
2023-03-31 12:57 ` Borislav Petkov
2023-03-31 13:35 ` Juergen Gross [this message]
2023-04-01 14:26 ` Borislav Petkov
2023-04-03 7:02 ` Juergen Gross
2023-03-06 16:34 ` [PATCH v4 10/12] x86/mtrr: use new cache_map in mtrr_type_lookup() Juergen Gross
2023-03-06 16:34 ` [PATCH v4 11/12] x86/mtrr: don't let mtrr_type_lookup() return MTRR_TYPE_INVALID Juergen Gross
2023-03-06 16:34 ` [PATCH v4 12/12] x86/mm: only check uniform after calling mtrr_type_lookup() Juergen Gross
2023-03-07 21:09 ` [PATCH v4 00/12] x86/mtrr: fix handling with PAT but without MTRR Michael Kelley (LINUX)
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=73226c11-4443-1e52-4566-5799d21e4ccb@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=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;
as well as URLs for NNTP newsgroup(s).