public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	geert+renesas@glider.be, Atish Patra <atishp@rivosinc.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	apatel@ventanamicro.com, alexghiti@rivosinc.com,
	Bjorn Topel <bjorn@rivosinc.com>,
	suagrfillet@gmail.com, jeeheng.sia@starfivetech.com,
	petrtesarik@huaweicloud.com, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	prabhakar.mahadev-lad.rj@bp.renesas.com
Subject: Re: [RFT 1/2] RISC-V: handle missing "no-map" properties for OpenSBI's PMP protected regions
Date: Tue, 19 Dec 2023 17:18:19 +0000	[thread overview]
Message-ID: <20231219-fernlike-device-4d7186aa4deb@spud> (raw)
In-Reply-To: <20231207-buffalo-varmint-de843c8a12bb@wendy>


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

Hey,

On Thu, Dec 07, 2023 at 01:11:23PM +0000, Conor Dooley wrote:
> On Thu, Dec 07, 2023 at 01:02:00PM +0000, Lad, Prabhakar wrote:
> > On Wed, Dec 6, 2023 at 2:26 PM Conor Dooley <conor@kernel.org> wrote:
> > > On Wed, Dec 06, 2023 at 04:52:11AM -0800, Palmer Dabbelt wrote:
> > > > On Thu, 10 Aug 2023 02:07:10 PDT (-0700), Conor Dooley wrote:
> 
> > > > > I'm perfectly happy to drop this series though, if people generally are
> > > > > of the opinion that this sort of firmware workaround is ill-advised.
> > > > > We are unaffected by it, so I certainly have no pressure to have
> > > > > something working here. It's my desire not to be user-hostile that
> > > > > motivated this patch.
> > > >
> > > > IIUC you guys and Reneas are the only ones who have hardware that might be
> > > > in a spot where users aren't able to update the firmware (ie, it's out in
> > > > production somewhere).
> > >
> > > I dunno if we can really keep thinking like that though. In terms of
> > > people who have devicetrees in the kernel and stuff available in western
> > > catalog distribution, sure.
> > > I don't think we can assume that that covers all users though, certainly
> > > the syntacore folks pop up every now and then, and I sure hope that
> > > Andes etc have larger customer bases than the in-kernel users would
> > > suggest.
> > >
> > > > So I'm adding Geert, though he probably saw this
> > > > months ago...
> > >
> > > Prabhakar might be a good call on that front. I'm not sure if the
> > > Renesas stuff works on affected versions of OpenSBI though, guess it
> > > depends on the sequencing of the support for the non-coherent stuff and
> > > when this bug was fixed.
> > >
> > ATM, I dont think there are any users who are using the upstream
> > kernel + OpenSBI (apart from me and Geert!). Currently the customers
> > are using the BSP releases.
> 
> That doesn't really answer whether or not you (and your customers) are
> using an affected version of the vendor OpenSBI?
> The affected range for OpenSBI itself is [v0.8 to v1.3).

Did you perhaps miss this mail Prabhakar?

Cheers,
Conor.

[-- 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-12-19 17:18 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 [this message]
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 ` [RFT 2/2] Revert "RISC-V: mark hibernation as nonportable" Conor Dooley
2024-01-23 17:50 ` [RFT 0/2] RISC-V: handle missing "no-map" properties for OpenSBI's PMP protected regions 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=20231219-fernlike-device-4d7186aa4deb@spud \
    --to=conor@kernel.org \
    --cc=alexghiti@rivosinc.com \
    --cc=apatel@ventanamicro.com \
    --cc=atishp@rivosinc.com \
    --cc=bjorn@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=geert+renesas@glider.be \
    --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=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=stable@vger.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