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


[Xen-devel] How Xen handles Dom1 interrupts?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] How Xen handles Dom1 interrupts?
From: "Jun Koi" <junkoi2004@xxxxxxxxx>
Date: Fri, 11 Aug 2006 19:03:57 +0900
Delivery-date: Fri, 11 Aug 2006 03:04:33 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=n2IWSKuH5oX45OHxzOiM0FJjeLuwjdZN/6rRTHfSBK7K+aK75ydx7HRS1LPZxJFOlptySbuPrXaggR2IQEdaaGxXodhJRilFhrJmTF0Eh+RjRnUzsy991P2SUKF4Md6VZx8iA5C6W6EOKmzYM7NNAR3jzZlp+ubxqlt5+yULFPU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Good morning,

I am new to Xen, and trying to understand how Xen works. I have some
questions about virtualization of interrupts on Xen. Thanks in advance
for all helps.

1) From papers about Xen architecture found at Xen homepage, Xen
seemingly intercepts interrupts of Dom1 (paravirtualization). So
interrupts occur in Dom1's context are sent to Xen, and Xen handles
them. Is that correct?

But then how can Dom1 gets the interrupts? For example if int3 occurs
inside Dom1, Xen intercepts int3, but then how debugger (like gdb) can
still work in Dom1? Maybe Xen sends that interrupt back to Dom1 after
processing it in VMM layer?

2) I have read
and looks like Dom1 still handles interrupts itself? Why, because I
suppose that the VMM already intercepts those interrupts?

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.


Xen-devel mailing list