From: Paolo Bonzini <pbonzini@redhat.com>
To: Arbel Moshe <arbel.moshe@oracle.com>,
rkrcmar@redhat.com, kvm@vger.kernel.org
Cc: idan.brown@oracle.com, liran.alon@oracle.com
Subject: Re: [kvm-unit-test PATCH 0/5]: x86: Add tests for VMware backdoor
Date: Wed, 14 Feb 2018 13:06:33 +0100 [thread overview]
Message-ID: <9de44cf2-33f1-c283-be25-27925e960a2d@redhat.com> (raw)
In-Reply-To: <20171224100801.145806-1-arbel.moshe@oracle.com>
On 24/12/2017 11:07, Arbel Moshe wrote:
> Hi,
> This series adds a set of unit tests to series:
> "KVM: x86: Add support for VMware backdoor I/O ports & Pseduo-PMCs"
>
> The series is split into the following patches:
> 1. Add an x86 utility to run a function in User Mode.
> 2. Add a test utility to run a function in User Mode / Kernel Mode, catch an
> exception, and run a callback to test function return value.
> 3. Add CR4 PCE bit definition.
> 4. Add x86_64 segment descriptor struct.
> 5. Add VMware backdoor tests:
> Test VMware port and VMware RDPMC backdoors, both in user mode and kernel
> mode.
Looks good, thanks. I'll shortly review the kernel parts too.
Paolo
prev parent reply other threads:[~2018-02-14 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 10:07 [kvm-unit-test PATCH 0/5]: x86: Add tests for VMware backdoor Arbel Moshe
2017-12-24 10:07 ` [PATCH 1/5] x86: Add utility to run function in User Mode Arbel Moshe
2017-12-24 10:07 ` [PATCH 2/5] x86: Add Test Utility to run in User Mode and catch exceptions Arbel Moshe
2017-12-24 10:07 ` [PATCH 3/5] x86: Add Definition for PCE bit in CR4 Arbel Moshe
2017-12-24 10:08 ` [PATCH 4/5] x86: Add definition for 64 bit Segment descriptor Arbel Moshe
2017-12-24 10:08 ` [PATCH 5/5] x86: Add VMware backdoor unit test Arbel Moshe
2018-02-14 12:06 ` Paolo Bonzini [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=9de44cf2-33f1-c283-be25-27925e960a2d@redhat.com \
--to=pbonzini@redhat.com \
--cc=arbel.moshe@oracle.com \
--cc=idan.brown@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=rkrcmar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.