From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Daniel J Blueman <daniel@numascale.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Steffen Persvold <sp@numascale.com>
Subject: Re: [PATCH v3] x86: Fix sibling map with NumaChip
Date: Wed, 4 Mar 2015 10:22:21 +0100 [thread overview]
Message-ID: <20150304092221.GG3233@pd.tnic> (raw)
In-Reply-To: <20150304045204.GA5158@gmail.com>
On Wed, Mar 04, 2015 at 05:52:04AM +0100, Ingo Molnar wrote:
> Hm, so why doesn't this_cpu_has() work? Supposedly such flags ought to
> be symmetric on all CPUs in the system?
Actually, static_cpu_has_safe() should be the fastest and the safest to
use in all cases.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-03-04 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 4:48 [PATCH v3] x86: Fix sibling map with NumaChip Daniel J Blueman
2015-03-04 4:52 ` Ingo Molnar
2015-03-04 9:22 ` Borislav Petkov [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=20150304092221.GG3233@pd.tnic \
--to=bp@alien8.de \
--cc=daniel@numascale.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sp@numascale.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