qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <paul.durrant@citrix.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v4 REPOST 2/2] Use ioreq-server API
Date: Wed, 3 Dec 2014 11:03:34 +0000	[thread overview]
Message-ID: <1417604616-6289-1-git-send-email-paul.durrant@citrix.com> (raw)

This patch series is a re-post v4 of what was originally the single
patch "Xen: Use the ioreq-server API when available". It was originally
posted on October 16th and pinged on October 29th. I am still awaiting
an ack/nack for patch #1, hence the re-post.

v2 of the series moved the code that added the PCI bus listener
to patch #1 and the remainder of the changes to patch #2. Patch #2
was then re-worked to constrain the #ifdefing to xen_common.h, as
requested by Stefano.

v3 of the series modifies patch #1 to add the listener interface
into the core qdev, rather than the PCI bus code. This change only
requires trivial modification to patch #2, to only act on realize/
unrealize of PCI devices. Patch #2 was also modified at Stefano's
request to remove an extra identity check of memory sections
against the ram region.

v4 of the series replaces the use of a vmstate pre_save callback
with extra code in the existing runstate change notification
callback. It also tidies up some things in xen-hvm.c pointed out
by Stefano and adds his ack to patch #2.

             reply	other threads:[~2014-12-03 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 11:03 Paul Durrant [this message]
2014-12-03 11:03 ` [Qemu-devel] [PATCH v4 REPOST 1/2] Add device listener interface Paul Durrant
2014-12-03 12:29   ` Stefano Stabellini
2014-12-03 13:40     ` Michael S. Tsirkin
2014-12-03 13:55       ` Paolo Bonzini
2014-12-03 14:11         ` Paul Durrant
2014-12-03 14:26     ` Andreas Färber
2014-12-05 10:28       ` Paul Durrant
2014-12-03 11:03 ` [Qemu-devel] [PATCH v4 REPOST 2/2] Xen: Use the ioreq-server API when available Paul Durrant

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=1417604616-6289-1-git-send-email-paul.durrant@citrix.com \
    --to=paul.durrant@citrix.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).