[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1403071124140.21846@nuc>
Date: Fri, 7 Mar 2014 11:25:16 -0600 (CST)
From: Christoph Lameter <cl@...ux.com>
To: Fengguang Wu <fengguang.wu@...el.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [percpu] BUG: using __this_cpu_add() in preemptible [00000000]
code: init/1
On Fri, 7 Mar 2014, Fengguang Wu wrote:
> Christoph,
>
> FYI, here is another bisect result and call trace. Interestingly, next-20140307
> no longer triggers this BUG message.
>
> commit a25982c15ae5298520033cd5848a82adf6a97376
> Author: Christoph Lameter <cl@...ux.com>
> AuthorDate: Thu Mar 6 11:05:21 2014 +1100
kvm_clock_read() disables preemption so this should not trigger. And it
seems to work around having to use this cpu ops.
static cycle_t kvm_clock_read(void)
{
struct pvclock_vcpu_time_info *src;
cycle_t ret;
int cpu;
preempt_disable_notrace();
cpu = smp_processor_id();
src = &hv_clock[cpu].pvti;
ret = pvclock_clocksource_read(src);
preempt_enable_notrace();
return ret;
}
Content of type "TEXT/PLAIN" skipped
Content of type "APPLICATION/OCTET-STREAM" skipped
View attachment "config-3.14.0-rc5-next-20140306-07138-g0ffb2fe" of type "TEXT/PLAIN" (108358 bytes)
_______________________________________________
LKP mailing list
LKP@...ux.intel.com
Powered by blists - more mailing lists