This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] full featured, fully bug-fix pv-ops branch?

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Subject: [Xen-devel] full featured, fully bug-fix pv-ops branch?
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 09 May 2011 13:16:11 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 May 2011 05:16:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Jeremy, Konrad,

stumbling over this once in a while (this time looking for where Dominic's
"blktap: Fix reference to freed struct request" patch ended up, without
any success so far) I wonder what pv-ops branch(es) is (are) supposed
to be the one(s) (e.g.) distros ought to use - that is, fully featured (at
least as far as non-experimental features go) *and* fully bug-fixed.

The branches XenParavirtOps on the wiki points to don't seem to be the
ones (some of them seem not to have a blktap implementation at all),
and gathering bits from various people's private trees can't be the
ultimate solution...

Thanks, Jan

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>