[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87bkignzdg.fsf@meer.lwn.net>
Date: Fri, 19 May 2023 08:56:43 -0600
From: Jonathan Corbet <corbet@....net>
To: Yan-Jie Wang <yanjiewtw@...il.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Randy Dunlap <rdunlap@...radead.org>,
Andre Przywara <andre.przywara@....com>,
Avi Kivity <avi@...hat.com>,
Yan-Jie Wang <yanjiewtw@...il.com>,
Ching-Chun Huang <jserv@...s.ncku.edu.tw>, trivial@...nel.org,
kvm@...r.kernel.org
Subject: Re: [PATCH v2] docs: clarify KVM related kernel parameters'
descriptions
Yan-Jie Wang <yanjiewtw@...il.com> writes:
> The descriptions of certain KVM related kernel parameters can be
> confusing. They state "Disable ...," which may make people think that
> setting them to 1 will disable the associated feature when in fact the
> opposite is true.
>
> This commit addresses this issue by revising the descriptions of these
> parameters by using "Control..." rather than "Enable/Disable...".
> 1==enabled or 0==disabled can be communicated by the description of
> default value such as "1 (enabled)" or "0 (disabled)".
>
> Also update the description of KVM's default value for kvm-intel.nested
> as it is enabled by default.
>
> Signed-off-by: Yan-Jie Wang <yanjiewtw@...il.com>
> ---
> Changes in v2:
> - Revise the descriptions based on Sean's suggesstion.
> - Fix the wrong default value of kvm-intel.nested
> ---
> .../admin-guide/kernel-parameters.txt | 53 ++++++++++---------
> 1 file changed, 29 insertions(+), 24 deletions(-)
Applied, thanks.
jon
Powered by blists - more mailing lists