All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Jinsong Liu <jinsong.liu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: RE: [PATCH] Revert Jan's patch (c/s 18879) since	 now itcanbe achieved by xenpm tool now
Date: Mon, 22 Dec 2008 10:12:42 +0000	[thread overview]
Message-ID: <494F762A.76E4.0078.0@novell.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC21C7FD9B7@pdsmsx503.ccr.corp.intel.com>

>>> "Liu, Jinsong" <jinsong.liu@intel.com> 22.12.08 10:40 >>>
>Jan Beulich wrote:
>>>>> "Liu, Jinsong" <jinsong.liu@intel.com> 20.12.08 14:37 >>>
>>> Revert Jan's patch (c/s 18879) since now it can be achieved by
>>> xenpm tool now.
>> 
>> Please don't, and rather (as Keir suggested) add an option to also
>> select the initial governor on the command line. While the xenpm tool
>> is nice, older distro-s won't run it by default, and having to fiddle
>> with the system startup scripts or running it manually (which
>> wouldn't necessarily work if you don't do a full install of the Xen
>> tool - e.g. to keep the distro's tools intact) isn't really desirable
>> in certain cases. 
>> 
>> Jan
>
>Jan,
>
>It's good for old distro-s user to use cmdline to set parameter, but I have
>some concern, since in fact cpufreq have 5 governors, with ~20 status
>parameters and ~10 control parameters. If we add option at grub
>cmdline to select initial governor, and add further options to set control
>parameters, it may make confuse for user, especially considered that
>some of the control parameters are governor-dependent (i.e. in c/s
>18879, the control para 'sample rate' and 'upthreshold' can only be used
>for ondemand or conservative governor). User may confuse what the

Which is why they are being parsed in the ondemand governor's source
file...

>default governor is, and what control parameters can be used at grub
>cmdline for that governor.

Anything not applicable would be ignored. I don't think there's much
confusion associated with this.

Jan

  reply	other threads:[~2008-12-22 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 13:37 [PATCH] Revert Jan's patch (c/s 18879) since now it can be achieved by xenpm tool now Liu, Jinsong
2008-12-22  8:55 ` [PATCH] Revert Jan's patch (c/s 18879) since now it canbe " Jan Beulich
2008-12-22  9:40   ` Liu, Jinsong
2008-12-22 10:12     ` Jan Beulich [this message]
2008-12-23  2:29       ` [PATCH] Revert Jan's patch (c/s 18879) since now itcanbe " Liu, Jinsong
2008-12-23  8:38         ` Keir Fraser
2008-12-23  9:02           ` Liu, Jinsong
2008-12-23  9:06             ` Keir Fraser
2008-12-23  9:34               ` [PATCH] Revert Jan's patch (c/s 18879) since nowitcanbe " Jan Beulich

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=494F762A.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=jinsong.liu@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.