From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xen.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Upstream Qemu Status (Was: Re: 4.2 TODO / Release Status)
Date: Tue, 8 May 2012 10:06:30 -0500 [thread overview]
Message-ID: <CAP8mzPOnSKR7k5qBPpNNLkdJ6eb3gcsWMO2p1LYP35oyyJvv8Q@mail.gmail.com> (raw)
In-Reply-To: <1336489170.13218.11.camel@cthulhu.hellion.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1664 bytes --]
On Tue, May 8, 2012 at 9:59 AM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
> On Tue, 2012-05-08 at 10:54 -0400, Stefano Stabellini wrote:
> > On Tue, 8 May 2012, Ian Campbell wrote:
> > > Where are we with the following?
> > >
> > > I've not seen anything recently about PCI passthrough.
> >
> > The last patch series that was sent is:
> >
> > http://marc.info/?l=qemu-devel&m=133346733411606&w=2
> >
> > it is still stuck waiting for reviews. Given that QEMU is in freeze for
> > the next release release now, I don't think anything is going to happen
> > in the next few weeks.
> > I could backport the patch series to the upstream QEMU tree that we use
> > with xen-unstable, but considering that we are in freeze ourselves and
> > that upstream QEMU is not used by default with HVM guests we
> > might as well wait for the beginning of the next release cycle.
>
> Thanks. I will mark these as "deferred to 4.3" and remove from the list.
> If they do go into upstream we can revisit whether we backport.
>
> > > Is it still the case that save/restore is waiting on lib{c,l} patches
> > > and Remus is waiting for those? What's the hold up there?
> >
> > The libxl save/restore patches haven't been applied yet.
>
> Ian J -- have you dropped these or are you waiting for something?
>
>
>
Ian J, also note that the remus libxl patches may not apply cleanly after
applying stefano's patches (even these might require some re-basing),
given that a lot of patches that came in later (the event based stuff, Ian
C's refactorings,etc)
went in.
If you could just let me know when they have been committed, I can
certainly
rebase mine and post them.
thanks
shriram
[-- Attachment #1.2: Type: text/html, Size: 2426 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-08 15:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 9:34 4.2 TODO / Release Status Ian Campbell
2012-05-08 10:32 ` Ian Campbell
2012-05-08 10:39 ` George Dunlap
2012-05-08 10:43 ` Ian Campbell
2012-05-08 10:42 ` Ian Campbell
2012-05-08 10:45 ` sched params spurious error message (Was: Re: 4.2 TODO / Release Status) Ian Campbell
2012-05-08 10:56 ` Dieter Bloms
2012-05-08 12:35 ` George Dunlap
2012-05-08 12:50 ` Ian Campbell
2012-05-08 10:47 ` Volunteer wanted: xl and empty HVM CD ROM drives " Ian Campbell
2012-05-08 10:52 ` Upstream Qemu Status " Ian Campbell
2012-05-08 12:45 ` Shriram Rajagopalan
2012-05-08 14:54 ` Stefano Stabellini
2012-05-08 14:59 ` Ian Campbell
2012-05-08 15:06 ` Shriram Rajagopalan [this message]
2012-05-09 13:42 ` Ian Jackson
2012-05-10 10:18 ` Extra libxl committer? (Was: Re: Upstream Qemu Status (Was: Re: 4.2 TODO / Release Status)) Ian Campbell
2012-05-10 10:46 ` Stefano Stabellini
2012-05-10 11:20 ` Ian Jackson
2012-05-14 8:56 ` Upstream Qemu Status (Was: Re: 4.2 TODO / Release Status) Ian Campbell
2012-05-08 14:09 ` 4.2 TODO / Release Status Bastian Blank
2012-05-08 14:38 ` Ian Campbell
2012-05-08 15:11 ` Bastian Blank
2012-05-08 15:23 ` Ian Campbell
2012-05-08 15:16 ` Olaf Hering
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=CAP8mzPOnSKR7k5qBPpNNLkdJ6eb3gcsWMO2p1LYP35oyyJvv8Q@mail.gmail.com \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=xen-devel@lists.xen.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).