From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dave McCracken <dcm@mccr.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: Error building current Linux git tree without configuring Xen
Date: Mon, 3 May 2010 14:27:35 -0400 [thread overview]
Message-ID: <20100503182735.GF24574@phenom.dumpdata.com> (raw)
In-Reply-To: <201004301434.26167.dcm@mccr.org>
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:
http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00785.html
> 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:
http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01133.html
But not sure if it has been completly flushed out.
>
> Dave McCracken
> Oracle Corp.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-03 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 19:34 Error building current Linux git tree without configuring Xen Dave McCracken
2010-05-03 18:27 ` Konrad Rzeszutek Wilk [this message]
2010-05-03 19:58 ` Dave McCracken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100503182735.GF24574@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dcm@mccr.org \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).