mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] genirq: Add chip hooks for taking CPUs on/off line.
Date: Wed, 23 Mar 2011 23:09:32 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1103232304240.31464@localhost6.localdomain6> (raw)
In-Reply-To: <4D8A6E38.7020203@gmail.com>

On Wed, 23 Mar 2011, David Daney wrote:
> On 03/21/2011 02:13 PM, Thomas Gleixner wrote:
> > I can't imagine any other purpose for that.
> 
> Modifying the affinity of non-per-cpu IRQs to use the new CPU?

Hmm. Good point. Ok, go ahead with that name.

> > Hmm. The offline fixup_irq() code is arch specific and usually calls
> > desc->irq_data.chip->irq_set_affinity under desc->lock. I have not yet
> > found an arch independent way to do that. Any ideas welcome.
> > 
> 
> There are all the new affinity callbacks, and the things shown in procfs?  Are
> those handled properly if I call chip->irq_set_affinity?  I think not.

If the arch code updates irq_data.affinity then yes. I still need to
go through all that maze and figure out what all the archs really want
to do in that case.

Thanks,

	tglx

  reply	other threads:[~2011-03-23 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 21:48 [RFC PATCH 0/2] Add IRQ " David Daney
2011-03-18 21:48 ` [RFC PATCH 1/2] genirq: Add " David Daney
2011-03-19 20:51   ` Thomas Gleixner
2011-03-21 18:26     ` David Daney
2011-03-21 21:13       ` Thomas Gleixner
2011-03-23 22:03         ` David Daney
2011-03-23 22:09           ` Thomas Gleixner [this message]
2011-03-18 21:48 ` [RFC PATCH 2/2] MIPS: Octeon: Rewrite interrupt handling code David Daney

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=alpine.LFD.2.00.1103232304240.31464@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=ddaney.cavm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.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
all inboxes | Powered by JetHome®