From: "Jan Beulich" <JBeulich@novell.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH v2 1/2] x86: skip migrating IRQF_PER_CPU irq in fixup_irqs
Date: Mon, 09 May 2011 15:28:37 +0100 [thread overview]
Message-ID: <4DC81635020000780004072A@vpn.id2.novell.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1105091437500.2843@ionos>
>>> On 09.05.11 at 14:39, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Fri, 6 May 2011, Konrad Rzeszutek Wilk wrote:
>> On Fri, May 06, 2011 at 02:43:36PM +0800, Tian, Kevin wrote:
>> > because Xen event chip silently fails the set_affinity ops, and
>> > logically IRQF_PER_CPU should be recognized here.
>>
>> OK, so what if the set_affinity ops was implemented?
>
> An interrupt chip which has a set_affinity op should not mark
> something per cpu, which implies that the irq CANNOT be moved.
Why shouldn't it be possible o use the same "chip" for both per-CPU
and "normal" IRQs?
Jan
next prev parent reply other threads:[~2011-05-09 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 6:43 [PATCH v2 1/2] x86: skip migrating IRQF_PER_CPU irq in fixup_irqs Tian, Kevin
2011-05-06 13:58 ` Konrad Rzeszutek Wilk
2011-05-06 21:41 ` Tian, Kevin
2011-05-09 12:39 ` Thomas Gleixner
2011-05-09 14:28 ` Jan Beulich [this message]
2011-05-10 3:26 ` Tian, Kevin
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=4DC81635020000780004072A@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=hpa@zytor.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).