From: Paul Durrant <Paul.Durrant@citrix.com>
To: Anthony Perard <anthony.perard@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] xen-hvm: use new resource mapping API
Date: Mon, 14 May 2018 09:38:57 +0000 [thread overview]
Message-ID: <d912b54af4c141b990782912cf237ed9@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20180510091518.28199-1-paul.durrant@citrix.com>
Anthony, Stefano,
Ping?
I'd like to get your feedback before spinning a v3 to incorporate Eric's suggestion regarding the commit comment for #2.
Paul
> -----Original Message-----
> From: Paul Durrant [mailto:paul.durrant@citrix.com]
> Sent: 10 May 2018 10:15
> 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: [PATCH v2 0/2] xen-hvm: use new resource mapping API
>
> 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 | 114 ++++++++++++++++++++++++++++++++-
> -----------
> include/hw/xen/xen_common.h | 14 ++++++
> 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
prev parent reply other threads:[~2018-05-14 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 9:15 [Qemu-devel] [PATCH v2 0/2] xen-hvm: use new resource mapping API Paul Durrant
2018-05-10 9:15 ` [Qemu-devel] [PATCH v2 1/3] xen-hvm: create separate function for ioreq server initialization Paul Durrant
2018-05-15 14:40 ` Anthony PERARD
2018-05-10 9:15 ` [Qemu-devel] [PATCH v2 2/3] checkpatch: generalize xen handle matching in the list of types Paul Durrant
2018-05-10 13:26 ` Eric Blake
2018-05-10 9:15 ` [Qemu-devel] [PATCH v2 3/3] xen-hvm: try to use xenforeignmemory_map_resource() to map ioreq pages Paul Durrant
2018-05-15 15:38 ` Anthony PERARD
2018-05-15 15:45 ` Paul Durrant
2018-05-15 16:16 ` Anthony PERARD
2018-05-15 16:26 ` Paul Durrant
2018-05-15 16:42 ` Eric Blake
2018-05-14 9:38 ` Paul Durrant [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=d912b54af4c141b990782912cf237ed9@AMSPEX02CL03.citrite.net \
--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).