mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
	<x86@kernel.org>
Cc: <hpa@zytor.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
	<arnd@arndb.de>, <peterz@infradead.org>
Subject: Re: [PATCH] paravirt/locks: avoid modifying static key before jump_label_init()
Date: Wed, 25 Oct 2017 15:35:21 +0800	[thread overview]
Message-ID: <1c852010-e9df-fac8-8970-6c60f769f40e@cn.fujitsu.com> (raw)
In-Reply-To: <7223e00c-0fe6-8844-d0f2-a7cabfba9c03@suse.com>

Hi Juergen,

[...]
>> I like your original method.
>> So, I try to fix it by moving the native_pv_lock_init() from
>>  native_smp_prepare_boot_cpu() to native_smp_prepare_cpus().
>
> Hmm, this might work, but the Xen case has to be modified (same for
> my more general solution), as xen_init_spinlocks() is still modifying
> the static key too early. And we can't move xen_init_spinlocks() to
> smp_prepare_cpus() as this would be too late for the alternatives
> patching.
>

Yes, Right.

> So let me extend your patch a little bit to cover Xen, too.
>

Yes!

How about moving the check of xen_pvspin into native_pv_lock_init()
like below?

Thanks,
	dou.

------------------------->8
diff --git a/arch/x86/kernel/paravirt.c b/arch/x86/kernel/paravirt.c
index 041096b..b5f3ecb 100644
--- a/arch/x86/kernel/paravirt.c
+++ b/arch/x86/kernel/paravirt.c
@@ -119,7 +119,7 @@ DEFINE_STATIC_KEY_TRUE(virt_spin_lock_key);

  void __init native_pv_lock_init(void)
  {
-       if (!static_cpu_has(X86_FEATURE_HYPERVISOR))
+       if (!static_cpu_has(X86_FEATURE_HYPERVISOR) || !xen_pvspin)
                 static_branch_disable(&virt_spin_lock_key);
  }

diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index aed1460..6b1335a 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1323,6 +1323,8 @@ void __init native_smp_prepare_cpus(unsigned int 
max_cpus)
         pr_info("CPU0: ");
         print_cpu_info(&cpu_data(0));

+       native_pv_lock_init();
+
         uv_system_init();

         set_mtrr_aps_delayed_init();
@@ -1350,7 +1352,6 @@ 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);
-       native_pv_lock_init();
  }

  void __init native_smp_cpus_done(unsigned int max_cpus)
diff --git a/arch/x86/xen/smp_pv.c b/arch/x86/xen/smp_pv.c
index 5147140..570b2bc 100644
--- a/arch/x86/xen/smp_pv.c
+++ b/arch/x86/xen/smp_pv.c
@@ -236,6 +236,8 @@ static void __init xen_pv_smp_prepare_cpus(unsigned 
int max_cpus)
                 xen_raw_printk(m);
                 panic(m);
         }
+       native_pv_lock_init();
+
         xen_init_lock_cpu(0);

         smp_store_boot_cpu_info();
diff --git a/arch/x86/xen/spinlock.c b/arch/x86/xen/spinlock.c
index e8ab80a..8e0ec79 100644
--- a/arch/x86/xen/spinlock.c
+++ b/arch/x86/xen/spinlock.c
@@ -130,7 +130,6 @@ void __init xen_init_spinlocks(void)

         if (!xen_pvspin) {
                 printk(KERN_DEBUG "xen: PV spinlocks disabled\n");
-               static_branch_disable(&virt_spin_lock_key);
                 return;
         }
         printk(KERN_DEBUG "xen: PV spinlocks enabled\n");


>> I hope it's useful to you.
>
> It really is, thanks.
>
>
> Juergen
>
>
>

  reply	other threads:[~2017-10-25  7:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 13:49 Juergen Gross
2017-10-25  4:26 ` Dou Liyang
2017-10-25  6:58   ` Juergen Gross
2017-10-25  7:35     ` Dou Liyang [this message]
2017-10-25  7:51       ` Juergen Gross
2017-10-25  8:06         ` Dou Liyang
2017-10-27  8:43 ` Ingo Molnar
2017-10-27  9:21   ` Juergen Gross
2017-10-27  9:38     ` Dou Liyang

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=1c852010-e9df-fac8-8970-6c60f769f40e@cn.fujitsu.com \
    --to=douly.fnst@cn.fujitsu.com \
    --cc=arnd@arndb.de \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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®