From: Fenghua Yu <fenghua.yu@intel.com>
To: Babu Moger <babu.moger@amd.com>
Cc: reinette.chatre@intel.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/resctrl: Fix memory bandwidth counter width for AMD
Date: Mon, 1 Jun 2020 16:23:18 -0700 [thread overview]
Message-ID: <20200601232318.GA57376@romley-ivt3.sc.intel.com> (raw)
In-Reply-To: <159105232628.48268.7763865625735367523.stgit@naples-babu.amd.com>
On Mon, Jun 01, 2020 at 06:00:29PM -0500, Babu Moger wrote:
> Memory bandwidth is calculated reading the monitoring counter
> at two intervals and calculating the delta. It is the software’s
> responsibility to read the count often enough to avoid having
> the count roll over _twice_ between reads.
>
> The current code hardcodes the bandwidth monitoring counter's width
> to 24 bits for AMD. This is due to default base counter width which
> is 24. Currently, AMD does not implement the CPUID 0xF.[ECX=1]:EAX
> to adjust the counter width. But, the AMD hardware supports much
> wider bandwidth counter with the default width of 44 bits.
>
> Kernel reads these monitoring counters every 1 second and adjusts the
> counter value for overflow. With 24 bits and scale value of 64 for AMD,
> it can only measure up to 1GB/s without overflowing. For the rates
> above 1GB/s this will fail to measure the bandwidth.
>
> Fix the issue setting the default width to 44 bits by adjusting the
> offset.
>
> AMD future products will implement the CPUID 0xF.[ECX=1]:EAX.
>
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
> - Sending it second time. Email client had some issues first time.
> - Generated the patch on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git (x86/cache).
>
> arch/x86/kernel/cpu/resctrl/core.c | 8 +++++++-
> arch/x86/kernel/cpu/resctrl/internal.h | 1 +
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c
> index 12f967c6b603..6040e9ae541b 100644
> --- a/arch/x86/kernel/cpu/resctrl/core.c
> +++ b/arch/x86/kernel/cpu/resctrl/core.c
> @@ -983,7 +983,13 @@ void resctrl_cpu_detect(struct cpuinfo_x86 *c)
> c->x86_cache_occ_scale = ebx;
> if (c->x86_vendor == X86_VENDOR_INTEL)
> c->x86_cache_mbm_width_offset = eax & 0xff;
> - else
> + else if (c->x86_vendor == X86_VENDOR_AMD) {
> + if (eax)
> + c->x86_cache_mbm_width_offset = eax & 0xff;
When AMD implements CPUID.0x1f.1:eax, will the offset be based on 24 or 44?
Seems it makes senses to be based on 44 because default counter width is 44.
> + else
> + c->x86_cache_mbm_width_offset =
> + MBM_CNTR_WIDTH_OFFSET_AMD;
If that's the case, you don't need this "else" because the CPUID reports
offset as 0 for default width 44.
This will match the Intel code above.
Otherwise, the code is awkward.
Thanks.
-Fenghua
next prev parent reply other threads:[~2020-06-01 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 23:00 Babu Moger
2020-06-01 23:23 ` Fenghua Yu [this message]
2020-06-02 14:30 ` Babu Moger
2020-06-02 17:13 ` Reinette Chatre
2020-06-02 17:33 ` Babu Moger
2020-06-02 21:59 ` Reinette Chatre
2020-06-02 21:51 ` Reinette Chatre
2020-06-02 22:12 ` Babu Moger
2020-06-02 23:28 ` Reinette Chatre
2020-06-03 15:04 ` Babu Moger
2020-07-01 22:13 Babu Moger
2020-07-07 14:04 ` Greg KH
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=20200601232318.GA57376@romley-ivt3.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.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®