From: Sean Christopherson <seanjc@google.com>
To: Dapeng Mi <dapeng1.mi@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Jim Mattson <jmattson@google.com>,
Mingwei Zhang <mizhang@google.com>,
Xiong Zhang <xiong.y.zhang@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Like Xu <like.xu.linux@gmail.com>,
Jinrong Liang <cloudliang@tencent.com>,
Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [PATCH 0/2] KVM vPMU code refine
Date: Thu, 20 Jun 2024 09:07:27 -0700 [thread overview]
Message-ID: <ZnRTv-dswVUr0hzZ@google.com> (raw)
In-Reply-To: <20240619182128.4131355-1-dapeng1.mi@linux.intel.com>
On Thu, Jun 20, 2024, Dapeng Mi wrote:
> This small patchset refines KVM vPMU code and relevant selftests.
> Patch 1/2 defines new macro KVM_PMC_MAX_GENERIC to avoid the Intel
> specific macro KVM_INTEL_PMC_MAX_GENERIC to be used in vPMU x86 common
> code. Patch 2/2 reduces the verbosity of "Random seed" messages to avoid
> the hugh number of messages to flood the regular output of selftests.
In the future, please post these as separate patches, they are completely unrelated.
next prev parent reply other threads:[~2024-06-20 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 18:21 [PATCH 0/2] KVM vPMU code refine Dapeng Mi
2024-06-19 18:21 ` [PATCH 1/2] KVM: x86/pmu: Define KVM_PMC_MAX_GENERIC for platform independence Dapeng Mi
2024-06-20 16:16 ` Sean Christopherson
2024-06-21 2:35 ` Mi, Dapeng
2024-06-21 13:48 ` Sean Christopherson
2024-06-19 18:21 ` [PATCH 2/2] selftests: kvm: Reduce verbosity of "Random seed" messages Dapeng Mi
2024-06-20 18:13 ` Sean Christopherson
2024-06-21 2:51 ` Mi, Dapeng
2024-06-21 13:29 ` Sean Christopherson
2024-06-26 1:57 ` Mi, Dapeng
2024-06-20 16:07 ` Sean Christopherson [this message]
2024-06-21 0:28 ` [PATCH 0/2] KVM vPMU code refine Mi, Dapeng
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=ZnRTv-dswVUr0hzZ@google.com \
--to=seanjc@google.com \
--cc=cloudliang@tencent.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--cc=pbonzini@redhat.com \
--cc=xiong.y.zhang@intel.com \
--cc=zhenyuw@linux.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 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.