All of lore.kernel.org
 help / color / mirror / Atom feed
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, 12 Apr 2010 13:27:24 +0200	[thread overview]
Message-ID: <4BC3039C.8090602@inria.fr> (raw)
In-Reply-To: <20100410125850.GH1878@reaktio.net>


[-- Attachment #1.1: Type: text/plain, Size: 1425 bytes --]

Le 10/04/2010 14:58, Pasi Kärkkäinen a écrit :
>> Have you been successful building the drivers for .31 or .32?
I just tried 2.6.33 so far, without success.

>> I'd like to make a set of patches available to apply to Xen 3.4.2 or
>> 4.0 to enable building the drivers with recent kernels and the forward
>> ported kernels I usually use, but while I've been able to rebuild them
>> on a opensuse 11.2 system running 2.6.31.12 I am finding it hard to
>> work out which patches need to be applied and what else the rpm build
>> process does to enable compilation.
>>
>> Any pointers would be much appreciated.
>>
> 
> Did you take a look at novell's sles11 sp1 kernel? it's 2.6.32 and
> should have pv-on-hvm drivers included?
Yes, that's Jan Beulich said on this list. However, I've buid a
2.6.32.11 kernel, with all xen patches available from SLE11-SP1 (as well
as a few others needed for applying xen patches properly), and used the
corresponding defconfig file. But I can't find any reference to those
drivers, at least with the names given in README file of xen tarball
(xen-platform-pci.ko, xen-vbd.ko, xen-vnif.ko and xen-balloon.ko).
That's probably just because of a name change.

Anyway (unless I'm wrong), the actual usefulness of pv-on-hvm is on
standard linux kernels, not on dom0 itself, and the issue seems to be on
xen Makefile side.
-- 
BOFH excuse #298:

Not enough interrupts


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2010-04-12 11:27 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
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 [this message]
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=4BC3039C.8090602@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 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.