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] How Xen handles Dom1 interrupts?

To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] How Xen handles Dom1 interrupts?
From: "Jun Koi" <junkoi2004@xxxxxxxxx>
Date: Fri, 11 Aug 2006 23:14:23 +0900
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, Daniel Stodden <stodden@xxxxxxxxxx>
Delivery-date: Fri, 11 Aug 2006 07:15:21 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DvfC6Ci3ZRAhHAEe7qLkJJqP0ntOAn6u8i5b6WJ7TrvuhtT5Kz9AcAVn0lDWFNotAWAgBGCzh2xvmNkIIiJ07uy3KercwkfnrvujgB112Mh7vzkwt7vgyD7VDk+QglOvBlUdYsflf3123tkvTYziJj2vSekMwO8cb+dVytcrK7A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1155293037.4347.25.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <fdaac4d50608110303g1ac77269u8501af326dce7e75@xxxxxxxxxxxxxx> <1155292762.18655.27.camel@xxxxxxxxxxxxxxxxxxxxxxx> <1155293037.4347.25.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 8/11/06, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> wrote:
On Fri, 2006-08-11 at 12:39 +0200, Daniel Stodden wrote:
> > 3) How is linux-xen-sparse/arch/i386/kernel/traps-xen.c compiled,
> > while it is not refereed to in
> > linux-xen-sparse/arch/i386/kernel/Makefile? I see traps.c is
> refereed
> > instead of traps-xen.c, but I still saw traps-xen.o there after
> > compiling? What traps.c does, and what traps-xen.c does, since both
> > are very similar to me.
> uhhm. now you got me. i noticed the file names changed at some point,
> i didn't bother why yet, or how the makefiles changed. maybe someone
> from xensource can tell.

        obj-y := $(call cherrypickxen, $(obj-y))

at the end of the Makefile will rewrite foo.o as foo-xen.o if there is a
foo-xen.c or foo-xen.S available. The function is defined in

Interesting! Would you tell me why we need that trick?

In that case, we can empty file traps-xen.c, no? Because according to
your mention, only the filename (and its existence) matters, but not
its content.


Xen-devel mailing list