From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Thiago Camargo Martins Cordeiro <thiagocmartinsc@gmail.com>
Cc: "J. Roeleveld" <joost@antarean.org>,
xen-devel@lists.xensource.com, keir.fraser@eu.citrix.com
Subject: Re: newer dom0 kernel / xen-unstable git kernel tree
Date: Tue, 22 Sep 2009 16:28:56 -0700 [thread overview]
Message-ID: <4AB95DB8.9020801@goop.org> (raw)
In-Reply-To: <6b7f6eb0909221626p48d1e7a7w5fe1dfaba54d02da@mail.gmail.com>
On 09/22/09 16:26, Thiago Camargo Martins Cordeiro wrote:
> Gotcha!
>
> To make use of the latest pv_ops dom0 need I the xen-unstable tree?
> Or can I use the Xen 3.4.1 / 3.3.2 from xen.org <http://xen.org>?
There's no close tie between dom0 and Xen itself; it should work with
any fairly recent version of Xen (and if it doesn't that's interesting
information).
J
next prev parent reply other threads:[~2009-09-22 23:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:05 newer dom0 kernel James Harper
2009-09-22 12:10 ` Pasi Kärkkäinen
2009-09-22 12:44 ` J. Roeleveld
2009-09-22 13:44 ` Pasi Kärkkäinen
2009-09-22 13:49 ` Thiago Camargo Martins Cordeiro
2009-09-22 13:59 ` newer dom0 kernel / xen-unstable git kernel tree Pasi Kärkkäinen
2009-09-22 23:26 ` Thiago Camargo Martins Cordeiro
2009-09-22 23:28 ` Jeremy Fitzhardinge [this message]
2009-09-23 6:52 ` Pasi Kärkkäinen
2009-09-23 6:57 ` Pasi Kärkkäinen
2009-09-23 8:46 ` James Harper
2009-09-23 8:59 ` Pasi Kärkkäinen
2009-09-23 9:01 ` James Harper
2009-09-23 11:19 ` Boris Derzhavets
2009-09-23 9:31 ` James Harper
2009-09-23 9:48 ` Pasi Kärkkäinen
2009-09-23 10:41 ` James Harper
2009-09-23 10:57 ` James Harper
2009-09-23 19:20 ` Jeremy Fitzhardinge
2009-09-24 2:56 ` James Harper
2009-09-23 19:19 ` Jeremy Fitzhardinge
2009-09-23 19:52 ` Jeremy Fitzhardinge
2009-09-23 19:59 ` Pasi Kärkkäinen
2009-09-23 20:12 ` Jeremy Fitzhardinge
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=4AB95DB8.9020801@goop.org \
--to=jeremy@goop.org \
--cc=joost@antarean.org \
--cc=keir.fraser@eu.citrix.com \
--cc=thiagocmartinsc@gmail.com \
--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 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.