From: Sean Christopherson <seanjc@google.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Like Xu <like.xu.linux@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH 0/2] x86/pmu: Add TSX testcase and fix force_emulation_prefix
Date: Wed, 5 Apr 2023 20:08:15 -0700 [thread overview]
Message-ID: <ZC43nyPWuZ6MdTjz@google.com> (raw)
In-Reply-To: <ZByPWH5ayCT25vbN@google.com>
On Thu, Mar 23, 2023, Sean Christopherson wrote:
> On Thu, Mar 23, 2023, Thomas Huth wrote:
> > On 14/02/2023 07.47, Like Xu wrote:
> > > CC more KUT maintainers, could anyone pick up these two minor x86 tests ?
> >
> > Your patches never made it to my inbox - I guess they got stuck in a mail
> > filter on the way ... Paolo, Sean, did you get them?
>
> Yeah, I have them. I'll prep a pull request, there are many KUT x86 patches
> floating around that need to get merged. Will likely take me a few days though.
Gah, forgot about this series. I'll plan on doing another pull request next week,
there are more outstanding KUT patches besides this one. And I'm finally diving
into KVM PMU stuff tomorrow, too.
next prev parent reply other threads:[~2023-04-06 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 7:54 [kvm-unit-tests PATCH 0/2] x86/pmu: Add TSX testcase and fix force_emulation_prefix Like Xu
2022-12-26 7:54 ` [kvm-unit-tests PATCH V2 1/2] x86/pmu: Add Intel Guest Transactional (commited) cycles testcase Like Xu
2022-12-26 7:54 ` [kvm-unit-tests PATCH RESEND 2/2] x86/pmu: Wrap the written counter value with gp_counter_width Like Xu
2023-02-14 6:47 ` [kvm-unit-tests PATCH 0/2] x86/pmu: Add TSX testcase and fix force_emulation_prefix Like Xu
2023-03-23 17:04 ` Thomas Huth
2023-03-23 17:41 ` Sean Christopherson
2023-04-06 3:08 ` Sean Christopherson [this message]
2023-06-07 23:25 ` Sean Christopherson
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=ZC43nyPWuZ6MdTjz@google.com \
--to=seanjc@google.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=pbonzini@redhat.com \
--cc=thuth@redhat.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).