From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] fix ia64 breakage with PHYSDEVOP_pirq_eoi_mfn (was Re:
	[PATCH 2/2] linux/x86: use shared page indicating the need
	for an EOI notification)
Date: Wed, 03 Dec 2008 10:15:33 +0000
Message-ID: <C55C0CC5.1FCBF%keir.fraser@eu.citrix.com>
References: <20081203101353.GJ15798%yamahata@valinux.co.jp>
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: <20081203101353.GJ15798%yamahata@valinux.co.jp>
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: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 03/12/2008 10:13, "Isaku Yamahata" <yamahata@valinux.co.jp> wrote:

>> If you are fully virtualised then gmfn should mean gpfn, and
>> arbitrary_virt_to_machine() is correct, isn't it? I can't see a situation
>> where arbitrary_virt_to_machine() wouldn't correctly give you a gmfn (after
>> all, it gets you a machine address in guest context, as its name describes
>> :-). 
> 
> Oh, you are quite right.
> Do you agree to rename PHYSDEVOP_pirq_eoi_mfn to PHYSDEVOP_pirq_eoi_gmfn?

Yes, and I'll fix up your patches myself to use a_v_t_m() always.

 -- Keir