From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: xen_hvm_callback_vector
Date: Mon, 30 Aug 2010 09:25:45 -0700
Message-ID: <4C7BDB89.90805@goop.org>
References: <4C7842C3.2000300@goop.org>
	<1283019557.3469.47.camel@localhost.localdomain>
	<4C798243.7000301@goop.org>
	<alpine.DEB.2.00.1008301030570.2545@kaball-desktop>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <alpine.DEB.2.00.1008301030570.2545@kaball-desktop>
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: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>, "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

 On 08/30/2010 02:37 AM, Stefano Stabellini wrote:
>> smp_xen_hvm_callback_vector is just missing, so I think it should be
>> using BUILD_INTERRUPT3 with the third arg being xen_evtchn_do_upcall.
> BUILD_INTERRUPT3 is an x86_32 only MACRO, that's why I am using
> apicinterrupt instead.

My original problem was that my 32-bit builds were failing because
smp_xen_hvm_callback_vector was missing.  I wonder if its the collision
of two sets of patches.

    J