From: Thomas Gleixner <tglx@linutronix.de>
To: Yi Sun <yi.y.sun@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
chao.p.peng@intel.com, chao.gao@intel.com,
isaku.yamahata@intel.com, michael.h.kelly@microsoft.com,
tianyu.lan@microsoft.com, "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH v1 2/3] locking/pvqspinlock, hv: Enable PV qspinlock for Hyper-V
Date: Thu, 13 Sep 2018 13:06:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1809131304560.1473@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1536830005-37260-3-git-send-email-yi.y.sun@linux.intel.com>
On Thu, 13 Sep 2018, Yi Sun wrote:
> +#include <asm/mshyperv.h>
>
> /* representing HT siblings of each logical CPU */
> DEFINE_PER_CPU_READ_MOSTLY(cpumask_var_t, cpu_sibling_map);
> @@ -1335,6 +1336,7 @@ void __init native_smp_prepare_boot_cpu(void)
> /* already set me in cpu_online_mask in boot_cpu_init() */
> cpumask_set_cpu(me, cpu_callout_mask);
> cpu_set_state_online(me);
> + hv_init_spinlocks();
No. We have smp_ops.smp_prepare_boot_cpu for that.
Thanks,
tglx
next prev parent reply other threads:[~2018-09-13 11:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 9:13 [PATCH v1 0/3] Enable PV qspinlock for Hyper-V Yi Sun
2018-09-13 9:13 ` [PATCH v1 1/3] X86/Hyper-V: Add Guest IDLE MSR support Yi Sun
2018-09-13 9:13 ` [PATCH v1 2/3] locking/pvqspinlock, hv: Enable PV qspinlock for Hyper-V Yi Sun
2018-09-13 11:06 ` Thomas Gleixner [this message]
2018-09-14 8:53 ` Yi Sun
2018-09-13 11:24 ` Thomas Gleixner
2018-09-14 9:04 ` Yi Sun
2018-09-14 10:42 ` Thomas Gleixner
2018-09-17 12:54 ` Yi Sun
2018-09-20 1:56 ` Yi Sun
2018-09-13 16:16 ` kbuild test robot
2018-09-13 16:42 ` kbuild test robot
2018-09-13 9:13 ` [PATCH v1 3/3] hv: add description for hv_nopvspin Yi Sun
2018-09-15 23:43 ` [PATCH v1 0/3] Enable PV qspinlock for Hyper-V Michael Kelley (EOSG)
2018-09-17 14:37 ` Yi Sun
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.21.1809131304560.1473@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@intel.com \
--cc=haiyangz@microsoft.com \
--cc=isaku.yamahata@intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.h.kelly@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=tianyu.lan@microsoft.com \
--cc=x86@kernel.org \
--cc=yi.y.sun@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).