mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: <palmer@dabbelt.com>
Cc: conor@kernel.org, conor.dooley@microchip.com,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Atish Patra" <atishp@rivosinc.com>,
	"Anup Patel" <apatel@ventanamicro.com>,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Song Shuai" <suagrfillet@gmail.com>,
	"JeeHeng Sia" <jeeheng.sia@starfivetech.com>,
	"Petr Tesarik" <petrtesarik@huaweicloud.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [RFT 2/2] Revert "RISC-V: mark hibernation as nonportable"
Date: Wed, 2 Aug 2023 12:12:53 +0100	[thread overview]
Message-ID: <20230802-chef-throng-d9de8b672a49@wendy> (raw)
In-Reply-To: <20230802-purse-hydrant-6f44f77364b0@wendy>

Revert commit ed309ce52218 ("RISC-V: mark hibernation as nonportable")
as the kernel now has a way to handle the "no-map"-less, PMP protected,
reserved memory nodes for the affected versions of OpenSBI.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
 arch/riscv/Kconfig | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 4c07b9189c86..47aef21073f9 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -866,11 +866,8 @@ menu "Power management options"
 
 source "kernel/power/Kconfig"
 
-# Hibernation is only possible on systems where the SBI implementation has
-# marked its reserved memory as not accessible from, or does not run
-# from the same memory as, Linux
 config ARCH_HIBERNATION_POSSIBLE
-	def_bool NONPORTABLE
+	def_bool y
 
 config ARCH_HIBERNATION_HEADER
 	def_bool HIBERNATION
-- 
2.40.1


  parent reply	other threads:[~2023-08-02 11:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 11:12 [RFT 0/2] RISC-V: handle missing "no-map" properties for OpenSBI's PMP protected regions Conor Dooley
2023-08-02 11:12 ` [RFT 1/2] " Conor Dooley
2023-08-06  9:03   ` Alexandre Ghiti
2023-08-07  0:44   ` JeeHeng Sia
2023-08-08 13:13     ` Conor Dooley
2023-08-09 10:24       ` JeeHeng Sia
2023-08-09 11:04         ` Conor Dooley
2023-08-08  7:54   ` Atish Kumar Patra
2023-08-08 13:39     ` Conor Dooley
2023-08-09  9:01       ` Atish Kumar Patra
2023-08-10  9:07         ` Conor Dooley
2023-12-06 12:52           ` Palmer Dabbelt
2023-12-06 14:23             ` Conor Dooley
2023-12-07 13:02               ` Lad, Prabhakar
2023-12-07 13:11                 ` Conor Dooley
2023-12-19 17:18                   ` Conor Dooley
2023-12-19 17:27                     ` Prabhakar Mahadev Lad
2023-12-19 18:06                       ` Palmer Dabbelt
2023-12-19 18:38                         ` Prabhakar Mahadev Lad
2023-12-19 18:57                           ` Conor Dooley
2023-12-19 19:46                             ` Prabhakar Mahadev Lad
2023-08-02 11:12 ` Conor Dooley [this message]
2024-01-23 17:50 ` [RFT 0/2] " 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=20230802-chef-throng-d9de8b672a49@wendy \
    --to=conor.dooley@microchip.com \
    --cc=alexghiti@rivosinc.com \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@rivosinc.com \
    --cc=bjorn@rivosinc.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=petrtesarik@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®