From: John Blackwood <john.blackwood@ccur.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Rusty Russell <rusty@rustcorp.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Setting /proc/irq/[n]/smp_affinity failure on 8 cpu systems
Date: Thu, 3 Dec 2009 07:30:21 -0600 [thread overview]
Message-ID: <4B17BD6D.1070000@ccur.com> (raw)
> On Wed, 2009-12-02 at 08:19 -0800, John Blackwood wrote:
> > > I would like to mention an irq set affinity issue occurs on an
> > > older Dell PowerEdge 6650 system:
> > > - 8 cpus (4 are hyper-threaded),
> > > - uses the struct apic 'apic_default' support
> > > - 32 bit (x86) kernel
> > >
> > > This issue is that once you change the irq smp_affinity of an irq
> > > to be less than all cpus in the system, you can never change really
> > > the
> > > irq smp_affinity back to be all cpus in the system (0xff) again,
> > > even though no error status is returned on the "/bin/echo ff >
> > > /proc/irq/[n]/smp_affinity" operation.
> > >
> > > This is due to that fact that BAD_APICID has the same value as
> > > all cpus (0xff) on 32bit kernels, and thus the value returned from
> > > set_desc_affinity() via the cpu_mask_to_apicid_and() function is
> > > treated
> > > as a failure in set_ioapic_affinity_irq_desc(), and no affinity
> > > changes
> > > are made.
> > >
> > > It seems like changing the BAD_APICID value from 0xFF to 0xFFFF for
> > > CONFIG_X86_32 might be one possible solution, and it seems to function
> > > properly for this Dell PowerEdge 6650 system.
>
> John, Thanks for the root cause and analysis. As you noticed, 0xff is a
> valid logical apicid. Similarly 0xffff is a valid logical x2apic cluster
> id. So while your patch fixes your issue, it doesn't completely fix the
> issue. Can you please check if the appended patch works and ack if it
> passes your test?
>
Hi Suresh,
Yes, your patch works on the Dell PowerEdge 6650 system.
Thanks for your help and quick reply.
next reply other threads:[~2009-12-03 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 13:30 John Blackwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-02 16:19 [RFC][PATCH] Setting /proc/irq/[n]/smp_affinity failure on 8 cpu systems John Blackwood
2009-12-03 1:13 ` Suresh Siddha
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=4B17BD6D.1070000@ccur.com \
--to=john.blackwood@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=suresh.b.siddha@intel.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.