mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: limit irq affinity
Date: Sun, 27 Sep 2009 18:19:09 -0700	[thread overview]
Message-ID: <86802c440909271819i303df4ccw9c5df1f4d4455e36@mail.gmail.com> (raw)
In-Reply-To: <20090928010217.GA16863@sgi.com>

On Sun, Sep 27, 2009 at 6:02 PM, Dimitri Sivanich <sivanich@sgi.com> wrote:
> This patch allows for restrictions to irq affinity via a new cpumask and
> device node value in the irq_cfg structure.  The node value can then be
> used by specific x86 architectures to determine the cpumask for the
> desired cpu irq affinity domain.
>
> The mask forces IRQ affinity to remain within the specified cpu domain.
> On some UV systems, this domain will be limited to the nodes accessible
> to the given node.  Currently other X86 systems will have all bits in
> the cpumask set, so non-UV systems will remain unaffected at this time.
>
> Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>
>
> ---
>
>  arch/x86/Kconfig                   |    1
>  arch/x86/include/asm/uv/uv_irq.h   |    2
>  arch/x86/include/asm/uv/uv_mmrs.h  |   25 ++++
>  arch/x86/kernel/apic/io_apic.c     |  166 +++++++++++++++++++++++++++------
>  arch/x86/kernel/apic/x2apic_uv_x.c |    2
>  arch/x86/kernel/uv_irq.c           |   68 +++++++++++++
>  6 files changed, 235 insertions(+), 29 deletions(-)
>
> Index: linux/arch/x86/kernel/apic/io_apic.c
> ===================================================================
> --- linux.orig/arch/x86/kernel/apic/io_apic.c   2009-09-26 15:28:04.000000000 -0500
> +++ linux/arch/x86/kernel/apic/io_apic.c        2009-09-26 16:20:04.000000000 -0500
> @@ -62,6 +62,7 @@
>  #include <asm/hw_irq.h>
>  #include <asm/uv/uv_hub.h>
>  #include <asm/uv/uv_irq.h>
> +#include <asm/uv/uv.h>
>
>  #include <asm/apic.h>
>
> @@ -149,6 +150,8 @@ struct irq_cfg {
>        struct irq_pin_list *irq_2_pin;
>        cpumask_var_t domain;
>        cpumask_var_t old_domain;
> +       cpumask_var_t allowed;
> +       int node;
>        unsigned move_cleanup_count;
>        u8 vector;
>        u8 move_in_progress : 1;
> @@ -184,6 +187,18 @@ void __init io_apic_disable_legacy(void)
>        nr_irqs_gsi = 0;
>  }
>

original irq affinity in irq_desc does not work?

YH

  reply	other threads:[~2009-09-28  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  1:02 Dimitri Sivanich
2009-09-28  1:19 ` Yinghai Lu [this message]
2009-09-28  1:54   ` Dimitri Sivanich
2009-10-01  9:07 ` Ingo Molnar
2009-10-01 17:55   ` Dimitri Sivanich

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=86802c440909271819i303df4ccw9c5df1f4d4455e36@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sivanich@sgi.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®