From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] KVM: x86: Rep string I/O WARN removal and test
Date: Mon, 25 Oct 2021 13:13:09 -0700 [thread overview]
Message-ID: <20211025201311.1881846-1-seanjc@google.com> (raw)
Remove a WARN that was added as part of the recent I/O overhaul to play
nice with SEV-ES string I/O.
For the record, my FIXME in lieu of a WARN was deliberate, as I suspected
userspace could trigger a WARN ;-)
Based on kvm/master, commit 95e16b4792b0 ("KVM: SEV-ES: go over the
sev_pio_data buffer in multiple passes if needed").
Sean Christopherson (2):
KVM: x86: Don't WARN if userspace mucks with RCX during string I/O
exit
KVM: selftests: Add test to verify KVM doesn't explode on "bad" I/O
arch/x86/kvm/x86.c | 9 +-
tools/testing/selftests/kvm/.gitignore | 1 +
tools/testing/selftests/kvm/Makefile | 1 +
.../selftests/kvm/x86_64/userspace_io_test.c | 114 ++++++++++++++++++
4 files changed, 123 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/kvm/x86_64/userspace_io_test.c
--
2.33.0.1079.g6e70778dc9-goog
next reply other threads:[~2021-10-25 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 20:13 Sean Christopherson [this message]
2021-10-25 20:13 ` [PATCH 1/2] KVM: x86: Don't WARN if userspace mucks with RCX during string I/O exit Sean Christopherson
2021-10-25 20:13 ` [PATCH 2/2] KVM: selftests: Add test to verify KVM doesn't explode on "bad" I/O Sean Christopherson
2021-12-09 5:48 ` [PATCH 0/2] KVM: x86: Rep string I/O WARN removal and test Sean Christopherson
2021-12-09 11:22 ` Paolo Bonzini
2021-12-09 15:50 ` 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=20211025201311.1881846-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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).