On Mon, 30 Jun 2008 17:56:44 -0300
Eduardo M KALINOWSKI <[EMAIL PROTECTED]> wrote:
> charlie derr escreveu:
> > Jochen Schulz wrote:
> >> Hakan BAYINDIR:
> >>> P.S. I cannot send a config.gz since the kernel is prepackaged.
> >>
> >> You'll find the configuration of the currently running kernel in
On Tue, 01 Jul 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
> After subscribing to cpu-freq mailing list and asking the same
> question here, Venkatesh Pallipadi from intel answered my question.
For the records: http://article.gmane.org/gmane.linux.kernel.cpufreq/6441
Regards.
--
To UNSUB
Jochen Schulz wrote:
> Hakan BAYINDIR:
>> After subscribing to cpu-freq mailing list and asking the same question here,
>> Venkatesh Pallipadi from intel answered my question. He said that since
>> voltages
>> in a CPU package is constant across cores, keeping frequencies low on other
>> cores whi
Hakan BAYINDIR:
>
> After subscribing to cpu-freq mailing list and asking the same question here,
> Venkatesh Pallipadi from intel answered my question. He said that since
> voltages
> in a CPU package is constant across cores, keeping frequencies low on other
> cores while clocking one up doesn'
Hakan BAYINDIR wrote:
> Volkan YAZICI wrote:
>> On Tue, 01 Jul 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
>>> #
>>> # CPU Frequency scaling
>>> #
>>> CONFIG_CPU_FREQ=y
>>> CONFIG_CPU_FREQ_TABLE=m
>>> # CONFIG_CPU_FREQ_DEBUG is not set
>>> CONFIG_CPU_FREQ_STAT=m
>>> # CONFIG_CPU_FREQ_STAT_DETA
Volkan YAZICI wrote:
> On Tue, 01 Jul 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
>> #
>> # CPU Frequency scaling
>> #
>> CONFIG_CPU_FREQ=y
>> CONFIG_CPU_FREQ_TABLE=m
>> # CONFIG_CPU_FREQ_DEBUG is not set
>> CONFIG_CPU_FREQ_STAT=m
>> # CONFIG_CPU_FREQ_STAT_DETAILS is not set
>> CONFIG_CPU_FREQ
On Tue, 01 Jul 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
> #
> # CPU Frequency scaling
> #
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_TABLE=m
> # CONFIG_CPU_FREQ_DEBUG is not set
> CONFIG_CPU_FREQ_STAT=m
> # CONFIG_CPU_FREQ_STAT_DETAILS is not set
> CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
> # C
On Tue, 01 Jul 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
> Yepp the config is under /boot with the name config-.
So? Can we see it, please?
Regards.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Jun 30, 2008 at 23:41:26 +0300, Hakan BAYINDIR wrote:
> Jochen Schulz wrote:
> > Hakan BAYINDIR:
> >
> >> P.S. I cannot send a config.gz since the kernel is prepackaged.
> >>
> >
> > You'll find the configuration of the currently running kernel in
> > /proc/config.gz. At least Debia
> charlie derr escreveu:
>> Jochen Schulz wrote:
>>> Hakan BAYINDIR:
P.S. I cannot send a config.gz since the kernel is prepackaged.
>>>
>>> You'll find the configuration of the currently running kernel in
>>> /proc/config.gz. At least Debian kernels have that feature enabled by=
>>> default.
charlie derr escreveu:
Jochen Schulz wrote:
Hakan BAYINDIR:
P.S. I cannot send a config.gz since the kernel is prepackaged.
You'll find the configuration of the currently running kernel in
/proc/config.gz. At least Debian kernels have that feature enabled by
default.
J.
It would sure be n
Jochen Schulz wrote:
Hakan BAYINDIR:
P.S. I cannot send a config.gz since the kernel is prepackaged.
You'll find the configuration of the currently running kernel in
/proc/config.gz. At least Debian kernels have that feature enabled by
default.
J.
It would sure be nice if that were the cas
Hakan BAYINDIR:
> Jochen Schulz wrote:
>> Hakan BAYINDIR:
>>
>>> P.S. I cannot send a config.gz since the kernel is prepackaged.
>>
>> You'll find the configuration of the currently running kernel in
>> /proc/config.gz. At least Debian kernels have that feature enabled by
>> default.
>
> Unfort
Jochen Schulz wrote:
> Hakan BAYINDIR:
>
>> P.S. I cannot send a config.gz since the kernel is prepackaged.
>>
>
> You'll find the configuration of the currently running kernel in
> /proc/config.gz. At least Debian kernels have that feature enabled by
> default.
>
> J.
>
Unfortunately th
Hakan BAYINDIR:
>
> P.S. I cannot send a config.gz since the kernel is prepackaged.
You'll find the configuration of the currently running kernel in
/proc/config.gz. At least Debian kernels have that feature enabled by
default.
J.
--
Looking into my eyes is the only way you'll know I'm telling
Volkan YAZICI wrote:
> Hi,
>
> On Sun, 29 Jun 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
>
>> I'm running debian testing on a Intel Core2Quad Q6600 CPU with 4
>> gigabytes of RAM for 7 months. Until 2.6.22, the kernel was scaling each
>> of my cores independently of each other but starting
Hi,
On Sun, 29 Jun 2008, Hakan BAYINDIR <[EMAIL PROTECTED]> writes:
> I'm running debian testing on a Intel Core2Quad Q6600 CPU with 4
> gigabytes of RAM for 7 months. Until 2.6.22, the kernel was scaling each
> of my cores independently of each other but starting with 2.6.22, every
> core is runn
Hi,
I'm running debian testing on a Intel Core2Quad Q6600 CPU with 4
gigabytes of RAM for 7 months. Until 2.6.22, the kernel was scaling each
of my cores independently of each other but starting with 2.6.22, every
core is running in the same frequency. While this doesn't pose any
stability or perf
18 matches
Mail list logo
