From: Peter Zijlstra <peterz@infradead.org>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Radim Krcmar <rkrcmar@redhat.com>,
Pankaj Gupta <pagupta@redhat.com>,
Eduardo Valentin <eduval@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>, Matt Wilson <msw@amazon.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
Waiman Long <longman@redhat.com>, kvm <kvm@vger.kernel.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Jan H . Schoenherr" <jschoenh@amazon.de>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [PATCHv3 1/1] locking/qspinlock/x86: Avoid test-and-set when PV_DEDICATED is set
Date: Fri, 10 Nov 2017 08:59:14 +0100 [thread overview]
Message-ID: <20171110075914.mcjp2niadqszo3yb@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CANRm+CxDmu=anHQ+CZJenAywiMVSZ-eOv7n3tiCYALL4tiqSqA@mail.gmail.com>
On Fri, Nov 10, 2017 at 10:07:56AM +0800, Wanpeng Li wrote:
> >> Also, you should not put cpumask_t on stack, that's 'broken'.
>
> Thanks pointing out this. I found a useful comments in arch/x86/kernel/irq.c:
>
> /* These two declarations are only used in check_irq_vectors_for_cpu_disable()
> * below, which is protected by stop_machine(). Putting them on the stack
> * results in a stack frame overflow. Dynamically allocating could result in a
> * failure so declare these two cpumasks as global.
> */
> static struct cpumask affinity_new, online_new;
That code no longer exists.. Also not entirely sure how it would be
helpful.
What you probably want to do is have a per-cpu cpumask, since
flush_tlb_others() is called with preemption disabled. But you probably
don't want an unconditionally allocated one, since most kernels will not
in fact be PV.
So you'll want something like:
static DEFINE_PER_CPU(cpumask_var_t, __pv_tlb_mask);
And then you need something like:
for_each_possible_cpu(cpu) {
zalloc_cpumask_var_node(per_cpu_ptr(&__pb_tlb_mask, cpu),
GFP_KERNEL, cpu_to_node(cpu));
}
before you set the pv-op or so.
next prev parent reply other threads:[~2017-11-10 7:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 20:26 Eduardo Valentin
2017-11-07 12:23 ` Paolo Bonzini
2017-11-07 12:39 ` Eduardo Valentin
2017-11-07 12:43 ` Paolo Bonzini
2017-11-08 8:45 ` Eduardo Valentin
2017-11-08 17:36 ` Radim Krčmář
2017-11-09 8:55 ` Eduardo Valentin
2017-11-09 14:17 ` Radim Krčmář
2017-11-16 4:54 ` Eduardo Valentin
2017-11-27 0:43 ` Wanpeng Li
2017-11-09 12:43 ` Wanpeng Li
2017-11-09 15:53 ` Pankaj Gupta
2017-11-09 16:05 ` Radim Krcmar
2017-11-09 16:17 ` Peter Zijlstra
2017-11-09 16:37 ` Pankaj Gupta
2017-11-09 16:45 ` Radim Krcmar
2017-11-09 17:12 ` Peter Zijlstra
2017-11-09 17:15 ` Peter Zijlstra
2017-11-09 17:28 ` Peter Zijlstra
2017-11-09 17:35 ` Radim Krcmar
2017-11-10 2:07 ` Wanpeng Li
2017-11-10 7:59 ` Peter Zijlstra [this message]
2017-11-10 8:04 ` Wanpeng Li
2017-11-09 17:31 ` Radim Krcmar
2017-11-09 16:00 ` Radim Krcmar
2017-11-10 6:07 ` Wanpeng Li
2017-11-10 8:19 ` Paolo Bonzini
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=20171110075914.mcjp2niadqszo3yb@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aliguori@amazon.com \
--cc=corbet@lwn.net \
--cc=eduval@amazon.com \
--cc=hpa@zytor.com \
--cc=jschoenh@amazon.de \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=msw@amazon.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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®