public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-qemu] parse-cpu-flags: stop filtering out 'pmu'
Date: Tue, 13 Oct 2026 11:21:58 +0200	[thread overview]
Message-ID: <fecye2iqh5fgyftylljarhnunlbqshxmtcmcrtpxuqmns6nvz3@jrkwb6nmlnpq> (raw)
In-Reply-To: <3cde24de-d79f-424c-b779-c0e22140faec@proxmox.com>

On Tue, Oct 13, 2026 at 11:19:11AM +0200, Fiona Ebner wrote:
> Am 13.10.26 um 10:32 AM schrieb Arthur Bied-Charreton:
> > 'pmu' was excluded from the list of flags in the custom CPU flag dialog
> > because it is not a CPUID flag (not part of '-cpu help' output).
> > However, it is a plain boolean property so it fits the [+-]<flag> syntax
> > from the custom CPU config, and QEMU accepts it when set manually via
> > '+pmu'.
> 
> What I wanted to write: if it's not a CPUID flag, wouldn't it be better
> to expose it as a separate property? I.e. add to the $cpu_fmt schema and
> have a separate checkbox in the UI?
> 
> But then I looked into the implementation and the 'pmu' property is very
> closely related to the CPUID_EXT_PDCM flag, so it makes a lot of sense
> if it goes through the same "on which nodes is it supported" checks and
> if we treat it as a flag.
> 
> Could you adapt the commit message to reflect this? IMHO the argument
> with QEMU accepting the same syntax is rather weak. There has to be
> conceptual similarity too, which there is :)
> 
fair enough, will adapt the message. thanks for looking into it!
> > 
> > Windows guests using VBS need a virtual PMU, which is not enabled by
> > default on many models (EPYC-Turin, EPYC-Genoa, SapphireRapids, and
> > presumably others I have not tested). This currently requires users to
> > edit the config by hand since the flag cannot be selected in the UI.
> > 
> > Remove 'pmu' from the blacklist so it shows up in the generated flag
> > list.
> > 
> > Reported-by: David Riley <d.riley@proxmox.com>
> > Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
> > ---
> >  debian/parse-cpu-flags.pl | 1 -
> >  1 file changed, 1 deletion(-)
> > 
> > diff --git a/debian/parse-cpu-flags.pl b/debian/parse-cpu-flags.pl
> > index e680f99..e1af0e8 100755
> > --- a/debian/parse-cpu-flags.pl
> > +++ b/debian/parse-cpu-flags.pl
> > @@ -66,7 +66,6 @@ my $filtered_props = {
> >          'legacy-multi-node' => 1,
> >          lmce => 1,
> >          migratable => 1,
> > -        pmu => 1,
> >          realized => 1,
> >          'start-powered-off' => 1,
> >          'tcg-cpuid' => 1,
> 
> Note: you also need to add it to debian/recognized-CPUID-flags-x86_64
I somehow completely forgot, thanks for noticing :)




  reply	other threads:[~2026-10-13  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  8:31 [PATCH pve-qemu] parse-cpu-flags: stop filtering out 'pmu' Arthur Bied-Charreton
2026-10-13  9:19 ` Fiona Ebner
2026-10-13  9:21   ` Arthur Bied-Charreton [this message]
2026-10-13  9:53 ` superseded: " Arthur Bied-Charreton

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=fecye2iqh5fgyftylljarhnunlbqshxmtcmcrtpxuqmns6nvz3@jrkwb6nmlnpq \
    --to=a.bied-charreton@proxmox.com \
    --cc=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal