From: Paolo Bonzini <pbonzini@redhat.com>
To: Amey Narkhede <ameynarkhede03@gmail.com>, qemu-devel@nongnu.org
Cc: Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/2] KVM: Introduce ioeventfd read support
Date: Sat, 31 Oct 2020 15:33:42 +0100 [thread overview]
Message-ID: <8014bc56-78fd-47f5-e62c-b8f6444f45bc@redhat.com> (raw)
In-Reply-To: <20201020170056.433528-1-ameynarkhede03@gmail.com>
On 20/10/20 19:00, Amey Narkhede wrote:
> The first patch updates linux headers to
> add ioeventfd read support while the
> second patch can be used to test the
> ioeventfd read feature with kvm-unit-test
> which reads from specified guest addres.
> Make sure the address provided in
> kvm_set_ioeventfd_read matches with address
> in x86/ioeventfd_read test in kvm-unit-tests.
>
> Amey Narkhede (2):
> linux-headers: Add support for reads in ioeventfd
> kvm: Add ioeventfd read test code
>
> accel/kvm/kvm-all.c | 55 +++++++++++++++++++++++++++++++++++++++
> linux-headers/linux/kvm.h | 5 +++-
> 2 files changed, 59 insertions(+), 1 deletion(-)
>
Hi,
in what occasions is this useful?
Paolo
prev parent reply other threads:[~2020-10-31 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 17:00 [PATCH 0/2] KVM: Introduce ioeventfd read support Amey Narkhede
2020-10-20 17:00 ` [PATCH 1/2] linux-headers: Add support for reads in ioeventfd Amey Narkhede
2020-10-20 17:00 ` [PATCH 2/2] kvm: Add ioeventfd read test code Amey Narkhede
2020-10-20 17:09 ` [PATCH 0/2] KVM: Introduce ioeventfd read support no-reply
2020-10-20 17:19 ` Amey Narkhede
2020-10-31 14:33 ` 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=8014bc56-78fd-47f5-e62c-b8f6444f45bc@redhat.com \
--to=pbonzini@redhat.com \
--cc=ameynarkhede03@gmail.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).