WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [GIT PULL] x86: unify some of kernel/irq*.c

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: [GIT PULL] x86: unify some of kernel/irq*.c
From: Ingo Molnar <mingo@xxxxxxx>
Date: Mon, 9 Feb 2009 11:29:51 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 Feb 2009 02:30:32 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <498CD661.4070804@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: <498CD661.4070804@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

> These changes factor out the differences between 32 and 64-bit do_IRQ  
> and unify the rest. Unfortunately there are still quite a few other  
> differences (like interrupt stack handling) which preclude further easy  
> unification.
>
> Thanks,
>    J
>
> The following changes since commit f21daa4d04885a34d1972afa9f82a8aebb6152bb:
>  Ingo Molnar (1):
>        Merge branch 'out-of-tree'
>
> are available in the git repository at:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git 
> jsgf/x86/unify-irq
>
> Jeremy Fitzhardinge (2):
>      x86: add handle_irq() to allow interrupt injection

Why doesnt Xen use a special irqchip, instead of this private hook/layer
in the lowlevel x86 arch level?

irqchip is at least well-specified and widely used. do_IRQ() internals
on the other hand will become a Xen special quickly. Also, adding a
needless function call there obviously does not help native performance.

        Ingo

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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