From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: PVHVM drivers in upstream linux kernel Date: Tue, 2 Dec 2014 14:09:14 +0000 Message-ID: <547DC80A.10301@citrix.com> References: <547D88EF.4050206@suse.com> <547D9A4A.6010201@citrix.com> <1417518314.24320.9.camel@citrix.com> <547DA392.90701@suse.com> <547DA99E.5080001@citrix.com> <547DB802.9020900@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <547DB802.9020900@suse.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Juergen Gross , Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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