[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54F72891.5070805@citrix.com>
Date: Wed, 4 Mar 2015 15:45:21 +0000
From: David Vrabel <david.vrabel@...rix.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>,
<paulmck@...ux.vnet.ibm.com>
CC: <linux-kernel@...r.kernel.org>, <mingo@...nel.org>,
<laijs@...fujitsu.com>, <dipankar@...ibm.com>,
<akpm@...ux-foundation.org>, <mathieu.desnoyers@...icios.com>,
<josh@...htriplett.org>, <tglx@...utronix.de>,
<peterz@...radead.org>, <rostedt@...dmis.org>,
<dhowells@...hat.com>, <edumazet@...gle.com>,
<dvhart@...ux.intel.com>, <fweisbec@...il.com>, <oleg@...hat.com>,
<bobby.prani@...il.com>, <x86@...nel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
<xen-devel@...ts.xenproject.org>
Subject: Re: [PATCH tip/core/rcu 02/20] x86: Use common outgoing-CPU-notification
code
On 04/03/15 14:55, Boris Ostrovsky wrote:
>
> In the meantime, it turned out that HVM guests are broken by this patch
> (with our without changes that we've been discussing), because HVM CPUs
> die with
>
> static void xen_hvm_cpu_die(unsigned int cpu)
> {
> xen_cpu_die(cpu);
> native_cpu_die(cpu);
> }
>
> Which means that cpu_wait_death() is called twice, and second call moves
> the CPU to CPU_BROKEN.
>
> The simple solution is to stop calling native_cpu_die() above but I'd
> like to use common code in native_cpu_die(). I'll see if I can carve it
> out without too much damage to x86.
If not really been following this thread but...
Would it be preferable to refactor xen_cpu_die() instead to factor out
its the cpu_wait_death() call?
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