From: Andrew Morton <akpm@linux-foundation.org>
To: John Keller <jpk@sgi.com>
Cc: linux-ia64@vger.kernel.org, steiner@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - SN: validate smp_affinity mask on intr redirect
Date: Thu, 03 May 2007 20:42:48 +0000 [thread overview]
Message-ID: <20070503134248.e9b58a32.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070503125602.12552.4152.sendpatchset@attica.americas.sgi.com>
On Thu, 03 May 2007 07:56:02 -0500
John Keller <jpk@sgi.com> wrote:
> On SN, only allow one bit to be set in the smp_affinty mask
> when redirecting an interrupt. Currently setting multiple
> bits is allowed, but only the first bit is used in
> determining the CPU to redirect to. This has caused confusion
> among some customers.
>
> ...
>
> +
> +int is_affinity_mask_valid(cpumask_t cpumask)
> +{
> + if (ia64_platform_is("sn2")) {
> + /* Only allow one CPU to be specified in the smp_affinity mask */
> + if (cpus_weight(cpumask) != 1)
> + return 0;
> + }
> + return 1;
> +}
A bool returning true or false would be appropriate, given this function's
clearly-boolean name.
> +#ifndef ARCH_HAS_IRQ_AFFINITY_VALIDATION
> +#define is_irq_affinity_mask_valid(cpumask) 1
> +#endif
The ARCH_HAS_FOO things have never been popular. There are a couple of
alternatives going around:
a) use __attribute__((weak)) and provide a one-line default
implementation in kernel/irq/proc.c. This has a small runtime cost.
b) In include/asm-ia64/irq.h, do
#define is_affinity_mask_valid is_affinity_mask_valid
and in kernel/irq/proc.c do
#ifndef is_affinity_mask_valid
#define is_affinity_mask_valid() 1
#endif
This has minimal runtime cost, but is a bit tricksy.
It has the advantage that it doesn't introduce some new identifier
which needs to be maintained.
> extern int irq_set_affinity(unsigned int irq, cpumask_t cpumask);
> extern int irq_can_set_affinity(unsigned int irq);
>
> Index: linux-2.6/include/asm-ia64/irq.h
> =================================> --- linux-2.6.orig/include/asm-ia64/irq.h 2007-05-01 15:47:01.660643076 -0500
> +++ linux-2.6/include/asm-ia64/irq.h 2007-05-01 15:48:42.729254805 -0500
> @@ -11,6 +11,8 @@
> * 02/29/00 D.Mosberger moved most things into hw_irq.h
> */
>
> +#include <linux/cpumask.h>
> +
This is the sort of inclusion which tends to make things blow up. I trust
this was carefully compile-tested.
With a) above, the is_affinity_mask_valid() declaration would be in a
different header. With b), no additional include will be needed.
> #define NR_IRQS 256
> #define NR_IRQ_VECTORS NR_IRQS
>
> @@ -30,4 +32,7 @@ extern void disable_irq_nosync (unsigned
> extern void enable_irq (unsigned int);
> extern void set_irq_affinity_info (unsigned int irq, int dest, int redir);
>
> +#define ARCH_HAS_IRQ_AFFINITY_VALIDATION
> +extern int is_affinity_mask_valid(cpumask_t cpumask);
> +
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: John Keller <jpk@sgi.com>
Cc: linux-ia64@vger.kernel.org, steiner@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - SN: validate smp_affinity mask on intr redirect
Date: Thu, 3 May 2007 13:42:48 -0700 [thread overview]
Message-ID: <20070503134248.e9b58a32.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070503125602.12552.4152.sendpatchset@attica.americas.sgi.com>
On Thu, 03 May 2007 07:56:02 -0500
John Keller <jpk@sgi.com> wrote:
> On SN, only allow one bit to be set in the smp_affinty mask
> when redirecting an interrupt. Currently setting multiple
> bits is allowed, but only the first bit is used in
> determining the CPU to redirect to. This has caused confusion
> among some customers.
>
> ...
>
> +
> +int is_affinity_mask_valid(cpumask_t cpumask)
> +{
> + if (ia64_platform_is("sn2")) {
> + /* Only allow one CPU to be specified in the smp_affinity mask */
> + if (cpus_weight(cpumask) != 1)
> + return 0;
> + }
> + return 1;
> +}
A bool returning true or false would be appropriate, given this function's
clearly-boolean name.
> +#ifndef ARCH_HAS_IRQ_AFFINITY_VALIDATION
> +#define is_irq_affinity_mask_valid(cpumask) 1
> +#endif
The ARCH_HAS_FOO things have never been popular. There are a couple of
alternatives going around:
a) use __attribute__((weak)) and provide a one-line default
implementation in kernel/irq/proc.c. This has a small runtime cost.
b) In include/asm-ia64/irq.h, do
#define is_affinity_mask_valid is_affinity_mask_valid
and in kernel/irq/proc.c do
#ifndef is_affinity_mask_valid
#define is_affinity_mask_valid() 1
#endif
This has minimal runtime cost, but is a bit tricksy.
It has the advantage that it doesn't introduce some new identifier
which needs to be maintained.
> extern int irq_set_affinity(unsigned int irq, cpumask_t cpumask);
> extern int irq_can_set_affinity(unsigned int irq);
>
> Index: linux-2.6/include/asm-ia64/irq.h
> ===================================================================
> --- linux-2.6.orig/include/asm-ia64/irq.h 2007-05-01 15:47:01.660643076 -0500
> +++ linux-2.6/include/asm-ia64/irq.h 2007-05-01 15:48:42.729254805 -0500
> @@ -11,6 +11,8 @@
> * 02/29/00 D.Mosberger moved most things into hw_irq.h
> */
>
> +#include <linux/cpumask.h>
> +
This is the sort of inclusion which tends to make things blow up. I trust
this was carefully compile-tested.
With a) above, the is_affinity_mask_valid() declaration would be in a
different header. With b), no additional include will be needed.
> #define NR_IRQS 256
> #define NR_IRQ_VECTORS NR_IRQS
>
> @@ -30,4 +32,7 @@ extern void disable_irq_nosync (unsigned
> extern void enable_irq (unsigned int);
> extern void set_irq_affinity_info (unsigned int irq, int dest, int redir);
>
> +#define ARCH_HAS_IRQ_AFFINITY_VALIDATION
> +extern int is_affinity_mask_valid(cpumask_t cpumask);
> +
next prev parent reply other threads:[~2007-05-03 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 12:56 [PATCH] - SN: validate smp_affinity mask on intr redirect John Keller
2007-05-03 12:56 ` John Keller
2007-05-03 20:42 ` Andrew Morton [this message]
2007-05-03 20:42 ` Andrew Morton
2007-05-03 21:19 ` John Keller
2007-05-03 21:19 ` 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=20070503134248.e9b58a32.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jpk@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.