From: Thomas Gleixner <tglx@linutronix.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-4.8] irq/affinity: use get/put_online_cpus
Date: Mon, 22 Aug 2016 11:01:05 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1608221059220.5608@nanos> (raw)
In-Reply-To: <20160814160032.GA4601@infradead.org>
On Sun, 14 Aug 2016, Christoph Hellwig wrote:
> Any chance to get a quick review for this and get it off to Linus?
> Without this fix the function is unusable in 4.8+ on my test systems
> because we seem to always get a inconsistent view of the cpu online
> bitmap - something that didn't happen before this merge window oddly
> enough.
That only happens if you have concurrent cpu hotplug operations, but yes this
needs to be fixed anyway.
Thanks,
tglx
next prev parent reply other threads:[~2016-08-22 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:06 Christoph Hellwig
2016-08-14 16:00 ` Christoph Hellwig
2016-08-22 9:01 ` Thomas Gleixner [this message]
2016-08-22 9:28 ` [tip:irq/urgent] genirq/affinity: Use get/put_online_cpus around cpumask operations tip-bot for Christoph Hellwig
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=alpine.DEB.2.20.1608221059220.5608@nanos \
--to=tglx@linutronix.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.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®