All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>, Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: PVHVM drivers in upstream linux kernel
Date: Tue, 2 Dec 2014 14:09:14 +0000	[thread overview]
Message-ID: <547DC80A.10301@citrix.com> (raw)
In-Reply-To: <547DB802.9020900@suse.com>

On 02/12/14 13:00, Juergen Gross wrote:
> 
> I'd see:
> - XEN_PV (selects PARAVIRT, XEN_FRONTEND): be able to run as pv-domain
>   (x86 only)

Depends on PARAVIRT perhaps?

> - XEN_PVHVM (selects XEN_FRONTEND): be able to run as hvm-domain with
>   pv-drivers
> - XEN_BACKEND (selects PARAVIRT if x86): be able to run as driver domain
>   (dom0 or other)

Does not need to select PARAVIRT -- HVM domains can run backends.

> - XEN_DOM0 (selects PARAVIRT if x86, XEN_BACKEND): be able to run as
>   dom0

XEN_DOM0 depends on XEN_PV or XEN_PVH (if x86) and whatever ARM needs.

> - XEN_FRONTEND: be able to run as domU with pv-drivers

It may also be interesting to consider splitting the PV MMU stuff under
a PARAVIRT_MMU option.  This might address a reason why people want to
disable PARAVIRT completely.

David

  reply	other threads:[~2014-12-02 14:09 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 [this message]
2014-12-02 14:35             ` Juergen Gross
2014-12-02 15:11     ` Konrad Rzeszutek Wilk
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=547DC80A.10301@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Campbell@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.