mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] x86: unify some of kernel/irq*.c
Date: Mon, 9 Feb 2009 11:29:51 +0100	[thread overview]
Message-ID: <20090209102951.GK20467@elte.hu> (raw)
In-Reply-To: <498CD661.4070804@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> 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

      reply	other threads:[~2009-02-09 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  0:31 Jeremy Fitzhardinge
2009-02-09 10:29 ` Ingo Molnar [this message]

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=20090209102951.GK20467@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®