From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] x86/intel: ensure Global Performance Counter Control is setup correctly
Date: Thu, 11 Jan 2024 15:15:57 +0100 [thread overview]
Message-ID: <ZZ_4HSvdg0R9Dv1Y@macbook> (raw)
In-Reply-To: <b1e76a5f-297b-4030-a69e-33cdf179c0ce@suse.com>
On Thu, Jan 11, 2024 at 03:01:01PM +0100, Jan Beulich wrote:
> On 11.01.2024 13:22, Roger Pau Monné wrote:
> > Oh, indeed, can adjust on this same patch if that's OK (seeing as the
> > issue was already there previous to my change).
>
> Well, I'm getting the impression that it was deliberate there, i.e. set
> setting of the feature flag may want to remain thus constrained.
Hm, I find it weird, but the original commit message doesn't help at
all. Xen itself only uses PMC0, and I don't find any other
justification in the current code to require at least 2 counters in
order to expose arch performance monitoring to be present.
Looking at the SDM vol3, the figures there only contain PMC0 and PMC1,
so someone only reading that manual might assume there must always be
2 global PMCs?
(vol4 clarifies the that the number of global PMCs is variable).
Thanks, Roger.
next prev parent reply other threads:[~2024-01-11 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 9:08 [PATCH v2] x86/intel: ensure Global Performance Counter Control is setup correctly Roger Pau Monne
2024-01-11 10:00 ` Jan Beulich
2024-01-11 10:32 ` Roger Pau Monné
2024-01-11 10:38 ` Jan Beulich
2024-01-11 10:11 ` Jan Beulich
2024-01-11 10:40 ` Roger Pau Monné
2024-01-11 11:34 ` Jan Beulich
2024-01-11 12:22 ` Roger Pau Monné
2024-01-11 14:01 ` Jan Beulich
2024-01-11 14:15 ` Roger Pau Monné [this message]
2024-01-11 15:52 ` Jan Beulich
2024-01-11 16:53 ` Roger Pau Monné
2024-01-12 7:42 ` Jan Beulich
2024-01-12 10:08 ` Roger Pau Monné
2024-01-12 10:19 ` Jan Beulich
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=ZZ_4HSvdg0R9Dv1Y@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.