public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman•id.au>
To: Denis Kirjanov <kda@linux-powerpc•org>
Cc: linuxppc-dev@lists•ozlabs.org, ego@linux•vnet.ibm.com
Subject: Re: [PATCH v2] ppc: cpufreq: disable preemption while checking CPU throttling state
Date: Tue, 08 Nov 2016 11:21:23 +1100	[thread overview]
Message-ID: <87k2celt30.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAOJe8K1Cb_UH+yRb8_hYB3T9i8EqteS_nTgWWNcA-EtZvm-wNg@mail.gmail.com>

Denis Kirjanov <kda@linux-powerpc•org> writes:
> On 11/7/16, Michael Ellerman <mpe@ellerman•id.au> wrote:
>> Denis Kirjanov <kda@linux-powerpc•org> writes:
>>>     [   67.700897] BUG: using smp_processor_id() in preemptible [00000000] code: cat/7343
>>>     [   67.700988] caller is .powernv_cpufreq_throttle_check+0x2c/0x710
>>
>> When did this break?
>
> I think that problem exists since commit
> 09a972d1620934142d30cfda455ffe429af751c4 ("cpufreq: powernv: Report
> cpu frequency throttling") but I can be wrong

Yep that looks right to me, thanks.

Gautham, how bad is the bug here, do we want to send this to stable?

cheers

  reply	other threads:[~2016-11-08  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 11:08 [PATCH v2] ppc: cpufreq: disable preemption while checking CPU throttling state Denis Kirjanov
2016-11-07  2:31 ` Gautham R Shenoy
2016-11-07  5:15   ` Denis Kirjanov
2016-11-07  7:36 ` Michael Ellerman
2016-11-07  8:02   ` Denis Kirjanov
2016-11-08  0:21     ` Michael Ellerman [this message]
2016-11-08  3:17       ` Gautham R Shenoy
2016-11-08  8:27         ` Michael Ellerman

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=87k2celt30.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman$(echo .)id.au \
    --cc=ego@linux$(echo .)vnet.ibm.com \
    --cc=kda@linux-powerpc$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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