From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: konrad.wilk@oracle.com,
xen-devel <xen-devel@lists.xenproject.org>,
ian.jackson@eu.citrix.com, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Xen 4.5-rc2 post update (RC2 was out 2014-Nov-11th)
Date: Fri, 21 Nov 2014 13:28:52 -0500 [thread overview]
Message-ID: <546F8464.5000906@oracle.com> (raw)
In-Reply-To: <20141121174212.0FF83118AA5@laptop.dumpdata.com>
(Followup list trimmed)
On 11/21/2014 12:42 PM, konrad.wilk@oracle.com wrote:
>
> = Open =
>
> == Known issues ==
>
> * xc_reserved_device_memory_map in hvmloader to avoid conflicting MMIO/RAM (good)
> RFC v6
> Treating pieces as bug-fixes only.
> - Tiejun Chen
>
> * PCI passthrough of INTx legacy devices can trigger list corruption (good)
> Sander reported it. Two different types of patches available.
> - Konrad Rzeszutek Wilk
>
> * pygrub does not handle certain configurations. (fair)
> an RFC patch posted.
> - Andrew Cooper
There is a regression in libxl's bitmap handling during a restore. I
need libxl maintainers to decide which of the two suggested ways to fix
it I should use. Both are fairly trivial.
There is also a bug in libxl's PCI detach code. In fact, two bugs, both
related to a race between libxl, qemu and guest. IanJ suggested a simple
patch for one (which, in fact, fixes a regression) but the second bug
will probably take me a while (need to make detaching call chain
asynchronous).
> == Linux ==
>
>
> * vAPIC in PVHVM guests (Linux side) (none)
> - Boris Ostrovsky
This, I believe, is queued for 3.19.
boris
next prev parent reply other threads:[~2014-11-21 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 17:42 Xen 4.5-rc2 post update (RC2 was out 2014-Nov-11th) konrad.wilk
2014-11-21 17:54 ` Don Slutz
2014-11-21 18:02 ` Konrad Rzeszutek Wilk
2014-11-21 18:28 ` Boris Ostrovsky [this message]
2014-11-24 16:20 ` Is: Slip. RC3 out to Dec 3rd. Was:Re: " Konrad Rzeszutek Wilk
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=546F8464.5000906@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.