mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Borislav Petkov <bp@suse.de>, Len Brown <len.brown@intel.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] x86: Fix the irq affinity in fixup_cpus
Date: Wed, 5 Jul 2017 22:10:18 +0800	[thread overview]
Message-ID: <20170705141018.GB17143@yu-desktop-1.sh.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1707050843380.2019@nanos>

On Wed, Jul 05, 2017 at 08:46:08AM +0200, Thomas Gleixner wrote:
> On Wed, 5 Jul 2017, Chen Yu wrote:
> > On Tue, Jul 04, 2017 at 10:50:33AM +0200, Thomas Gleixner wrote:
> > Here's the test result for affinity:
> > # uname -r
> > 4.12.0+
> > # cat /proc/irq/32/smp_affinity
> > 00000000,80000000
> > # echo 0 > /sys/devices/system/cpu/cpu31/online 
> > # cat /proc/irq/32/smp_affinity
> > 00000000,ffffffff
> > Looks like cpu31 is till included in the irq mask.
> 
> Yes, because the offline broke affinity and now it's reset to the default
> affinity mask. /proc/irq/*/affinity is the affinity which is allowed by the
> admin, not the one which is effective.
> 
> Look at /proc/irq/32/effective_affinity to see where it's really routed to.
>
ok, got it, this is normal now.
cat /proc/irq/32/effective_affinity
00000000,00000001

Thanks,
	Yu

      reply	other threads:[~2017-07-05 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  7:46 Chen Yu
2017-06-04 20:04 ` Thomas Gleixner
2017-07-03 13:51   ` Chen Yu
2017-07-04  8:50     ` Thomas Gleixner
2017-07-05  3:20       ` Chen Yu
2017-07-05  6:46         ` Thomas Gleixner
2017-07-05 14:10           ` Chen Yu [this message]

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=20170705141018.GB17143@yu-desktop-1.sh.intel.com \
    --to=yu.c.chen@intel.com \
    --cc=bp@suse.de \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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®