xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Guillaume Rousse <Guillaume.Rousse@inria.fr>,
	xen-devel@lists.xensource.com
Subject: Re: status of PV drivers in Xen 4.0
Date: Tue, 20 Apr 2010 19:16:57 +0300	[thread overview]
Message-ID: <20100420161657.GX1878@reaktio.net> (raw)
In-Reply-To: <s2qf4527be1004120905lc38f7b21o8ca104a01cfd006f@mail.gmail.com>

On Mon, Apr 12, 2010 at 05:05:37PM +0100, Andrew Lyon wrote:
> >>
> >> I'm not sure where to go next with this but I hope this info is useful.
> >>
> >
> > Congratulations!
> >
> > This is valuable information, thanks for going through that.
> >
> > Can you reproduce this with Xen 4.0.0 ? ie. does opensuse xen have
> > some patches related to pv-on-hvm drivers?
> 
> I believe SLES11SP1 will have Xen 4.0 but I have been unable to find
> anywhere to download srpms, apparently they are on dvd2 but as it is
> still in beta there are no iso images either, however opensuse factory
> does have a Xen 4.0 srpm:
> 
> http://download.opensuse.org/factory/repo/src-oss/suse/src/xen-4.0.0_20978_01-1.4.src.rpm
> 
> So the same process could be followed using that, I'm going to give it
> a try tomorrow.
> 

Did you have time to try this yet? 

> >
> > If there are some patches, those should be upstreamed to Xen.
> 
> Hmm, the patches may simply be there to allow building using the
> /usr/src/linux/include/xen headers instead of /usr/src/xen/ , and as
> xensource does not have a newer "classic" kernel than 2.6.18 why would
> they upsteam them.
> 

There has been a lot of demand for PV-on-HVM drivers recently so things
that make them easier to build should be integrated to Xen, imo.

Getting pvops-based pv-on-hvm drivers to upstream Linux is the ultimate goal of course :)

-- Pasi

  parent reply	other threads:[~2010-04-20 16:16 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
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 [this message]
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=20100420161657.GX1878@reaktio.net \
    --to=pasik@iki.fi \
    --cc=Guillaume.Rousse@inria.fr \
    --cc=andrew.lyon@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 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).