[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5342DCF3.7080408@citrix.com>
Date: Mon, 7 Apr 2014 18:14:27 +0100
From: David Vrabel <david.vrabel@...rix.com>
To: <konrad@...nel.org>
CC: <xen-devel@...ts.xenproject.org>, <linux-kernel@...r.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Steven Rostedt <rostedt@...dmis.org>, <stable@...r.kernel.org>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>
Subject: Re: [PATCH] xen/spinlock: Don't enable them unconditionally.
On 04/04/14 19:48, konrad@...nel.org wrote:
> From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
>
> The git commit a945928ea2709bc0e8e8165d33aed855a0110279
> ('xen: Do not enable spinlocks before jump_label_init() has executed')
> was added to deal with the jump machinery. Earlier the code
> that turned on the jump label was only called by Xen specific
> functions. But now that it had been moved to the initcall machinery
> it gets called on Xen, KVM, and baremetal - ouch!. And the detection
> machinery to only call it on Xen wasn't remembered in the heat
> of merge window excitement.
>
> This means that the slowpath is enabled on baremetal while it should
> not be.
Applied to devel/for-linus-3.15.
Thanks.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists