From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: ruscur@russell.cc
Subject: Re: (subset) [PATCH v2 4/4] powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT
Date: Thu, 31 Aug 2023 14:02:30 +1000 [thread overview]
Message-ID: <169345455029.11824.10985056549717167842.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20230823055317.751786-4-mpe@ellerman.id.au>
On Wed, 23 Aug 2023 15:53:17 +1000, Michael Ellerman wrote:
> lppaca_shared_proc() takes a pointer to the lppaca which is typically
> accessed through get_lppaca(). With DEBUG_PREEMPT enabled, this leads
> to checking if preemption is enabled, for example:
>
> BUG: using smp_processor_id() in preemptible [00000000] code: grep/10693
> caller is lparcfg_data+0x408/0x19a0
> CPU: 4 PID: 10693 Comm: grep Not tainted 6.5.0-rc3 #2
> Call Trace:
> dump_stack_lvl+0x154/0x200 (unreliable)
> check_preemption_disabled+0x214/0x220
> lparcfg_data+0x408/0x19a0
> ...
>
> [...]
Applied to powerpc/next.
[4/4] powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT
https://git.kernel.org/powerpc/c/eac030b22ea12cdfcbb2e941c21c03964403c63f
cheers
next prev parent reply other threads:[~2023-08-31 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 5:53 [PATCH 1/4] powerpc/pseries: Move VPHN constants into vphn.h Michael Ellerman
2023-08-23 5:53 ` [PATCH 2/4] powerpc/pseries: Move hcall_vphn() prototype " Michael Ellerman
2023-08-23 5:53 ` [PATCH 3/4] powerpc: Don't include lppaca.h in paca.h Michael Ellerman
2023-08-23 5:53 ` [PATCH v2 4/4] powerpc/pseries: Rework lppaca_shared_proc() to avoid DEBUG_PREEMPT Michael Ellerman
2023-08-31 4:02 ` Michael Ellerman [this message]
2023-08-31 4:02 ` [PATCH 1/4] powerpc/pseries: Move VPHN constants into vphn.h 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=169345455029.11824.10985056549717167842.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=ruscur@russell.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.