From: Reinette Chatre <reinette.chatre@intel.com>
To: "Maciej Wieczór-Retman" <maciej.wieczor-retman@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] x86/resctrl: Enable non-contiguous bits in Intel CAT
Date: Tue, 12 Sep 2023 09:13:45 -0700 [thread overview]
Message-ID: <7b73c07a-c229-9d95-7069-7d80df465ffb@intel.com> (raw)
In-Reply-To: <ob4e7sb4pfitjn7arlt7f6be3hvdoyp5yecb4o5ub3i36u2qhv@4s6vzu5nk342>
Hi Maciej,
On 9/11/2023 11:53 PM, Maciej Wieczór-Retman wrote:
> On 2023-09-11 at 13:05:16 -0700, Reinette Chatre wrote:
>> Hi Maciej,
>>> diff --git a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>>> index b44c487727d4..782e2700290b 100644
>>> --- a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>>> +++ b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
>>> @@ -87,10 +87,13 @@ int parse_bw(struct rdt_parse_data *data, struct resctrl_schema *s,
>>>
>>> /*
>>> * Check whether a cache bit mask is valid.
>>> - * For Intel the SDM says:
>>> - * Please note that all (and only) contiguous '1' combinations
>>> - * are allowed (e.g. FFFFH, 0FF0H, 003CH, etc.).
>>> - * Additionally Haswell requires at least two bits set.
>>> + * On Intel CPUs, non-contiguous 1s value support is indicated by CPUID:
>>> + * - CPUID.0x10.1:ECX[3]: L3 non-contiguous 1s value supported if 1
>>> + * - CPUID.0x10.2:ECX[3]: L2 non-contiguous 1s value supported if 1
>>> + *
>>> + * Additionally Haswell requires at least two bits set. Since it does not
>>> + * have CPUID enumeration support for Cache allocation the non-contiguous 1s
>>> + * value support is disabled.
>>
>> The second sentence can be misinterpreted. non-contiguous 1s value support is
>> disabled on Haswell because Haswell does not support non-contiguous 1s value,
>> not because it does not have CPUID enumeration for RDT.
>
> Would phrasing it like this:
>
> + * Additionally Haswell requires at least two bits set. Since it does not
> + * allow the non-contiguous 1s for cache allocation the support is
> + * hardcoded to disabled.
>
> be more sensible?
>
I think the above would be sensible as a comment of cache_alloc_hsw_probe()
where the support is hardcoded but here the comment is just used to summarize
what the hardware supports.
Maybe just something like:
Haswell does not support a non-contiguous 1s value and additionally
requires at least two bits set.
Reinette
next prev parent reply other threads:[~2023-09-12 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 8:53 [PATCH 0/3] x86/resctrl: Non-contiguous bitmasks " Wieczor-Retman, Maciej
2023-09-01 8:55 ` [PATCH 1/3] x86/resctrl: Enable non-contiguous bits " Wieczor-Retman, Maciej
2023-09-11 20:05 ` Reinette Chatre
2023-09-12 6:53 ` Maciej Wieczór-Retman
2023-09-12 16:13 ` Reinette Chatre [this message]
2023-09-01 8:55 ` [PATCH 2/3] x86/resctrl: Add sparse_bitmaps file in info Wieczor-Retman, Maciej
2023-09-11 20:05 ` Reinette Chatre
2023-09-12 6:57 ` Maciej Wieczór-Retman
2023-09-01 8:55 ` [PATCH 3/3] Documentation/x86: Document resctrl's new sparse_bitmaps Wieczor-Retman, Maciej
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=7b73c07a-c229-9d95-7069-7d80df465ffb@intel.com \
--to=reinette.chatre@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.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®