From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] cpufreq: allow ordinary boolean options to be passed on the command line Date: Mon, 2 Nov 2015 11:11:41 +0000 Message-ID: <563744ED.5040106@citrix.com> References: <5633BBAB02000078000B0617@prv-mh.provo.novell.com> <5633C36E.7040508@citrix.com> <56374F0C02000078000B0AA5@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZtD1i-0001TU-Qb for xen-devel@lists.xenproject.org; Mon, 02 Nov 2015 11:11:50 +0000 In-Reply-To: <56374F0C02000078000B0AA5@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Jinsong Liu , xen-devel List-Id: xen-devel@lists.xenproject.org On 02/11/15 10:54, Jan Beulich wrote: >>>> On 30.10.15 at 20:22, wrote: >> On 30/10/15 17:49, Jan Beulich wrote: >>> I was quite surprised to find "cpufreq=off" not doing what one would >>> expect it to do. Fix this. >>> >>> Signed-off-by: Jan Beulich >>> >>> --- a/docs/misc/xen-command-line.markdown >>> +++ b/docs/misc/xen-command-line.markdown >>> @@ -391,11 +391,12 @@ If set, force use of the performance cou >>> available support. >>> >>> ### cpufreq >>> -> `= dom0-kernel | none | xen[,[powersave|performance|ondemand|userspace][,][,[][,[verbose]]]]` >>> +> `= none | {{ | xen } [:[powersave|performance|ondemand|userspace][,][,[][,[verbose]]]]} | dom0-kernel` >> If I am reading the parsing correctly below, the insertion if ':' is to >> match the previous behaviour? (or have I missed something?) > We've always supported , and : there. I do think that documenting > comma here is bad (since it's also used as the separator between > sub-options), and hence I've taken the opportunity to make this > match other command line options (where we generally use colon > for separation of main and sub-options). Agreed. Reviewed-by: Andrew Cooper