LKML Archive on
help / color / mirror / Atom feed
From: Nick Kossifidis <>
To: Alexandre Ghiti <>
Cc: Nick Kossifidis <>,
	Palmer Dabbelt <>,
	Paul Walmsley <>,
	Albert Ou <>,
	linux-riscv <>,
	" List"
Subject: Re: [PATCH] riscv: Don't use va_pa_offset on kdump
Date: Sat, 09 Oct 2021 16:18:48 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Στις 2021-10-06 14:13, Alexandre Ghiti έγραψε:
>> +
>> +       /* This will trigger a jump to CSR_STVEC anyway */
>>         jalr    zero, a2, 0
> The last jump to a2 can be removed since the fault will be triggered
> before even reaching this instruction.

Just switching SATP to zero doesn't generate a trap unless mstatus.TVM 
is set (for visualization purposes). The hart will try and execute the 
next instruction but it's not clear in the spec what happens in case the 
code is cached, I don't want to rely solely on STVEC. I prefer having 
this instruction there, note that some earlier QEMU versions also had 
this behavior (the original kdump patch didn't set STVEC and it worked 
fine after setting SATP to zero).

> This patch fixes a regression introduced when moving the kernel to the
> end of the address space, so we should add:
> Fixes: 2bfc6cd81bd1 ("riscv: Move kernel mapping outside of linear 
> mapping")
> And it should be backported to 5.13 and 5.14. It seems that the
> following tags should be enough:
> Cc: <> # 5.13
> Cc: <> # 5.14
> And finally, you can add:
> Reviewed-by: Alexandre Ghiti <>

ACK, thanks ! I'll resend the patch with the tags you mentioned.


  reply	other threads:[~2021-10-09 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 12:20 Nick Kossifidis
2021-10-06 11:13 ` Alexandre Ghiti
2021-10-09 13:18   ` Nick Kossifidis [this message]
2021-10-23 20:14     ` Palmer Dabbelt
2021-10-25  1:00       ` Nick Kossifidis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] riscv: Don'\''t use va_pa_offset on kdump' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).