From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: Re: status of PV drivers in Xen 4.0
Date: Mon, 05 Apr 2010 18:50:46 +0200 [thread overview]
Message-ID: <4BBA14E6.70208@inria.fr> (raw)
In-Reply-To: <20100330060411.GT1878@reaktio.net>
Le 30/03/2010 08:04, Pasi Kärkkäinen a écrit :
> On Mon, Mar 29, 2010 at 11:02:09PM +0200, Guillaume Rousse wrote:
>> Hello.
>>
>> The directory 'unmodified_drivers', in Xen-4.0rc8, seems to still
>> requires a 2.6.18 XenLinux kernel to build. For instance, overrides.mk
>> still refers to $(objtree)/include/linux/autoconf.h, instead of
>> $(objtree)/include/generated/autoconf.h in recent kernels.
>>
>
> I believe it should compile with 2.6.27 aswell.. or if it doesn't,
> please let us know.
>
> See here for PV-on-HVM drivers building instructions for SLES11 2.6.27:
> http://wp.colliertech.org/cj/?p=653
>
> If the unmodified_drivers from Xen 4.0 doesn't build for 2.6.27,
> then we should definitely add the (possible) patches from Novell.
Whatever XenLinux tree I tried (xensource 2.6.18, or novell 2.6.32), it
fails to build for 2.6.33. It's probably a trivial error, such as a
missing header file, but I'm really not enough kernel-aware to find
which one:
[guillomovitch@n2 linux-2.6]$ make -C
/lib/modules/2.6.33.1-desktop-2mnb/build M=$PWD modules
make: entrant dans le répertoire « /usr/src/linux-2.6.33.1-desktop-2mnb »
CC [M]
/home/guillomovitch/cooker/xen/BUILD/xen-4.0-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o
In file included from
/home/guillomovitch/cooker/xen/BUILD/xen-4.0-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:52:
include/xen/interface/memory.h:32: error: expected
specifier-qualifier-list before 'GUEST_HANDLE'
include/xen/interface/memory.h:53: warning: data definition has no type
or storage class
include/xen/interface/memory.h:53: warning: type defaults to 'int' in
declaration of 'DEFINE_GUEST_HANDLE_STRUCT'
include/xen/interface/memory.h:53: warning: parameter names (without
types) in function declaration
BTW, the pvops-based 2.6.32.11 kernel isn't a suitable xenlinux tree, it
misses needed files.
--
BOFH excuse #284:
Electrons on a bender
next prev parent reply other threads:[~2010-04-05 16:50 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
2010-03-30 8:17 ` Guillaume Rousse
2010-03-30 10:04 ` Pasi Kärkkäinen
2010-04-05 16:50 ` Guillaume Rousse [this message]
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=4BBA14E6.70208@inria.fr \
--to=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).