From: Peter Xu <peterx@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] KVM: selftests: Allow specify physical cpu list in demand paging test
Date: Wed, 7 Jun 2023 09:27:43 -0400 [thread overview]
Message-ID: <ZICFz6khhyBjsMiS@x1n> (raw)
In-Reply-To: <20230607001226.1398889-1-seanjc@google.com>
On Tue, Jun 06, 2023 at 05:12:26PM -0700, Sean Christopherson wrote:
> From: Peter Xu <peterx@redhat.com>
>
> Mimic the dirty log test and allow the user to pin demand paging test
> tasks to physical CPUs.
>
> Put the help message into a general helper as suggested by Sean.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> Link: https://lore.kernel.org/r/20230601184256.180413-1-peterx@redhat.com
> [sean: rebase, tweak arg ordering, add "print" to helper, print program name]
> Signed-off-by: Sean Christopherson <seanjc@google.com>
Thanks, Sean!
--
Peter Xu
prev parent reply other threads:[~2023-06-07 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 0:12 [PATCH v3] KVM: selftests: Allow specify physical cpu list in demand paging test Sean Christopherson
2023-06-07 0:54 ` Sean Christopherson
2023-06-07 13:27 ` Peter Xu [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=ZICFz6khhyBjsMiS@x1n \
--to=peterx@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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