From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: why was XENMEM_translate_gpfn_list removed
Date: Thu, 26 Aug 2010 08:28:14 +0100
Message-ID: <C89BD61E.1F321%keir.fraser@eu.citrix.com>
References: <1282780763.26987.3.camel@Workstation>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1282780763.26987.3.camel@Workstation>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "yzhang.unc@gmail.com" <yzhang.unc@gmail.com>, "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 26/08/2010 00:59, "Ian Zhang" <yzhang.unc@gmail.com> wrote:

> Why was XENMEM_translate_gpfn_list removed in Xen 4.0. How to achieve
> similar purpose in HVM?

It's not needed, since all hypercalls on an HVM guest refer to guest
pseudo-physical addresses. Keeping translate_gpfn_list just encouraged lazy
programmers to design bad hypervisor interfaces.

 -- Keir

> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel