From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Tony <tony.luck@intel.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH 0/5] Message signaled irq handling cleanups
Date: Wed, 27 Sep 2006 22:02:23 -0600 [thread overview]
Message-ID: <m18xk4lju8.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200609280057.03372.ak@suse.de> (Andi Kleen's message of "Thu, 28 Sep 2006 00:57:03 +0200")
Andi Kleen <ak@suse.de> writes:
> On Wednesday 27 September 2006 21:54, Eric W. Biederman wrote:
>>
>> The following patch set should be enough to clear up the
>> outstanding issues with genirq on i386 and x86_64. This actually
>> takes things a step farther and moves all of architecture
>> dependencies I could find into the appropriate architecture.
>>
>> So hopefully we are finally close enough that other architectures
>> will be able implement msi support, without too much trouble.
>>
>> msi: Simplify msi sanity checks by adding with generic irq code.
>> msi: Only use a single irq_chip for msi interrupts
>> msi: Refactor and move the msi irq_chip into the arch code.
>> msi: Move the ia64 code into arch/ia64
>> htirq: Tidy up the htirq code
>
>
> The (small) x86-64 parts are fine by me. Thanks.
Note this should allow the hack in -mm that disables stack switch
with 4K stacks on i386 to be dropped.
Eric
next prev parent reply other threads:[~2006-09-28 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 19:54 Eric W. Biederman
2006-09-27 22:57 ` Andi Kleen
2006-09-28 4:02 ` Eric W. Biederman [this message]
2006-09-27 19:54 Eric W. Biederman
2006-09-27 19:55 Eric W. Biederman
2006-09-27 20:29 ` Eric W. Biederman
2006-09-27 22:36 ` Benjamin Herrenschmidt
2006-09-27 22:51 ` Benjamin Herrenschmidt
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=m18xk4lju8.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.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®