From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
kvmarm@lists.linux.dev, Gavin Shan <gshan@redhat.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
pbonzini@redhat.com, shuah@kernel.org, maz@kernel.org,
oliver.upton@linux.dev, maciej.szmigiero@oracle.com,
shan.gavin@gmail.com
Subject: Re: [PATCH 0/2] KVM: selftests: Remove duplicate VM in memslot_perf_test
Date: Wed, 8 Feb 2023 02:07:26 +0000 [thread overview]
Message-ID: <167581358112.362323.5029488346682062350.b4-ty@google.com> (raw)
In-Reply-To: <20230118092133.320003-1-gshan@redhat.com>
On Wed, 18 Jan 2023 17:21:31 +0800, Gavin Shan wrote:
> PATCH[1] Removes the duplicate VM in memslot_perf_test
> PATCH[2] Assign guest page size in the sync area in prepare_vm()
>
> Gavin Shan (2):
> KVM: selftests: Remove duplicate VM in memslot_perf_test
> KVM: selftests: Assign guest page size in sync area early in
> memslot_perf_test
>
> [...]
Applied to kvm-x86 selftests, thanks!
[1/2] KVM: selftests: Remove duplicate VM in memslot_perf_test
https://github.com/kvm-x86/linux/commit/e5b426879fc3
[2/2] KVM: selftests: Assign guest page size in sync area early in memslot_perf_test
https://github.com/kvm-x86/linux/commit/45f679550d72
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
prev parent reply other threads:[~2023-02-08 2:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 9:21 [PATCH 0/2] KVM: selftests: Remove duplicate VM in memslot_perf_test Gavin Shan
2023-01-18 9:21 ` [PATCH 1/2] " Gavin Shan
2023-01-23 23:56 ` Maciej S. Szmigiero
2023-01-27 0:08 ` Gavin Shan
2023-01-18 9:21 ` [PATCH 2/2] KVM: selftests: Assign guest page size in sync area early " Gavin Shan
2023-01-23 23:57 ` Maciej S. Szmigiero
2023-02-08 2:07 ` Sean Christopherson [this message]
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=167581358112.362323.5029488346682062350.b4-ty@google.com \
--to=seanjc@google.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=maciej.szmigiero@oracle.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox