From: John Andersen <john.s.andersen@intel.com>
To: pbonzini@redhat.com, kvm@vger.kernel.org
Cc: John Andersen <john.s.andersen@intel.com>
Subject: [PATCH 0/1] Paravirtualized control register pinning test
Date: Wed, 19 Feb 2020 10:04:35 -0800 [thread overview]
Message-ID: <20200219180436.6580-1-john.s.andersen@intel.com> (raw)
This is the corresponding test for
https://lore.kernel.org/kvm/20200218215902.5655-1-john.s.andersen@intel.com/T/#t
Thank you!
John Andersen (1):
x86: Add control register pinning test
x86/Makefile.common | 3 +-
lib/x86/desc.h | 1 +
lib/x86/processor.h | 1 +
lib/x86/desc.c | 8 +++
x86/cr_pin.c | 163 ++++++++++++++++++++++++++++++++++++++++++++
x86/pcid.c | 8 ---
x86/unittests.cfg | 4 ++
7 files changed, 179 insertions(+), 9 deletions(-)
create mode 100644 x86/cr_pin.c
--
2.21.0
next reply other threads:[~2020-02-19 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:04 John Andersen [this message]
2020-02-19 18:04 ` [PATCH 1/1] x86: Add control register pinning test John Andersen
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=20200219180436.6580-1-john.s.andersen@intel.com \
--to=john.s.andersen@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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).