From: Tejun Heo <tj@kernel.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
the arch/x86 maintainers <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [RFC PATCH] x86-64: software IRQ masking and handling
Date: Mon, 12 Jul 2010 09:45:42 +0200 [thread overview]
Message-ID: <4C3AC826.4010506@kernel.org> (raw)
In-Reply-To: <201007121149.58129.rusty@rustcorp.com.au>
Hello, Rusty.
On 07/12/2010 04:19 AM, Rusty Russell wrote:
> Also, is it worth trying to implement this soft disable generically?
> I know at least ppc64 does it today...
>
> (Y'know, because your initial patch wasn't ambitious enough...)
We can evolve things such that common parts are factored into generic
code but most of important part being heavily dependent on the
specific architecture, I don't think there will be too much (calling
irqhandler on a separate stack if necessary, generic IRQ masking flag
mgmt maybe merged into preemption flag and so on).
Thanks.
--
tejun
next prev parent reply other threads:[~2010-07-12 7:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 18:01 [RFC PATCH] x86-64: software IRQ masking and handling Tejun Heo
2010-07-11 19:26 ` Ingo Molnar
2010-07-11 20:29 ` Linus Torvalds
2010-07-11 22:03 ` Steven Rostedt
2010-07-12 1:18 ` Linus Torvalds
2010-07-12 5:11 ` Eric Dumazet
2010-07-12 8:02 ` Rusty Russell
2010-07-12 7:41 ` Tejun Heo
2010-07-12 2:19 ` Rusty Russell
2010-07-12 2:49 ` Linus Torvalds
2010-07-12 7:45 ` Tejun Heo [this message]
2010-07-12 7:35 ` Tejun Heo
2010-07-12 13:55 ` Christoph Lameter
2010-08-03 21:37 ` Jeremy Fitzhardinge
2010-08-04 2:09 ` Rusty Russell
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=4C3AC826.4010506@kernel.org \
--to=tj@kernel.org \
--cc=cl@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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