From: Paul Durrant <paul.durrant@citrix.com>
To: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org
Cc: Paul Durrant <paul.durrant@citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [Qemu-devel] [PATCH v3 0/3] xen-hvm: use new resource mapping API
Date: Tue, 15 May 2018 17:40:50 +0100 [thread overview]
Message-ID: <20180515164053.14604-1-paul.durrant@citrix.com> (raw)
This series modifies QEMU to use the new guest resource mapping API
(available in Xen 4.11+) to map ioreq pages.
v2:
- Add a patch to checkpatch to avoid misparsing of Xen stable API handles
Paul Durrant (3):
xen-hvm: create separate function for ioreq server initialization
checkpatch: generalize xen handle matching in the list of types
xen-hvm: try to use xenforeignmemory_map_resource() to map ioreq pages
configure | 5 ++
hw/i386/xen/trace-events | 1 +
hw/i386/xen/xen-hvm.c | 112 ++++++++++++++++++++++++++++++++------------
include/hw/xen/xen_common.h | 16 +++++++
scripts/checkpatch.pl | 2 +-
5 files changed, 105 insertions(+), 31 deletions(-)
---
Cc: Anthony Perard <anthony.perard@citrix.com>
Cc: Daniel P. Berrange <berrange@redhat.com>
Cc: Eric Blake <eblake@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>
--
2.11.0
next reply other threads:[~2018-05-15 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 16:40 Paul Durrant [this message]
2018-05-15 16:40 ` [Qemu-devel] [PATCH v3 1/3] xen-hvm: create separate function for ioreq server initialization Paul Durrant
2018-05-15 16:40 ` [Qemu-devel] [PATCH v3 2/3] checkpatch: generalize xen handle matching in the list of types Paul Durrant
2018-05-15 16:40 ` [Qemu-devel] [PATCH v3 3/3] xen-hvm: try to use xenforeignmemory_map_resource() to map ioreq pages Paul Durrant
2018-05-18 10:17 ` Anthony PERARD
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=20180515164053.14604-1-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).