From: "Jan Beulich" <JBeulich@novell.com>
To: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Cc: xen-devel@lists.xensource.com
Subject: Re: status of PV drivers in Xen 4.0
Date: Tue, 30 Mar 2010 13:10:55 +0100 [thread overview]
Message-ID: <4BB2066F0200007800037CF2@vpn.id2.novell.com> (raw)
In-Reply-To: <4BB1E022.10108@inria.fr>
>>> Guillaume Rousse <Guillaume.Rousse@inria.fr> 30.03.10 13:27 >>>
>Le 30/03/2010 09:49, Jan Beulich a écrit :
>>>>> Pasi Kärkkäinen<pasik@iki.fi> 30.03.10 08:04 >>>
>>> Does anyone know if the 2.6.3x Novell xenified kernels have PV-on-HVM drivers?
>>
>> .32 certainly does (but still uses autoconf.h). .33/.34 likely weren't built
>> so far, but we will in any case fix this up once we get there.
>Just to be sure: does the suse xen kernel directly includes those
>additional modules, or is it rather a suitable tree for building them
>from xen packages ?
Both - they come pre-compiled in KMPs and the tree is also suitable
for building.
Jan
next prev parent reply other threads:[~2010-03-30 12:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:02 status of PV drivers in Xen 4.0 Guillaume Rousse
2010-03-30 6:04 ` Pasi Kärkkäinen
2010-03-30 7:49 ` Jan Beulich
2010-03-30 7:52 ` Pasi Kärkkäinen
2010-03-30 11:27 ` Guillaume Rousse
2010-03-30 12:10 ` Jan Beulich [this message]
2010-03-30 8:17 ` Guillaume Rousse
2010-03-30 10:04 ` Pasi Kärkkäinen
2010-04-05 16:50 ` Guillaume Rousse
2010-04-10 12:31 ` Andrew Lyon
2010-04-10 12:58 ` Pasi Kärkkäinen
2010-04-10 13:17 ` Andrew Lyon
2010-04-12 11:21 ` Pasi Kärkkäinen
2010-04-12 11:27 ` Guillaume Rousse
2010-04-12 15:40 ` Andrew Lyon
2010-04-12 15:50 ` Pasi Kärkkäinen
2010-04-12 16:05 ` Andrew Lyon
2010-04-12 16:51 ` Pasi Kärkkäinen
2010-04-20 16:16 ` Pasi Kärkkäinen
2010-04-20 16:52 ` Stefano Stabellini
2010-04-20 17:05 ` Pasi Kärkkäinen
2010-04-20 17:07 ` Stefano Stabellini
2010-04-13 21:35 ` Guillaume Rousse
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=4BB2066F0200007800037CF2@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Guillaume.Rousse@inria.fr \
--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).