linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] powernv: Avoid calling trace tlbie in kexec path.
Date: Thu, 23 Nov 2017 00:37:01 +0530	[thread overview]
Message-ID: <1511377449.2a15exj7wg.naveen@linux.ibm.com> (raw)
In-Reply-To: <151137178794.14123.18003389448303728066.stgit@jupiter.in.ibm.com>

Mahesh J Salgaonkar wrote:
> From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
>=20
> Rebooting into a new kernel with kexec fails in trace_tlbie() which is
> called from native_hpte_clear(). This happens if the running kernel has
> CONFIG_LOCKDEP enabled. With lockdep enabled, the tracepoints always
> execute few RCU checks regardless of whether tracing is on or off.
> We are already in the last phase of kexec sequence in real mode with
> HILE_BE set. At this point the RCU check ends up in RCU_LOCKDEP_WARN and
> causes kexec to fail.
>=20
> Fix this by not calling trace_tlbie() from native_hpte_clear().
>=20
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
> Reported-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
> ---
>  arch/powerpc/mm/hash_native_64.c |   15 ++++++++++++---
>  1 file changed, 12 insertions(+), 3 deletions(-)
>=20
> diff --git a/arch/powerpc/mm/hash_native_64.c b/arch/powerpc/mm/hash_nati=
ve_64.c
> index 3848af1..640cf56 100644
> --- a/arch/powerpc/mm/hash_native_64.c
> +++ b/arch/powerpc/mm/hash_native_64.c
> @@ -47,7 +47,8 @@
>=20
>  DEFINE_RAW_SPINLOCK(native_tlbie_lock);
>=20
> -static inline void __tlbie(unsigned long vpn, int psize, int apsize, int=
 ssize)
> +static inline unsigned long  ___tlbie(unsigned long vpn, int psize,
> +						int apsize, int ssize)
>  {
>  	unsigned long va;
>  	unsigned int penc;
> @@ -100,7 +101,15 @@ static inline void __tlbie(unsigned long vpn, int ps=
ize, int apsize, int ssize)
>  			     : "memory");
>  		break;
>  	}
> -	trace_tlbie(0, 0, va, 0, 0, 0, 0);

Does it help if you use the _rcuidle variant instead, to turn off all=20
rcu checks for tracing __tlbie()?
	trace_tlbie_rcuidle(0, 0, va, 0, 0, 0, 0);


- Naveen

=

  reply	other threads:[~2017-11-22 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 17:32 [PATCH] powernv: Avoid calling trace tlbie in kexec path Mahesh J Salgaonkar
2017-11-22 19:07 ` Naveen N. Rao [this message]
2017-11-23  9:38   ` Mahesh Jagannath Salgaonkar
2017-11-23 10:02     ` Naveen N. Rao
2017-11-22 22:56 ` Balbir Singh
2017-11-23 11:18   ` Mahesh Jagannath Salgaonkar
2017-11-23 12:15   ` Michael Ellerman
2017-11-23 13:11     ` Naveen N. Rao
2017-11-24  4:13       ` Balbir Singh
2017-11-24  6:10         ` Michael Ellerman
2017-11-24  6:10       ` Michael Ellerman
2017-11-24  9:46 ` 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=1511377449.2a15exj7wg.naveen@linux.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mahesh@linux.vnet.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).