From: Anup Patel <anup@brainfault.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: apatel@ventanamicro.com, Emil Renner Berthing <kernel@esmil.dk>,
Greg KH <gregkh@linuxfoundation.org>,
Atish Patra <atishp@rivosinc.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org,
jirislaby@kernel.org, ajones@ventanamicro.com
Subject: Re: [PATCH] tty: hvc: Don't enable the RISC-V SBI console by default
Date: Wed, 14 Feb 2024 21:20:13 +0530 [thread overview]
Message-ID: <CAAhSdy3Tf=9jD1Cd11RjwKyDFPA_gHTqxMXSJ3HwANFFnR-8dA@mail.gmail.com> (raw)
In-Reply-To: <20240214153429.16484-2-palmer@rivosinc.com>
On Wed, Feb 14, 2024 at 9:06 PM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> From: Palmer Dabbelt <palmer@rivosinc.com>
>
> The new SBI console has the same problem as the old one: there's only
> one shared backing hardware and no synchronization, so the two drivers
> end up stepping on each other. This was the same issue the old SBI-0.1
> console drivers had, but that was disabled by default when SBI-0.1 was.
>
> So just mark the new driver as nonportable.
>
> Reported-by: Emil Renner Berthing <kernel@esmil.dk>
> Fixes: 88ead68e764c ("tty: Add SBI debug console support to HVC SBI driver")
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
LTGM.
Reviewed-by: Anup Patel <anup@brainfault.org>
Regards,
Anup
> ---
> drivers/tty/hvc/Kconfig | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/hvc/Kconfig b/drivers/tty/hvc/Kconfig
> index 6e05c5c7bca1..c2a4e88b328f 100644
> --- a/drivers/tty/hvc/Kconfig
> +++ b/drivers/tty/hvc/Kconfig
> @@ -108,13 +108,15 @@ config HVC_DCC_SERIALIZE_SMP
>
> config HVC_RISCV_SBI
> bool "RISC-V SBI console support"
> - depends on RISCV_SBI
> + depends on RISCV_SBI && NONPORTABLE
> select HVC_DRIVER
> help
> This enables support for console output via RISC-V SBI calls, which
> - is normally used only during boot to output printk.
> + is normally used only during boot to output printk. This driver
> + conflicts with real console drivers and should not be enabled on
> + systems that directly access the console.
>
> - If you don't know what do to here, say Y.
> + If you don't know what do to here, say N.
>
> config HVCS
> tristate "IBM Hypervisor Virtual Console Server support"
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-02-14 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:34 [PATCH] tty: hvc: Don't enable the RISC-V SBI console by default Palmer Dabbelt
2024-02-14 15:44 ` Paul Walmsley
2024-02-14 15:50 ` Anup Patel [this message]
2024-02-14 15:54 ` Conor Dooley
2024-02-21 19:50 ` 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='CAAhSdy3Tf=9jD1Cd11RjwKyDFPA_gHTqxMXSJ3HwANFFnR-8dA@mail.gmail.com' \
--to=anup@brainfault.org \
--cc=ajones@ventanamicro.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel@esmil.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=palmer@rivosinc.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;
as well as URLs for NNTP newsgroup(s).