All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Schuster <ml@markus.schuster.name>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [XCP] new version available
Date: Tue, 19 Jan 2010 20:39:21 +0100	[thread overview]
Message-ID: <201001192039.21424.ml@markus.schuster.name> (raw)
In-Reply-To: <20100119193606.GF2861@reaktio.net>

On Tuesday 19 January 2010 20:36:06 Pasi Kärkkäinen wrote:
> On Tue, Jan 19, 2010 at 08:30:40PM +0100, Markus Schuster wrote:
> > On Tuesday 19 January 2010 18:57:11 Pasi Kärkkäinen wrote:
> > > On Tue, Jan 19, 2010 at 07:54:08PM +0200, Pasi Kärkkäinen wrote:
> > > > On Tue, Jan 19, 2010 at 03:36:16PM +0100, Markus Schuster wrote:
> > > > > Dave Scott wrote:
> > > > > > * PV drivers check for magic strings in xenstore removed
> > > > >
> > > > > Scott, one question: Can the Windows PV drivers be used with
> > > > > "normal" XEN or is some additional infrastructure from XCP
> > > > > necessary?
> > > >
> > > > Yes they can, with some patches to Xen:
> > > > http://lists.xensource.com/archives/html/xen-devel/2009-11/msg00932.h
> > > >tml
> > > > http://lists.xensource.com/archives/html/xen-devel/2009-12/msg00593.h
> > > >tml
> > >
> > > These patches are already in xen-3.4-testing.hg and in xen-unstable.hg,
> > > so they'll be in Xen 3.4.3 and 4.0.0 releases.
> >
> > That's cool! Is there some comparison with GPLPV drivers in case of
> > stability, speed, features and so on?
> > It looks a bit like future competition between the two driver packs?
> 
> Well the major difference is that GPLPV drivers are opensource,
> and the Citrix Windows PV drivers provided in XCP are not.

Ah, I see - too bad Citrix couldn't open source them :)

Regards,
Markus

  reply	other threads:[~2010-01-19 19:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 18:13 [XCP] new version available Dave Scott
2010-01-18 18:19 ` Dave Scott
2010-01-18 18:24   ` Thiago Camargo Martins Cordeiro
     [not found] ` <81A73678E76EA642801C8F2E4823AD2143B8C194C1-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-01-18 20:03   ` [Xen-devel] " Pasi Kärkkäinen
2010-01-19 13:43     ` [Xen-API] " Marco Sinhoreli
2010-01-19 13:53       ` Ian Campbell
2010-01-19 14:06         ` Rob Hoes
2010-01-19 14:36 ` Markus Schuster
2010-01-19 17:54   ` Pasi Kärkkäinen
2010-01-19 17:57     ` Pasi Kärkkäinen
2010-01-19 19:30       ` Markus Schuster
2010-01-19 19:36         ` Pasi Kärkkäinen
2010-01-19 19:39           ` Markus Schuster [this message]
2010-01-21 17:48             ` Ian Pratt
2010-01-21 17:51               ` Konrad Rzeszutek Wilk
2010-01-21 18:03                 ` Keir Fraser
2010-01-21 20:07                   ` Keith Coleman
2010-01-21 21:06                 ` Pasi Kärkkäinen
2010-01-21 21:52                   ` Keith Coleman
2010-01-21 19:57               ` Tom Rotenberg
2010-01-25 23:29 ` Rose, Gregory V
     [not found]   ` <43F901BD926A4E43B106BF17856F07559CEF9E56-osO9UTpF0UQ8Ug9VwtkbtrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-01-26 10:56     ` Dave Scott
     [not found]       ` <81A73678E76EA642801C8F2E4823AD2143E92238F7-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-01-26 17:26         ` Rose, Gregory V

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=201001192039.21424.ml@markus.schuster.name \
    --to=ml@markus.schuster.name \
    --cc=pasik@iki.fi \
    --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.