From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Nicolas Pitre <npitre@baylibre.com>,
Calixte Pernot <calixte.pernot@grenoble-inp.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] vt: Add enable module parameter
Date: Mon, 26 Jan 2026 11:57:39 +0100 [thread overview]
Message-ID: <2026012604-yelling-hurdle-ebf9@gregkh> (raw)
In-Reply-To: <40fa8cab-af36-4420-9099-511474833fe1@redhat.com>
On Mon, Jan 26, 2026 at 11:49:45AM +0100, Jocelyn Falempe wrote:
> On 26/01/2026 11:30, Greg Kroah-Hartman wrote:
> > On Mon, Jan 26, 2026 at 11:20:21AM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Jan 26, 2026 at 10:43:35AM +0100, Jocelyn Falempe wrote:
> > > > On 26/01/2026 10:33, Greg Kroah-Hartman wrote:
> > > > > On Mon, Jan 26, 2026 at 10:21:50AM +0100, Jocelyn Falempe wrote:
> > > > > > This allows to build the kernel with CONFIG_VT enabled, and choose
> > > > > > on the kernel command line to enable it or not.
> > > > >
> > > > > This says what is happening, but not why?
> > > > >
> > > > > > Add vt.enable=1 to force enable, or vt.enable=0 to force disable.
> > > > >
> > > > > Why are we using a 1990's technology for a new feature? What is this
> > > > > going to allow to have happen? Who needs/wants this? Who will use it?
> > > > > For what?
> > > >
> > > > The goal is to ease the transition to disable CONFIG_VT.
> > > >
> > > > So if this is merged, you can boot without VT on any Linux distribution,
> > > > without rebuilding the kernel.
> > >
> > > But that's a distro-specific thing, the distro should be enabling or
> > > disabling the option as it needs, it should not be a user-configurable
> > > boot-time selection option as userspace depends entirely on this either
> > > being there or not. Why would you have a kernel with both options but
> > > userspace without that?
> >
> > And to follow-up on this, if a distro wanted to support this, why not
> > just provide 2 different kernel images? One with this enabled and one
> > without? It's up to the distro to support such a thing, not the kernel
> > community, right?
>
> That's clearly not an option, they will prefer to keep VT enabled forever
> than adding yet another kernel package.
But that's a distro's choice to make, why are you forcing this onto the
kernel? Either a distro wants to support a userspace with VT enabled,
or not. So then choose the kernel option you wish to have here and away
you go!
> And for distributions that already have kernel and kernel-rt, that
> means maintaining 4 kernels for all combination.
Again, that's a distro choice, you are now forcing us to maintain the
option due to the lack of an agreement in your organization :)
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-26 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 9:21 [PATCH] vt: Add enable module parameter Jocelyn Falempe
2026-01-26 9:33 ` Greg Kroah-Hartman
2026-01-26 9:43 ` Jocelyn Falempe
2026-01-26 10:20 ` Greg Kroah-Hartman
2026-01-26 10:30 ` Greg Kroah-Hartman
2026-01-26 10:49 ` Jocelyn Falempe
2026-01-26 10:57 ` Greg Kroah-Hartman [this message]
2026-01-26 10:48 ` Jocelyn Falempe
2026-01-26 10:59 ` Greg Kroah-Hartman
2026-01-26 12:26 ` Jocelyn Falempe
2026-01-26 12:46 ` Greg Kroah-Hartman
2026-01-26 13:05 ` Jocelyn Falempe
2026-01-26 14:36 ` Greg Kroah-Hartman
2026-01-26 17:24 ` Nicolas Pitre
2026-01-26 22:59 ` Jocelyn Falempe
2026-01-26 23:00 ` Jocelyn Falempe
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=2026012604-yelling-hurdle-ebf9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=calixte.pernot@grenoble-inp.org \
--cc=jfalempe@redhat.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=npitre@baylibre.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