public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Greg KH <greg@kroah.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [PATCH v4 00/10] xen: initial domain support
Date: Tue, 19 Oct 2010 14:54:38 -0700	[thread overview]
Message-ID: <4CBE139E.3060004@goop.org> (raw)
In-Reply-To: <20101019211448.GA10109@kroah.com>

 On 10/19/2010 02:14 PM, Greg KH wrote:
> On Tue, Oct 19, 2010 at 12:16:31PM +0100, Stefano Stabellini wrote:
>> Hi all,
>> this series implements the basic support needed to boot Linux as initial
>> domain on Xen: the target is not to add full featured dom0 support in
>> the kernel but to be able to boot Linux on Xen on native.
> Nice, but what real use is this?
>
> I thought people wanted dom0 support, this doesn't seem to give them
> that.  Is that still the end-goal here, and this is merely a
> stepping-stone to get there?

Yes, it's a significant step there.  Once that's merged the main missing
piece is backend drivers, which we can probably get into a mergable form
for the next window.  And in the meantime, they're a fairly
self-contained thing to maintain out of tree (like other drivers).

Our strategy has been to put together a cluster of patch series which
each have their own intrinsic value, but are also all leading to full
dom0 support.  For example, Stefano's pv-hvm patches are useful for
running Linux as a fully virtualized domain under Xen, but the reworking
of the interrupt infrastructure in a way that dom0 support requires. 
Likewise, Konrad's work on pci-passthrough for domU domains adds all the
machinery required for a Xen domain to have direct access to hardware,
which is also what dom0 requires.

This particular series introduces the pieces needed for the kernel to
actually boot up to usermode as dom0, which has some value even if it
doesn't yet allow you to start new domains (well, you could, but they
wouldn't have any devices).

The net result is that there will be no massive "Xen dom0" patch series,
since that has been pretty clearly rejected in the past.  Instead full
dom0 support is being implemented - at least to some extent - as the
emergent result of a number of Xen-related patches.  These patches also
touch very little code outside of the existing Xen codebase, so there
shouldn't be much scope for controversy.

    J

  reply	other threads:[~2010-10-19 21:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 11:16 [PATCH v4 00/10] xen: initial domain support Stefano Stabellini
2010-10-19 11:17 ` [PATCH v4 01/10] xen: introduce XEN_DOM0 as a silent option stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 02/10] xen: remap GSIs as pirqs when running as initial domain stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 03/10] xen: remap MSIs into " stefano.stabellini
2010-10-19 20:15   ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-10-19 20:24     ` Konrad Rzeszutek Wilk
2010-10-19 11:17 ` [PATCH v4 04/10] xen: map a dummy page for local apic and ioapic in xen_set_fixmap stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 05/10] xen: use vcpu_ops to setup cpu masks stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 06/10] xen: Initialize xenbus for dom0 stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 07/10] xen: add the direct mapping area for ISA bus access stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 08/10] xen: use host E820 map for dom0 stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 09/10] xen: make hvc_xen console work " stefano.stabellini
2010-10-19 11:17 ` [PATCH v4 10/10] xen: mask the MTRR feature from the cpuid stefano.stabellini
2010-10-19 21:14 ` [PATCH v4 00/10] xen: initial domain support Greg KH
2010-10-19 21:54   ` Jeremy Fitzhardinge [this message]
2010-10-19 23:01     ` [Xen-devel] " Greg KH

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=4CBE139E.3060004@goop.org \
    --to=jeremy@goop.org \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --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