From: Paul Durrant <Paul.Durrant@citrix.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>
Subject: Re: [Qemu-devel] [PATCH] xen-hvm: ignore background I/O sections
Date: Mon, 9 May 2016 16:40:08 +0000 [thread overview]
Message-ID: <a7f9f9aaadf74570b39b4769a27060b2@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <5730BD25.6060300@redhat.com>
> -----Original Message-----
> From: Paolo Bonzini [mailto:pbonzini@redhat.com]
> Sent: 09 May 2016 17:39
> To: Paul Durrant; qemu-devel@nongnu.org; xen-devel@lists.xenproject.org
> Cc: Stefano Stabellini; Anthony Perard
> Subject: Re: [PATCH] xen-hvm: ignore background I/O sections
>
>
>
> On 09/05/2016 18:18, 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>
> > ---
> > xen-hvm.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/xen-hvm.c b/xen-hvm.c
> > index 039680a..8ab44f0 100644
> > --- a/xen-hvm.c
> > +++ b/xen-hvm.c
> > @@ -510,8 +510,12 @@ static void xen_io_add(MemoryListener *listener,
> > MemoryRegionSection *section)
> > {
> > XenIOState *state = container_of(listener, XenIOState, io_listener);
> > + MemoryRegion *mr = section->mr;
> >
> > - memory_region_ref(section->mr);
> > + if (mr->ops == &unassigned_io_ops)
> > + return;
>
> Missing braces, same in xen_io_del. Otherwise looks ok.
>
Ah, sorry. Forgot to style-switch. Will post v2.
> Paolo
>
> > + memory_region_ref(mr);
> >
> > xen_map_io_section(xen_xc, xen_domid, state->ioservid, section);
> > }
> > @@ -520,10 +524,14 @@ static void xen_io_del(MemoryListener *listener,
> > MemoryRegionSection *section)
> > {
> > XenIOState *state = container_of(listener, XenIOState, io_listener);
> > + MemoryRegion *mr = section->mr;
> > +
> > + if (mr->ops == &unassigned_io_ops)
> > + return;
> >
> > xen_unmap_io_section(xen_xc, xen_domid, state->ioservid, section);
> >
> > - memory_region_unref(section->mr);
> > + memory_region_unref(mr);
> > }
> >
> > static void xen_device_realize(DeviceListener *listener,
> >
prev parent reply other threads:[~2016-05-09 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:18 [Qemu-devel] [PATCH] xen-hvm: ignore background I/O sections Paul Durrant
2016-05-09 16:39 ` Paolo Bonzini
2016-05-09 16:40 ` 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=a7f9f9aaadf74570b39b4769a27060b2@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.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).