From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: [PATCH v3] docs: add PVH specification
Date: Thu, 25 Sep 2014 17:00:50 -0700
Message-ID: <20140925170050.0a8c9c66@mantra.us.oracle.com>
References: <1411060764-4016-1-git-send-email-roger.pau@citrix.com>
	<20140922173837.1e069d63@mantra.us.oracle.com>
	<54218EDE0200007800037B2A@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <mukesh.rathor@oracle.com>) id 1XXIy4-00020Y-6y
	for xen-devel@lists.xenproject.org; Fri, 26 Sep 2014 00:01:00 +0000
In-Reply-To: <54218EDE0200007800037B2A@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, David Vrabel <david.vrabel@citrix.com>, Roger Pau Monne <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, 23 Sep 2014 14:16:46 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 23.09.14 at 02:38, <mukesh.rathor@oracle.com> wrote:
> > On Thu, 18 Sep 2014 19:19:24 +0200
> > Roger Pau Monne <roger.pau@citrix.com> wrote:
> > 
> >> Introduce a document that describes the interfaces used on PVH.
> >> This document has been designed from a guest OS point of view
> >> (i.e.: what a guest needs to do in order to support PVH).
> > ..... 
> >> +
> >> +*TODO*: we need to figure out what to do with MMIO regions, right
> >> now Xen +sets all the holes in the native e820 to MMIO regions for
> >> Dom0 up to 4GB. We +need to decide what to do with MMIO regions
> >> above 4GB on Dom0, and what to do +for PVH DomUs with
> >> pci-passthrough.
> > 
> > My previous comment in earlier version on this:
> > 
> > "We map all non-ram regions for dom0 1:1 till the highest non-ram
> > e820 entry. If there is anything that is beyond the last e820 entry,
> > it will remain unmapped."
> 
> But that's something that needs fixing rather than spelling out in
> the documentation. I.e. Roger having this as a TODO seems quite
> right to me.

Yes, but what Roger is saying implies we don't map above 4GB which
is incorrect. Perhaps:

We map all non-ram regions for dom0 1:1 till the last e820 entry. If the 
last entry ends below 4GB, then the remaining space is mapped 1:1 upto 4GB.
This implies that if there is any region beyond the last e820 entry above
4GB, it is not mapped.  
TODO: Map region beyond last e820 if it's above 4GB. Add support for domUs
with pci passthru.


-Mukesh