From: Fenghua Yu <fenghua.yu@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, reinette.chatre@intel.com,
babu.moger@amd.com, x86@kernel.org
Subject: Re: [PATCH v2] x86/resctrl: Fix zero cbm for AMD in cbm_validate
Date: Tue, 17 May 2022 09:33:28 -0700 [thread overview]
Message-ID: <YoPOWC0waMuSlvI6@fyu1.sc.intel.com> (raw)
In-Reply-To: <20220517001234.3137157-1-eranian@google.com>
Hi, Eranian,
On Mon, May 16, 2022 at 05:12:34PM -0700, Stephane Eranian wrote:
> AMD supports cbm with no bits set as reflected in rdt_init_res_defs_amd() by:
...
> @@ -107,6 +107,10 @@ static bool cbm_validate(char *buf, u32 *data, struct rdt_resource *r)
> first_bit = find_first_bit(&val, cbm_len);
> zero_bit = find_next_zero_bit(&val, cbm_len, first_bit);
>
> + /* no need to check bits if arch supports no bits set */
> + if (r->cache.arch_has_empty_bitmaps && val == 0)
> + goto done;
> +
> /* Are non-contiguous bitmaps allowed? */
> if (!r->cache.arch_has_sparse_bitmaps &&
> (find_next_bit(&val, cbm_len, zero_bit) < cbm_len)) {
> @@ -119,7 +123,7 @@ static bool cbm_validate(char *buf, u32 *data, struct rdt_resource *r)
> r->cache.min_cbm_bits);
> return false;
> }
> -
> +done:
> *data = val;
> return true;
> }
Isn't it AMD supports 0 minimal CBM bits? Then should set its min_cbm_bits as 0.
Is the following patch a better fix? I don't have AMD machine and cannot
test the patch.
diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c
index 6055d05af4cc..031d77dd982d 100644
--- a/arch/x86/kernel/cpu/resctrl/core.c
+++ b/arch/x86/kernel/cpu/resctrl/core.c
@@ -909,6 +909,7 @@ static __init void rdt_init_res_defs_amd(void)
r->cache.arch_has_sparse_bitmaps = true;
r->cache.arch_has_empty_bitmaps = true;
r->cache.arch_has_per_cpu_cfg = true;
+ r->cache.min_cbm_bits = 0;
} else if (r->rid == RDT_RESOURCE_MBA) {
hw_res->msr_base = MSR_IA32_MBA_BW_BASE;
hw_res->msr_update = mba_wrmsr_amd;
next prev parent reply other threads:[~2022-05-17 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 0:12 Stephane Eranian
2022-05-17 16:33 ` Fenghua Yu [this message]
2022-05-17 16:49 ` Reinette Chatre
2022-05-17 17:27 ` Fenghua Yu
2022-05-17 18:10 ` Reinette Chatre
2022-05-18 16:34 ` Fenghua Yu
2022-05-25 13:10 ` Stephane Eranian
2022-07-25 19:47 ` Babu Moger
2022-08-01 14:58 ` Moger, Babu
2022-08-01 15:19 ` Stephane Eranian
2022-10-18 18:33 ` [tip: x86/urgent] x86/resctrl: Fix min_cbm_bits for AMD tip-bot2 for Babu Moger
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=YoPOWC0waMuSlvI6@fyu1.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=babu.moger@amd.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--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®