qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH v4 0/2] Use ioreq-server API
@ 2014-10-16 12:11 Paul Durrant
  2014-10-16 12:11 ` [Qemu-devel] [PATCH v4 1/2] Add device listener interface Paul Durrant
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Paul Durrant @ 2014-10-16 12:11 UTC (permalink / raw)
  To: qemu-devel, xen-devel

This patch series is v4 of what was originally the single patch
"Xen: Use the ioreq-server API when available".

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-10-29 14:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-16 12:11 [Qemu-devel] [PATCH v4 0/2] Use ioreq-server API Paul Durrant
2014-10-16 12:11 ` [Qemu-devel] [PATCH v4 1/2] Add device listener interface Paul Durrant
2014-10-16 12:11 ` [Qemu-devel] [PATCH v4 2/2] Xen: Use the ioreq-server API when available Paul Durrant
2014-10-29 14:54 ` [Qemu-devel] [Xen-devel] [PATCH v4 0/2] Use ioreq-server API Paul Durrant

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).