public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Alexandre Ghiti <alexghiti@rivosinc.com>
Cc: "Björn Töpel" <bjorn@rivosinc.com>,
	"Atish Patra" <atishp@atishpatra.org>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Anup Patel" <apatel@ventanamicro.com>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	robh@kernel.org, jeeheng.sia@starfivetech.com,
	linux-kernel@vger.kernel.org, palmer@rivosinc.com,
	leyfoon.tan@starfivetech.com, mason.huo@starfivetech.com,
	"Guo Ren" <guoren@kernel.org>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Song Shuai" <suagrfillet@gmail.com>,
	linux-riscv@lists.infradead.org,
	"Andrew Jones" <ajones@ventanamicro.com>
Subject: Re: Bug report: kernel paniced when system hibernates
Date: Fri, 26 May 2023 15:59:07 +0100	[thread overview]
Message-ID: <20230526-steep-omen-a5a46a1086bf@spud> (raw)
In-Reply-To: <CAHVXubiDezbwZO6X2btvgpq-XqHnxZjXzaMnSK2YrHc_ioLx8Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1754 bytes --]

On Fri, May 26, 2023 at 03:14:33PM +0200, Alexandre Ghiti wrote:
> Hi everyone,
> 
> On Thu, May 25, 2023 at 11:24 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Thu, May 25, 2023 at 01:06:04PM -0700, Atish Patra wrote:
> > > On Thu, May 25, 2023 at 11:39 AM Conor Dooley <conor@kernel.org> wrote:
> > > >
> > > > On Thu, May 25, 2023 at 11:37:40AM -0700, Atish Patra wrote:
> > > >
> > > > > Any testing of hibernation still needs to revert the patch until we
> > > > > have the proper fix.
> > > >
> > > > "the patch" is what exactly? I assume you don't mean depending on
> > > > NONPORTABLE, since that is a Kconfig option.
> > >
> > > Nope. Sorry I meant the commit
> > >
> > > 3335068 ("riscv: Use PUD/P4D/PGD pages for the linear mapping")
> >
> > Ah, if your SBI implementation is one of the affected ones, yeah.
> > If not, you can just set NONPORTABLE :)
> 
> @Björn Töpel emitted the idea of excluding from the hibernation all
> the memory nodes in the "/reserved-memory" node
> (https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/devicetree/bindings/reserved-memory/reserved-memory.yaml):
> I have to admit that I don't see why it is not done by default by the
> kernel.

My understanding was that it was perfectly fine to use reserved memory
nodes to fence off some memory to use in device drivers etc, which then
may need to be saved/restored.

> Unless there is stuff in this node that needs to be "hibernated", I
> think that would be a very good solution since we would not rely on
> the name of the "internal" nodes of "/reserved-memory" (i.e.
> "mmode_resv").
> 
> I'm digging into why it is not done by default, just wanted to have
> your feedback before the week-end :)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-05-26 14:59 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  9:24 Bug report: kernel paniced when system hibernates Song Shuai
2023-05-16  9:55 ` JeeHeng Sia
2023-05-16 11:14   ` Alexandre Ghiti
2023-05-16 11:27     ` JeeHeng Sia
2023-05-17  8:33       ` Alexandre Ghiti
2023-05-18  4:06         ` JeeHeng Sia
2023-05-16 11:12 ` Alexandre Ghiti
2023-05-17  8:58   ` Alexandre Ghiti
2023-05-17 11:05     ` Song Shuai
     [not found]       ` <CAHVXubgjgMvFV0MOABbtKr+2TH85+0kow7wOrjxFCP5iXt1saQ@mail.gmail.com>
2023-05-17 14:42         ` Fwd: " Alexandre Ghiti
2023-05-18  1:29           ` JeeHeng Sia
2023-05-18  9:13             ` Alexandre Ghiti
2023-05-18  3:29           ` Song Shuai
2023-05-18 11:54             ` Alexandre Ghiti
2023-05-17 11:27     ` Conor Dooley
2023-05-17 14:55       ` Alexandre Ghiti
2023-05-18  6:53         ` Anup Patel
2023-05-18  7:59           ` Conor Dooley
2023-05-18  8:41             ` Alexandre Ghiti
2023-05-18 10:35               ` Conor Dooley
2023-05-18 11:58                 ` Alexandre Ghiti
2023-05-24 23:53                   ` Atish Patra
2023-05-25 12:55                     ` Conor Dooley
2023-05-18 12:21                 ` JeeHeng Sia
2023-05-18 12:09           ` Alexandre Ghiti
2023-05-18 14:04             ` Anup Patel
2023-05-24 13:49               ` Conor Dooley
2023-05-24 13:57                 ` Alexandre Ghiti
2023-05-24 15:59                   ` Conor Dooley
2023-05-24 23:45               ` Atish Patra
2023-05-25 13:08                 ` Conor Dooley
2023-05-25 13:21                   ` Anup Patel
2023-05-25 13:37                     ` Conor Dooley
2023-05-25 13:43                       ` Anup Patel
2023-05-25 13:55                         ` Conor Dooley
2023-05-25 13:59                           ` Anup Patel
2023-05-25 14:20                             ` Conor Dooley
2023-05-25 17:39                               ` Atish Patra
2023-05-25 18:22                                 ` Conor Dooley
2023-05-25 18:37                                   ` Atish Patra
2023-05-25 18:39                                     ` Conor Dooley
2023-05-25 20:06                                       ` Atish Patra
2023-05-25 21:24                                         ` Conor Dooley
2023-05-26 13:14                                           ` Alexandre Ghiti
2023-05-26 14:59                                             ` Conor Dooley [this message]
2023-05-26 15:12                                               ` Alexandre Ghiti
2023-05-26 15:17                                                 ` Anup Patel
2023-05-26 15:22                                                   ` Alexandre Ghiti
2023-05-26 18:48                                                     ` Atish Patra
2023-05-16 11:35 ` Conor Dooley

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=20230526-steep-omen-a5a46a1086bf@spud \
    --to=conor@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=anup@brainfault.org \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@atishpatra.org \
    --cc=bjorn@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=guoren@kernel.org \
    --cc=jeeheng.sia@starfivetech.com \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mason.huo@starfivetech.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@kernel.org \
    --cc=suagrfillet@gmail.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