Linux IA64 platform development
 help / color / mirror / Atom feed
From: John Keller <jpk@sgi.com>
To: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Cc: akpm@linux-foundation.org, tglx@linutronix.de
Subject: genirq regression - CONFIG_AUTO_IRQ_AFFINITY
Date: Fri, 05 Dec 2008 16:40:01 +0000	[thread overview]
Message-ID: <200812051640.mB5Ge2U1122172@fcbayern.americas.sgi.com> (raw)

The addition of the generic affinity autoselector has introduced
a regression in SN2 Altix.

In the past, request_irq()'s call to select_smp_affinity() was
essentially a noop. 

#ifdef CONFIG_AUTO_IRQ_AFFINITY
extern int select_smp_affinity(unsigned int irq);
#else
static inline int select_smp_affinity(unsigned int irq)
{
        return 1;
}


Now changes have created do_irq_select_affinity(), which is
executed by a call to request_irq().

  request_irq()
   __setup_irq()
    do_irq_select_affinity()

do_irq_select_affinity() will call the set_affinity() routine,
with a default mask. On SN2 (and possibly all ia64 platforms),
this will retarget all device interrupts to the same CPU, most
likely CPU0.


#ifndef CONFIG_AUTO_IRQ_AFFINITY
/*
 * Generic version of the affinity autoselector.
 */
int do_irq_select_affinity(unsigned int irq, struct irq_desc *desc)
{
        cpumask_t mask;

        if (!irq_can_set_affinity(irq))
                return 0;

        cpus_and(mask, cpu_online_map, irq_default_affinity);

        /*
         * Preserve an userspace affinity setup, but make sure that
         * one of the targets is online.
         */
        if (desc->status & (IRQ_AFFINITY_SET | IRQ_NO_BALANCING)) {
                if (cpus_intersects(desc->affinity, cpu_online_map))
                        mask = desc->affinity;
                else
                        desc->status &= ~IRQ_AFFINITY_SET;
        }

        desc->affinity = mask;
        desc->chip->set_affinity(irq, mask);

        return 0;
}

This set_affinity call undoes all the performance related interrupt
targetting that the SN2 PROM did at boot.

I'm looking at a patch that makes use of the new IRQ_AFFINITY_SET
flag in the irq_desc to get around this.

Is this an issue for all ia64 platforms? Or does irq balancing
factor in here? IRQ balancing is disabled on SN2.

John Keller


             reply	other threads:[~2008-12-05 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 16:40 John Keller [this message]
2008-12-06  4:56 ` genirq regression - CONFIG_AUTO_IRQ_AFFINITY Yinghai Lu
2008-12-08 14:29 ` John Keller

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=200812051640.mB5Ge2U1122172@fcbayern.americas.sgi.com \
    --to=jpk@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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