From: Zhao Liu <zhao1.liu@intel.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, pbonzini@redhat.com,
mtosatti@redhat.com, sandipan.das@amd.com, babu.moger@amd.com,
likexu@tencent.com, like.xu.linux@gmail.com, groug@kaod.org,
khorenko@virtuozzo.com, alexander.ivanov@virtuozzo.com,
den@virtuozzo.com, davydov-max@yandex-team.ru,
xiaoyao.li@intel.com, dapeng1.mi@linux.intel.com,
joe.jin@oracle.com, ewanhai-oc@zhaoxin.com, ewanhai@zhaoxin.com
Subject: Re: [PATCH v7 2/9] target/i386: disable PERFCORE when "-pmu" is configured
Date: Tue, 25 Nov 2025 11:47:39 +0800 [thread overview]
Message-ID: <aSUm22dRG6dczdkp@intel.com> (raw)
In-Reply-To: <077866b9-eaa2-4671-bb96-6c6776d0f72b@oracle.com>
> Please let me know whether you would like to include Patch 2 on
> "amd_perfmon_always_on" as part of the "compat_prop" patch, or if you'd prefer
> that I re-create Patch 2 with your Suggested-by.
>
> Either option works for me.
I took some time to revisit the dependency issues with PDCM again, and I
do think the approach mentioned in previous reply should work.
Ok, let me pick your patch 1 & 2. I will rebase these on the CET series
(since I've also modified the dependency for Arch LBR). The entire
dependency fix series may take some time and may need to wait for
several weeks.
However, at least it's decoupled from the rest. :)
At the same time, I'll help go through the remaining patches 3-9 again,
as it's been quite a while since I last reviewed them.
> It seems the Patches 3 - 9 are not impacted by this Live Migration issue.
> Perhaps they may be accepted (or as well as Patch 2 "amd_perfmon_always_on")
> without "compat_prop" patch? They are independent with each other.
Yes, I think so.
> Another concern is Patch 3. Something unexpected may occur when live migrating
> from a KVM host without KVM_PMU_CAP_DISABLE to one that has it enabled. The
> migration will succeed, but the perceived perf/vPMU support could change.
> Can we assume it is the user's responsibility to ensure compatibility between
> KVM hosts when "-pmu" is specified?
Yes, I think so, too. I understand that QEMU needs to ensure vmstate
migration compatibility.
Thanks,
Zhao
next prev parent reply other threads:[~2025-11-25 3:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 6:14 [PATCH v7 0/9] target/i386/kvm/pmu: PMU Enhancement, Bugfix and Cleanup Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 1/9] target/i386: disable PerfMonV2 when PERFCORE unavailable Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 2/9] target/i386: disable PERFCORE when "-pmu" is configured Dongli Zhang
2025-11-19 11:06 ` Zhao Liu
2025-11-20 0:22 ` Dongli Zhang
2025-11-25 3:47 ` Zhao Liu [this message]
2025-11-11 6:14 ` [PATCH v7 3/9] target/i386/kvm: set KVM_PMU_CAP_DISABLE if " Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 4/9] target/i386/kvm: extract unrelated code out of kvm_x86_build_cpuid() Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 5/9] target/i386/kvm: rename architectural PMU variables Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 6/9] target/i386/kvm: query kvm.enable_pmu parameter Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 7/9] target/i386/kvm: reset AMD PMU registers during VM reset Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 8/9] target/i386/kvm: support perfmon-v2 for reset Dongli Zhang
2025-11-11 6:14 ` [PATCH v7 9/9] target/i386/kvm: don't stop Intel PMU counters Dongli Zhang
2025-11-19 2:07 ` [PATCH v7 0/9] target/i386/kvm/pmu: PMU Enhancement, Bugfix and Cleanup Dongli Zhang
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=aSUm22dRG6dczdkp@intel.com \
--to=zhao1.liu@intel.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=babu.moger@amd.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=davydov-max@yandex-team.ru \
--cc=den@virtuozzo.com \
--cc=dongli.zhang@oracle.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=groug@kaod.org \
--cc=joe.jin@oracle.com \
--cc=khorenko@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=likexu@tencent.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sandipan.das@amd.com \
--cc=xiaoyao.li@intel.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;
as well as URLs for NNTP newsgroup(s).