This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Error building current Linux git tree without configurin

To: Dave McCracken <dcm@xxxxxxxx>
Subject: Re: [Xen-devel] Error building current Linux git tree without configuring Xen
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 3 May 2010 14:27:35 -0400
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen Developers List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 03 May 2010 11:29:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201004301434.26167.dcm@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201004301434.26167.dcm@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Fri, Apr 30, 2010 at 02:34:26PM -0500, Dave McCracken wrote:
> I tried to build a Linux kernel from current git sources without specifying 

Which branch is that? Can you do 'git log' and tell me what is the
latest you see?

> any form of Xen.  I got these three undefined symbols:
> xen_register_gsi
> xen_teardown_msi_dev
> xen_setup_msi_irqs
> I defined them as dummy functions in arch/x86/include/asm/xen/pci.h for the 
> case where CONFIG_XEN is not set, and got a working kernel.  They're also 

There was a patch that fixed this floating around. Don't think Jeremy
had a chance to check in it..

Here is the thread:

> defined as dummy functions higher in the file under #else clauses for other 
> config variables.  I assume we don't want the dummy functions defined 
> multiple 
> times, but I'm not sure the cleanest solution.

Something along these lines:


But not sure if it has been completly flushed out.
> Dave McCracken
> Oracle Corp.
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>