All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	conor@kernel.org, atishp@atishpatra.org, anup@brainfault.org,
	alex@ghiti.fr, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, suagrfillet@gmail.com,
	jeeheng.sia@starfivetech.com
Subject: Re: [PATCH v1] RISC-V: mark hibernation as nonportable
Date: Wed, 31 May 2023 15:10:21 +0000	[thread overview]
Message-ID: <168554582182.8247.5723560098196678790.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230526-astride-detonator-9ae120051159@wendy>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 26 May 2023 11:59:08 +0100 you wrote:
> Hibernation support depends on firmware marking its reserved/PMP
> protected regions as not accessible from Linux.
> The latest versions of the de-facto SBI implementation (OpenSBI) do
> not do this, having dropped the no-map property to enable 1 GiB huge
> page mappings by the kernel.
> This was exposed by commit 3335068f8721 ("riscv: Use PUD/P4D/PGD pages
> for the linear mapping"), which made the first 2 MiB of DRAM (where SBI
> typically resides) accessible by the kernel.
> Attempting to hibernate with either OpenSBI, or other implementations
> following its lead, will lead to a kernel panic ([1], [2]) as the
> hibernation process will attempt to save/restore any mapped regions,
> including the PMP protected regions in use by the SBI implementation.
> 
> [...]

Here is the summary with links:
  - [v1] RISC-V: mark hibernation as nonportable
    https://git.kernel.org/riscv/c/ed309ce52218

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor.dooley@microchip.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	conor@kernel.org, atishp@atishpatra.org, anup@brainfault.org,
	alex@ghiti.fr, linux-kernel@vger.kernel.org,
	paul.walmsley@sifive.com, suagrfillet@gmail.com,
	jeeheng.sia@starfivetech.com
Subject: Re: [PATCH v1] RISC-V: mark hibernation as nonportable
Date: Wed, 31 May 2023 15:10:21 +0000	[thread overview]
Message-ID: <168554582182.8247.5723560098196678790.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230526-astride-detonator-9ae120051159@wendy>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Fri, 26 May 2023 11:59:08 +0100 you wrote:
> Hibernation support depends on firmware marking its reserved/PMP
> protected regions as not accessible from Linux.
> The latest versions of the de-facto SBI implementation (OpenSBI) do
> not do this, having dropped the no-map property to enable 1 GiB huge
> page mappings by the kernel.
> This was exposed by commit 3335068f8721 ("riscv: Use PUD/P4D/PGD pages
> for the linear mapping"), which made the first 2 MiB of DRAM (where SBI
> typically resides) accessible by the kernel.
> Attempting to hibernate with either OpenSBI, or other implementations
> following its lead, will lead to a kernel panic ([1], [2]) as the
> hibernation process will attempt to save/restore any mapped regions,
> including the PMP protected regions in use by the SBI implementation.
> 
> [...]

Here is the summary with links:
  - [v1] RISC-V: mark hibernation as nonportable
    https://git.kernel.org/riscv/c/ed309ce52218

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-05-31 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 10:59 [PATCH v1] RISC-V: mark hibernation as nonportable Conor Dooley
2023-05-26 10:59 ` Conor Dooley
2023-05-31 15:03 ` Palmer Dabbelt
2023-05-31 15:03   ` Palmer Dabbelt
2023-05-31 15:10 ` patchwork-bot+linux-riscv [this message]
2023-05-31 15:10   ` patchwork-bot+linux-riscv

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=168554582182.8247.5723560098196678790.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=jeeheng.sia@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --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 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.