From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Abhishek Bhardwaj <abhishekbh@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Anthony Steinhauser <asteinhauser@google.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Mark Gross <mgross@linux.intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Tony Luck <tony.luck@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Waiman Long <longman@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
kvm@vger.kernel.org, x86@kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v5] x86/speculation/l1tf: Add KConfig for setting the L1D cache flush mode
Date: Sun, 16 Aug 2020 09:47:25 +0200 [thread overview]
Message-ID: <20200816074725.GF21914@zn.tnic> (raw)
In-Reply-To: <87y2ntotah.fsf@nanos.tec.linutronix.de>
+ Masami.
On Thu, Jul 09, 2020 at 12:51:34PM +0200, Thomas Gleixner wrote:
> Abhishek Bhardwaj <abhishekbh@google.com> writes:
> > This change adds a new kernel configuration that sets the l1d cache
> > flush setting at compile time rather than at run time.
> >
> > The reasons for this change are as follows -
> >
> > - Kernel command line arguments are getting unwieldy. These parameters
> > are not a scalable way to set the kernel config. They're intended as a
> > super limited way for the bootloader to pass info to the kernel and
> > also as a way for end users who are not compiling the kernel themselves
> > to tweak the kernel behavior.
> >
> > - Also, if a user wants this setting from the start. It's a definite
> > smell that it deserves to be a compile time thing rather than adding
> > extra code plus whatever miniscule time at runtime to pass an
> > extra argument.
> >
> > - Finally, it doesn't preclude the runtime / kernel command line way.
> > Users are free to use those as well.
>
> TBH, I don't see why this is a good idea.
>
> 1) I'm not following your argumentation that the command line option is
> a poor Kconfig replacement. The L1TF mode is a boot time (module
> load time) decision and the command line parameter is there to
> override the carefully chosen and sensible default behaviour.
>
> 2) You can add the desired mode to the compiled in (partial) kernel
> command line today.
>
> 3) Boot loaders are well capable of handling large kernel command lines
> and the extra time spend for reading the parameter does not matter
> at all.
Also, there's Documentation/admin-guide/bootconfig.rst which extends
cmdline options handling even more and allows for passing options in a
file. Maybe that'll help in this case too.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2020-08-16 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:47 [PATCH v5] x86/speculation/l1tf: Add KConfig for setting the L1D cache flush mode Abhishek Bhardwaj
2020-07-09 10:51 ` Thomas Gleixner
2020-07-09 19:42 ` Doug Anderson
2020-07-09 22:43 ` mark gross
[not found] ` <CA+noqojC3z_o8+_Ek=17XxjVC+efoLHsUh08cbcTDrgxMcEGNQ@mail.gmail.com>
2020-07-09 23:29 ` Doug Anderson
2020-07-17 16:22 ` Thomas Gleixner
2020-07-17 17:19 ` Doug Anderson
2020-08-16 7:47 ` Borislav Petkov [this message]
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=20200816074725.GF21914@zn.tnic \
--to=bp@alien8.de \
--cc=abhishekbh@google.com \
--cc=asteinhauser@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgross@linux.intel.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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