From: Gerd Hoffmann <kraxel@redhat.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 1/2] xenner: add event channel implementation.
Date: Tue, 26 Aug 2008 10:27:52 +0200 [thread overview]
Message-ID: <48B3BE88.8090003@redhat.com> (raw)
In-Reply-To: <C4D8BBAC.1C758%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> We'll certainly be sync'ing with upstream qemu now, yes. I'm not sure what
> Ian Jackson's plans are with regard to Gerd's patches. I think he was hoping
> that Gerd would post patches to xen-devel against his tree (being an
> existing and actively maintained and tested Xen patchset) and then we would
> from there submit to upstream.
There are two patchsets out there:
#1 for upstream qemu:
http://kraxel.fedorapeople.org/patches/qemu-upstream/
#2 for qemu-xen:
http://kraxel.fedorapeople.org/patches/qemu-xen/
The patchsets are largely identical, thats why I don't post both.
I usually post only the upstream version and include a pointer to the
qemu-xen patches in the intro text for the patchset.
Differences come (a) from the fact that qemu-xen is old (these should go
away once Ian synced with upstream) and (b) the slightly different
ordering to make the qemu-xen patchset bisection-friendly.
> Afaics there's some workflow or patchflow to
> be worked out here:
Workflow could look like this:
(1) Ian merges upstream into qemu-xen.
(2) I'll rebase my patches to the resulting tree.
(3) Merge both patchsets, into the trees.
That should result in almost identical hw/xen* files in both trees, so
we don't end up with a big mess when Ian merges again.
> I can't see why we would take Gerd's patches wholesale
> when we have a working patchset already.
Which patchset you are refering to? As far I know Ian & Samuel are
focusing on getting the changes to generic qemu code upstream (such as
serial and ide fixes which ran over the qemu-devel list already), not on
the xen support bits.
cheers,
Gerd
next prev parent reply other threads:[~2008-08-26 8:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 10:25 [Qemu-devel] [PATCH 0/2] RfC: xenner (aka xen emulation) bits Gerd Hoffmann
2008-08-22 10:25 ` [Qemu-devel] [PATCH 1/2] xenner: add event channel implementation Gerd Hoffmann
2008-08-22 13:46 ` Anthony Liguori
2008-08-22 15:04 ` Gerd Hoffmann
2008-08-25 12:58 ` Gerd Hoffmann
2008-08-25 14:15 ` Anthony Liguori
2008-08-25 15:12 ` [Xen-devel] " Keir Fraser
2008-08-25 17:57 ` Anthony Liguori
2008-08-25 18:42 ` Keir Fraser
2008-08-26 8:27 ` Gerd Hoffmann [this message]
2008-08-26 8:40 ` Keir Fraser
2008-08-26 8:39 ` Daniel P. Berrange
2008-08-22 10:25 ` [Qemu-devel] [PATCH 2/2] xenner: use evtchn function pointers in the backends Gerd Hoffmann
[not found] ` <m2n.s.1KWU8S-002Pyj@chiark.greenend.org.uk>
2008-08-26 11:02 ` [Qemu-devel] [PATCH 1/2] xenner: add event channel implementation Ian Jackson
2008-08-26 13:13 ` Gerd Hoffmann
2008-08-26 13:28 ` Ian Jackson
2008-08-26 19:34 ` Gerd Hoffmann
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=48B3BE88.8090003@redhat.com \
--to=kraxel@redhat.com \
--cc=keir.fraser@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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).