All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	David Vrabel <david.vrabel@citrix.com>
Subject: Re: PVHVM drivers in upstream linux kernel
Date: Tue, 2 Dec 2014 10:11:01 -0500	[thread overview]
Message-ID: <20141202151101.GG27869@laptop.dumpdata.com> (raw)
In-Reply-To: <1417518314.24320.9.camel@citrix.com>

On Tue, Dec 02, 2014 at 11:05:14AM +0000, Ian Campbell wrote:
> On Tue, 2014-12-02 at 10:54 +0000, David Vrabel wrote:
> > On 02/12/14 09:39, Juergen Gross wrote:
> > > Hi,
> > > 
> > > looking into the upstream linux sources I realized that the PVHVM
> > > drivers of XEN are only available with the pvops kernel. Is this on
> > > purpose? Shouldn't the frontend drivers, xen/platform-pci.c etc. be
> > > configurable without having to enable CONFIG_PARAVIRT?
> > 
> > I suppose that would be possible but I don't think it's a useful
> > configuration because you would lose PV spinlocks for example.
> 
> IIRC the reason this hasn't been implemented until now is that
> refactoring would be required to the various bits of driver code which
> assumes PAE + PARAVIRT when they aren't strictly needed, e.g. grant
> table code. Whether its worth the churn at this stage is debatable, but
> I think the (in)ability to use PV spinlocks is a red-herring.
> 
> Adding PV drivers to an HVM guest is a useful thing to do, even without
> PV spinlocks. PV IO gets you far more incremental benefit than the locks
> do, adding PV IO paths is the number 1 thing which should be done to any
> guest.
> 
> One actual usecase is installing from a distro installer which isn't
> PAE, let alone PARAVIRT enabled[0], to get far enough that you can
> install a more capable PVHVM kernel with more bells and whistles.
> 
> If there were distros around who refused wholesale to enable PARAVIRT
> even in a non-default kernel then it would be more likely that they
> could be convinced to enable a set of PV IO drivers, since they have 0
> impact on a non-PARAVIRT system, and still give significant benefit to
> Xen users. I don't know of any of the major distros are refusing
> PARAVIRT in this way though.
> 
> Ian.
> 
> [0] The default i386 Debian installer falls into this camp, but you can
> use the special PV Xen variant to install as PVHVM too so it's not so
> critical.

And the Fedora 21 LiveISO (32-bit) does too.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2014-12-02 15:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02  9:39 PVHVM drivers in upstream linux kernel Juergen Gross
2014-12-02 10:54 ` David Vrabel
2014-12-02 11:02   ` Juergen Gross
2014-12-02 11:05   ` Ian Campbell
2014-12-02 11:33     ` Juergen Gross
2014-12-02 11:36       ` Ian Campbell
2014-12-02 11:39         ` Juergen Gross
2014-12-02 11:59       ` David Vrabel
2014-12-02 13:00         ` Juergen Gross
2014-12-02 14:09           ` David Vrabel
2014-12-02 14:35             ` Juergen Gross
2014-12-02 15:11     ` Konrad Rzeszutek Wilk [this message]
2014-12-02 15:13       ` Ian Campbell
2014-12-02 17:04         ` Konrad Rzeszutek Wilk
2014-12-02 15:10 ` Konrad Rzeszutek Wilk

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=20141202151101.GG27869@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.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 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.