From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: [RFC PATCH 3/16]: PVH xen: Add PHYSDEVOP_map_iomem
Date: Tue, 15 Jan 2013 15:35:38 -0800
Message-ID: <20130115153538.7b82b284@mantra.us.oracle.com>
References: <20130111173243.2438c22a@mantra.us.oracle.com>
	<50F3F8CE02000078000B53E6@nat28.tlf.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>
In-Reply-To: <50F3F8CE02000078000B53E6@nat28.tlf.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 <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Mon, 14 Jan 2013 11:23:42 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 12.01.13 at 02:32, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > In this patch, we define PHYSDEVOP_map_iomem and add support for
> > it. Also, XEN_DOMCTL_memory_mapping code is put into a function so
> > it can be shared later for PVH. No change in
> > XEN_DOMCTL_memory_mapping functionality. 
> 
> Is that to say that a PVH guest will need to issue this for each and
> every MMIO range? Irrespective of being DomU or Dom0? I would
> have expected that this could be transparent...
> 

Hmm.. we discussed this at xen hackathon last year.  The 
guest maps the entire range in one shot. Doing it this way keeps
things flexible for future if EPT size gets to be a problem.

Mukesh