From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
qemu-devel@nongnu.org, xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Qemu-devel] [PATCH v3] xen-hvm: ignore background I/O sections
Date: Wed, 25 May 2016 14:04:31 -0400 (EDT) [thread overview]
Message-ID: <46701863.17238471.1464199471397.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160525155232.GD1184@perard.uk.xensource.com>
----- Original Message -----
> From: "Anthony PERARD" <anthony.perard@citrix.com>
> To: "Paul Durrant" <paul.durrant@citrix.com>
> Cc: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org, "Stefano Stabellini" <sstabellini@kernel.org>, "Paolo
> Bonzini" <pbonzini@redhat.com>
> Sent: Wednesday, May 25, 2016 5:52:32 PM
> Subject: Re: [PATCH v3] xen-hvm: ignore background I/O sections
>
> On Mon, May 09, 2016 at 05:31:20PM +0100, Paul Durrant wrote:
> > Since Xen will correctly handle accesses to unimplemented I/O ports (by
> > returning all 1's for reads and ignoring writes) there is no need for
> > QEMU to register backgroud I/O sections.
> >
> > This patch therefore adds checks to xen_io_add/del so that sections with
> > memory-region ops pointing at 'unassigned_io_ops' are ignored.
> >
> > Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> > Cc: Stefano Stabellini <sstabellini@kernel.org>
> > Cc: Anthony Perard <anthony.perard@citrix.com>
> > Cc: Paolo Bonzini <pbonzini@redhat.com>
>
> Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Do you have a signed GPG key or do I need to apply this for you?
Thanks,
Paolo
next prev parent reply other threads:[~2016-05-25 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1462811480-16295-1-git-send-email-paul.durrant@citrix.com>
2016-05-25 15:52 ` [Qemu-devel] [PATCH v3] xen-hvm: ignore background I/O sections Anthony PERARD
2016-05-25 18:04 ` Paolo Bonzini [this message]
2016-05-26 9:09 ` Stefano Stabellini
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=46701863.17238471.1464199471397.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=paul.durrant@citrix.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).