Patch looks good.
Acked-by: Venkatesh Pallipadi
On Mon, Oct 22, 2012 at 2:37 PM, Suresh Siddha
wrote:
>
> Thomas, You wanted to run some tests with this, right? Please give it a
> try and see if this is ok to be pushed to the -tip.
>
> thanks,
> suresh
> --8<--
> From: Suresh Siddha
>
Patch looks good.
Acked-by: Venkatesh Pallipadi ve...@google.com
On Mon, Oct 22, 2012 at 2:37 PM, Suresh Siddha
suresh.b.sid...@intel.com wrote:
Thomas, You wanted to run some tests with this, right? Please give it a
try and see if this is ok to be pushed to the -tip.
thanks,
suresh
--8--
On Tue, Feb 12, 2008 at 12:10:54AM +0100, R. J. Wysocki wrote:
> On Monday, 11 of February 2008, Lukas Hejtmanek wrote:
> > Hello,
>
> Hi,
>
> > 2.6.25-rc1 takes really long time till it suspends (about 30-40secs, used to
> > be about 5 secs at all) and it is resuming about few minutes. While
On Mon, Feb 11, 2008 at 12:06:50PM -0800, Venki Pallipadi wrote:
> On Mon, Feb 11, 2008 at 05:37:04PM -0200, Carlos R. Mafra wrote:
> > Pallipadi, Venkatesh wrote:
> > >
> > > Can you send me the output of acpidump and full dmesg to me. Looks like
> > > it
On Mon, Feb 11, 2008 at 05:37:04PM -0200, Carlos R. Mafra wrote:
> Pallipadi, Venkatesh wrote:
> >
> > Can you send me the output of acpidump and full dmesg to me. Looks like
> > it is a platform issue due to which we cannot use C1 mwait idle during
> > suspend resume, something similar to issue
On Mon, Feb 11, 2008 at 05:37:04PM -0200, Carlos R. Mafra wrote:
Pallipadi, Venkatesh wrote:
Can you send me the output of acpidump and full dmesg to me. Looks like
it is a platform issue due to which we cannot use C1 mwait idle during
suspend resume, something similar to issue we had
On Tue, Feb 12, 2008 at 12:10:54AM +0100, R. J. Wysocki wrote:
On Monday, 11 of February 2008, Lukas Hejtmanek wrote:
Hello,
Hi,
2.6.25-rc1 takes really long time till it suspends (about 30-40secs, used to
be about 5 secs at all) and it is resuming about few minutes. While
On Mon, Feb 11, 2008 at 12:06:50PM -0800, Venki Pallipadi wrote:
On Mon, Feb 11, 2008 at 05:37:04PM -0200, Carlos R. Mafra wrote:
Pallipadi, Venkatesh wrote:
Can you send me the output of acpidump and full dmesg to me. Looks like
it is a platform issue due to which we cannot use C1
On Fri, Feb 08, 2008 at 11:28:48AM +0100, Andi Kleen wrote:
>
> > - set_cpus_allowed(current, tmp);
> > + smp_mb();
> > + /* kick all the CPUs so that they exit out of pm_idle */
> > + smp_call_function(do_nothing, NULL, 0, 0);
>
> I think the last argument (wait) needs to be 1 to make
On Fri, Feb 08, 2008 at 11:28:48AM +0100, Andi Kleen wrote:
- set_cpus_allowed(current, tmp);
+ smp_mb();
+ /* kick all the CPUs so that they exit out of pm_idle */
+ smp_call_function(do_nothing, NULL, 0, 0);
I think the last argument (wait) needs to be 1 to make sure it is
Earlier commit 40d6a146629b98d8e322b6f9332b182c7cbff3df
added smp_call_function in cpu_idle_wait() to kick cpus that are in tickless
idle. Looking at cpu_idle_wait code at that time, code seemed to be
over-engineered for a case which is rarely used (while changing idle handler).
Below is a
Earlier commit 40d6a146629b98d8e322b6f9332b182c7cbff3df
added smp_call_function in cpu_idle_wait() to kick cpus that are in tickless
idle. Looking at cpu_idle_wait code at that time, code seemed to be
over-engineered for a case which is rarely used (while changing idle handler).
Below is a
On Thu, Jan 17, 2008 at 11:40:32AM -0800, Andrew Morton wrote:
> On Thu, 17 Jan 2008 11:22:19 -0800 "Pallipadi, Venkatesh" <[EMAIL PROTECTED]>
> wrote:
>
> >
> > The problem is
> > >> modprobe:2584 conflicting cache attribute 5000-50001000
> > >> uncached<->default
> >
> > Some address
On Thu, Jan 17, 2008 at 11:52:43PM +0100, Andreas Herrmann3 wrote:
> On Thu, Jan 17, 2008 at 11:15:05PM +0100, Ingo Molnar wrote:
> >
> > * Andreas Herrmann3 <[EMAIL PROTECTED]> wrote:
> >
> > > On Thu, Jan 17, 2008 at 10:42:09PM +0100, Ingo Molnar wrote:
> > > >
> > > > * Siddha, Suresh B
On Thu, Jan 17, 2008 at 04:14:37PM -0500, Jeff Dike wrote:
> On Thu, Jan 17, 2008 at 11:38:53AM -0800, Pallipadi, Venkatesh wrote:
> > Apart from unxlate, there is also ioremap_wc which is defined in the
> > same way.
>
> And while we're on the subject, what's the deal with these, in
>
On Thu, Jan 17, 2008 at 04:14:37PM -0500, Jeff Dike wrote:
On Thu, Jan 17, 2008 at 11:38:53AM -0800, Pallipadi, Venkatesh wrote:
Apart from unxlate, there is also ioremap_wc which is defined in the
same way.
And while we're on the subject, what's the deal with these, in
On Thu, Jan 17, 2008 at 11:52:43PM +0100, Andreas Herrmann3 wrote:
On Thu, Jan 17, 2008 at 11:15:05PM +0100, Ingo Molnar wrote:
* Andreas Herrmann3 [EMAIL PROTECTED] wrote:
On Thu, Jan 17, 2008 at 10:42:09PM +0100, Ingo Molnar wrote:
* Siddha, Suresh B [EMAIL PROTECTED] wrote:
On Thu, Jan 17, 2008 at 11:40:32AM -0800, Andrew Morton wrote:
On Thu, 17 Jan 2008 11:22:19 -0800 Pallipadi, Venkatesh [EMAIL PROTECTED]
wrote:
The problem is
modprobe:2584 conflicting cache attribute 5000-50001000
uncached-default
Some address range here is being mapped
On Wed, Jan 16, 2008 at 10:14:00AM +0200, Mika Penttilä wrote:
> [EMAIL PROTECTED] kirjoitti:
> >KERNPG_TABLE was a bug in earlier patch. Remove it from pte.
> >pte_val() check is redundant as this routine is called immediately after a
> >ptepage is allocated afresh.
> >
> >Signed-off-by:
On Wed, Jan 16, 2008 at 07:57:48PM +0100, Andreas Herrmann wrote:
> Hi,
>
> I just want to report that the PAT support in x86/mm causes crashes
> on two of my test machines. On both boxes the SATA detection does
> not work when the PAT support is patched into the kernel.
>
> Symptoms are as
On Wed, Jan 16, 2008 at 07:57:48PM +0100, Andreas Herrmann wrote:
Hi,
I just want to report that the PAT support in x86/mm causes crashes
on two of my test machines. On both boxes the SATA detection does
not work when the PAT support is patched into the kernel.
Symptoms are as follows --
On Wed, Jan 16, 2008 at 10:14:00AM +0200, Mika Penttilä wrote:
[EMAIL PROTECTED] kirjoitti:
KERNPG_TABLE was a bug in earlier patch. Remove it from pte.
pte_val() check is redundant as this routine is called immediately after a
ptepage is allocated afresh.
Signed-off-by: Venkatesh Pallipadi
On Tue, Jan 15, 2008 at 09:16:50AM -0800, Jeremy Fitzhardinge wrote:
> Ingo Molnar wrote:
> >-#define _PAGE_PRESENT (_AC(1, UL)<<_PAGE_BIT_PRESENT)
> >-#define _PAGE_RW(_AC(1, UL)<<_PAGE_BIT_RW)
> >-#define _PAGE_USER (_AC(1, UL)<<_PAGE_BIT_USER)
> >-#define _PAGE_PWT (_AC(1,
On Tue, Jan 15, 2008 at 09:16:50AM -0800, Jeremy Fitzhardinge wrote:
Ingo Molnar wrote:
-#define _PAGE_PRESENT (_AC(1, UL)_PAGE_BIT_PRESENT)
-#define _PAGE_RW(_AC(1, UL)_PAGE_BIT_RW)
-#define _PAGE_USER (_AC(1, UL)_PAGE_BIT_USER)
-#define _PAGE_PWT (_AC(1, UL)_PAGE_BIT_PWT)
Reintroduce run time configurable max_cstate for !CPU_IDLE case.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
===
--- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
Reintroduce run time configurable max_cstate for !CPU_IDLE case.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
===
--- linux-2.6.24-rc.orig/drivers/acpi/processor_idle.c
On Wed, Dec 19, 2007 at 08:32:55PM +0100, Ingo Molnar wrote:
>
> * Venki Pallipadi <[EMAIL PROTECTED]> wrote:
>
> > Aviod TLB flush IPIs during C3 states by voluntary leave_mm() before
> > entering C3.
> >
> > The performance impact of TL
On Wed, Dec 19, 2007 at 11:48:14AM -0800, H. Peter Anvin wrote:
> Ingo Molnar wrote:
> >
> >i dont think it's required for C3 to even turn off any portion of the
> >CPU - if an interrupt arrives after the C3 sequence is initiated but
> >just before dirty cachelines have been flushed then the CPU
On Wed, Dec 19, 2007 at 08:40:32PM +0100, Ingo Molnar wrote:
>
> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
> > Ingo Molnar wrote:
> >> * Venki Pallipadi <[EMAIL PROTECTED]> wrote:
> >>
> >>> Aviod TLB flush IPIs during C3
Aviod TLB flush IPIs during C3 states by voluntary leave_mm()
before entering C3.
The performance impact of TLB flush on C3 should not be significant with
respect to C3 wakeup latency. Also, CPUs tend to flush TLB in hardware while in
C3 anyways.
On a 8 logical CPU system, running make -j2, the
Aviod TLB flush IPIs during C3 states by voluntary leave_mm()
before entering C3.
The performance impact of TLB flush on C3 should not be significant with
respect to C3 wakeup latency. Also, CPUs tend to flush TLB in hardware while in
C3 anyways.
On a 8 logical CPU system, running make -j2, the
On Wed, Dec 19, 2007 at 08:40:32PM +0100, Ingo Molnar wrote:
* H. Peter Anvin [EMAIL PROTECTED] wrote:
Ingo Molnar wrote:
* Venki Pallipadi [EMAIL PROTECTED] wrote:
Aviod TLB flush IPIs during C3 states by voluntary leave_mm() before
entering C3.
The performance impact of TLB
On Wed, Dec 19, 2007 at 11:48:14AM -0800, H. Peter Anvin wrote:
Ingo Molnar wrote:
i dont think it's required for C3 to even turn off any portion of the
CPU - if an interrupt arrives after the C3 sequence is initiated but
just before dirty cachelines have been flushed then the CPU can just
On Wed, Dec 19, 2007 at 08:32:55PM +0100, Ingo Molnar wrote:
* Venki Pallipadi [EMAIL PROTECTED] wrote:
Aviod TLB flush IPIs during C3 states by voluntary leave_mm() before
entering C3.
The performance impact of TLB flush on C3 should not be significant
with respect to C3 wakeup
On Fri, Dec 14, 2007 at 01:42:12AM +0100, Andi Kleen wrote:
> > +void __cpuinit pat_init(void)
> > +{
> > + /* Set PWT+PCD to Write-Combining. All other bits stay the same */
> > + if (cpu_has_pat) {
>
> All the old CPUs (PPro etc.) with known PAT bugs need to clear this flag
> now in their
On Fri, Dec 14, 2007 at 01:42:12AM +0100, Andi Kleen wrote:
+void __cpuinit pat_init(void)
+{
+ /* Set PWT+PCD to Write-Combining. All other bits stay the same */
+ if (cpu_has_pat) {
All the old CPUs (PPro etc.) with known PAT bugs need to clear this flag
now in their CPU init
elow over rc2 and see whether it fixes the problem.
Looking at the code, it should fix the problem. If it does not, can you send
me the output of acpidump from your system. That will help to look further
into this. You can get acpidump from latest pmtools package here.
www.kernel.org/pub/linux/ker
.
www.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
Thanks,
Venki
Test patch for the bug report at
https://bugzilla.redhat.com/show_bug.cgi?id=312201
Signed-off-by: Venki Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.24-rc/drivers/acpi/processor_idle.c
Current idle time in kstat is based on jiffies and is coarse grained.
tick_sched.idle_sleeptime is making some attempt to keep track of
idle time in a fine grained manner. But, it is not handling
the time spent in interrupts fully.
Make tick_sched.idle_sleeptime accurate with respect to time
Current idle time in kstat is based on jiffies and is coarse grained.
tick_sched.idle_sleeptime is making some attempt to keep track of
idle time in a fine grained manner. But, it is not handling
the time spent in interrupts fully.
Make tick_sched.idle_sleeptime accurate with respect to time
On Tue, Aug 07, 2007 at 07:13:36PM +0400, Oleg Nesterov wrote:
> On 08/07, Gautham R Shenoy wrote:
> >
> > After some debugging, I saw that the hang occured because
> > the high prio process was stuck in a loop doing yield() inside
> > wait_task_inactive(). Description follows:
> >
> > Say a
On Tue, Aug 07, 2007 at 07:13:36PM +0400, Oleg Nesterov wrote:
On 08/07, Gautham R Shenoy wrote:
After some debugging, I saw that the hang occured because
the high prio process was stuck in a loop doing yield() inside
wait_task_inactive(). Description follows:
Say a high-prio task
On Tue, Jul 31, 2007 at 05:38:08PM +0200, Eric Sesterhenn / Snakebyte wrote:
> * Pallipadi, Venkatesh ([EMAIL PROTECTED]) wrote:
> > This means things should work fine with processor.max_cstate=2 boot
> > option
> > as well. Can you please double check that.
>
> yes, system boots fine with this
On Tue, Jul 31, 2007 at 05:38:08PM +0200, Eric Sesterhenn / Snakebyte wrote:
* Pallipadi, Venkatesh ([EMAIL PROTECTED]) wrote:
This means things should work fine with processor.max_cstate=2 boot
option
as well. Can you please double check that.
yes, system boots fine with this kernel
Add another PCI ID for ICH7 force hpet.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.21/arch/i386/kernel/quirks.c
===
--- linux-2.6.21.orig/arch/i386/kernel/quirks.c
+++
Enable HPET later during boot, after the force detect in PCI quirks.
Also add a call to repeat the force enabling at resume time.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c | 50 +++-
include/asm-i386/hpet.h
force_enable hpet for ICH5.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c |2
arch/i386/kernel/quirks.c | 101 +-
include/asm-i386/hpet.h |2
include/linux/pci_ids.h |1
4 files changed, 103
A bugfix in ich5 hpet force detect which caused resumes to fail.
Thanks to Udo A Steinberg for reporting the problem.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
---
arch/i386/kernel/quirks.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
Force detect and/or enable HPET on ICH chipsets. This patch just handles the
detection part and following patches use this information. Adds a function
to repeat the force enabling during resume time.
Using HPET this way, instead of PIT increases the time CPUs can
reside in C-state when system
Restructure and rename legacy replacement mode HPET timer support.
Just the code structural changes and should be zero functionality change.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
---
Index: linux-2.6.22-rc5/arch/i386/kernel/hpet.c
Auto-detect the presence of HPET on ICH5 or newer platforms and enable
HPET for broadcast timer. This gives a bigger upperlimit for tickless time
tick and improves the power consumption in comparison to PIT as broadcast timer.
This patch:
Change the broadcast timer, if a timer with higher
Auto-detect the presence of HPET on ICH5 or newer platforms and enable
HPET for broadcast timer. This gives a bigger upperlimit for tickless time
tick and improves the power consumption in comparison to PIT as broadcast timer.
This patch:
Change the broadcast timer, if a timer with higher
Restructure and rename legacy replacement mode HPET timer support.
Just the code structural changes and should be zero functionality change.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
---
Index: linux-2.6.22-rc5/arch/i386/kernel/hpet.c
Force detect and/or enable HPET on ICH chipsets. This patch just handles the
detection part and following patches use this information. Adds a function
to repeat the force enabling during resume time.
Using HPET this way, instead of PIT increases the time CPUs can
reside in C-state when system
Enable HPET later during boot, after the force detect in PCI quirks.
Also add a call to repeat the force enabling at resume time.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
---
arch/i386/kernel/hpet.c | 50 +++-
include/asm-i386/hpet.h |
force_enable hpet for ICH5.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
---
arch/i386/kernel/hpet.c |2
arch/i386/kernel/quirks.c | 101 +-
include/asm-i386/hpet.h |2
include/linux/pci_ids.h |1
4 files changed, 103
A bugfix in ich5 hpet force detect which caused resumes to fail.
Thanks to Udo A Steinberg for reporting the problem.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
---
arch/i386/kernel/quirks.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
Add another PCI ID for ICH7 force hpet.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.21/arch/i386/kernel/quirks.c
===
--- linux-2.6.21.orig/arch/i386/kernel/quirks.c
+++
Documentation changes based on Pavel's feedback.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/Documentation/cpuidle/sysfs.txt
===
--- linux-2.6.22-rc-mm.orig/Documentation/cpuidle/sysfs.txt
Introduce a governor rating scheme to pick the right governor by default.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/include/linux/cpuidle.h
===
---
Make default cpuidle sysfs to show current_governor and current_driver in
read-only mode. More elaborate available_governors and available_drivers with
writeable current_governor and current_driver interface only appear with
"cpuidle_sysfs_switch" boot parameter.
Signed-off-by: Venkatesh
Change the C-state early break out algorithm in menu governor.
We only look at early breakouts that result in wakeups shorter than idle state's
target_residency. If such a breakout is frequent enough, eliminate the
particular idle state upto a timeout period.
Signed-off-by: Venkatesh Pallipadi
Fix the uninitialized usage of ret.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/cpuidle/sysfs.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/sysfs.c 2007-06-04
Keep /proc/acpi/processor/CPU*/power around for a while as powertop depends
on it. It will be marked deprecated and removed in future. powertop can use
cpuidle interfaces instead.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/acpi/processor_idle.c
Compile fix for menu governor.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/cpuidle/governors/menu.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/governors/menu.c2007-06-01
Len,
Following are a bunch of small changes to cpuidle trying to prepare it
for mainline. Some of the changes are just the compile timer errors/warnings
and you probably already have them in acpi-test.
Should apply cleanly to latest acpi-test. Please include in acpi-test.
Thanks,
Venki
This
Len,
Following are a bunch of small changes to cpuidle trying to prepare it
for mainline. Some of the changes are just the compile timer errors/warnings
and you probably already have them in acpi-test.
Should apply cleanly to latest acpi-test. Please include in acpi-test.
Thanks,
Venki
This
Compile fix for menu governor.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/drivers/cpuidle/governors/menu.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/governors/menu.c2007-06-01
Keep /proc/acpi/processor/CPU*/power around for a while as powertop depends
on it. It will be marked deprecated and removed in future. powertop can use
cpuidle interfaces instead.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/drivers/acpi/processor_idle.c
Fix the uninitialized usage of ret.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/drivers/cpuidle/sysfs.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/sysfs.c 2007-06-04
15:44:17.0
Change the C-state early break out algorithm in menu governor.
We only look at early breakouts that result in wakeups shorter than idle state's
target_residency. If such a breakout is frequent enough, eliminate the
particular idle state upto a timeout period.
Signed-off-by: Venkatesh Pallipadi
Make default cpuidle sysfs to show current_governor and current_driver in
read-only mode. More elaborate available_governors and available_drivers with
writeable current_governor and current_driver interface only appear with
cpuidle_sysfs_switch boot parameter.
Signed-off-by: Venkatesh
Introduce a governor rating scheme to pick the right governor by default.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/include/linux/cpuidle.h
===
---
Documentation changes based on Pavel's feedback.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/Documentation/cpuidle/sysfs.txt
===
--- linux-2.6.22-rc-mm.orig/Documentation/cpuidle/sysfs.txt
On Fri, Jun 01, 2007 at 02:41:57PM -0700, Jesse Barnes wrote:
> On Friday, June 1, 2007 2:19:43 Andi Kleen wrote:
> > And normally the MTRRs win, don't they (if I remember the table correctly)
> > So if the MTRR says UC and PAT disagrees it might not actually help
>
> I just checked, yes the
On Fri, Jun 01, 2007 at 02:41:57PM -0700, Jesse Barnes wrote:
On Friday, June 1, 2007 2:19:43 Andi Kleen wrote:
And normally the MTRRs win, don't they (if I remember the table correctly)
So if the MTRR says UC and PAT disagrees it might not actually help
I just checked, yes the MTRRs win
Add a flag in /proc/timer_stats to indicate deferrable timers. This will let
developers/users to differentiate between types of tiemrs in /proc/timer_stats.
Deferrable timer and normal timer will appear in /proc/timer_stats as below.
10D, 1 swapper queue_delayed_work_on
On Wed, May 30, 2007 at 01:30:39PM -0700, Stephen Hemminger wrote:
> On Wed, 30 May 2007 12:55:51 -0700 (PDT)
> David Miller <[EMAIL PROTECTED]> wrote:
>
> > From: Patrick McHardy <[EMAIL PROTECTED]>
> > Date: Wed, 30 May 2007 20:42:32 +0200
> >
> > > Stephen Hemminger wrote:
> > > >>>Index:
On Wed, May 30, 2007 at 12:55:51PM -0700, David Miller wrote:
> From: Patrick McHardy <[EMAIL PROTECTED]>
> Date: Wed, 30 May 2007 20:42:32 +0200
>
> > Stephen Hemminger wrote:
> > >>>Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
> >
On Wed, May 30, 2007 at 08:42:32PM +0200, Patrick McHardy wrote:
> Stephen Hemminger wrote:
> >>>Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
> >>>===
> >>>--- linux-2.6.22-rc-mm.orig/net/sched/sch_generic.c2007-05-24
>
On Wed, May 30, 2007 at 12:55:51PM -0700, David Miller wrote:
From: Patrick McHardy [EMAIL PROTECTED]
Date: Wed, 30 May 2007 20:42:32 +0200
Stephen Hemminger wrote:
Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
===
---
On Wed, May 30, 2007 at 01:30:39PM -0700, Stephen Hemminger wrote:
On Wed, 30 May 2007 12:55:51 -0700 (PDT)
David Miller [EMAIL PROTECTED] wrote:
From: Patrick McHardy [EMAIL PROTECTED]
Date: Wed, 30 May 2007 20:42:32 +0200
Stephen Hemminger wrote:
Index:
Add a flag in /proc/timer_stats to indicate deferrable timers. This will let
developers/users to differentiate between types of tiemrs in /proc/timer_stats.
Deferrable timer and normal timer will appear in /proc/timer_stats as below.
10D, 1 swapper queue_delayed_work_on
On Wed, May 30, 2007 at 08:42:32PM +0200, Patrick McHardy wrote:
Stephen Hemminger wrote:
Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
===
--- linux-2.6.22-rc-mm.orig/net/sched/sch_generic.c2007-05-24
On Thu, May 24, 2007 at 05:04:13PM -0700, H. Peter Anvin wrote:
>
> If they grow slowly from the bottom, I guess we could simply allocate
> space in the vector byte by byte instead. Either way, it means more
> work whenever anything has to change.
>
hpa,
Below patch adds a new word for
On Tue, May 29, 2007 at 11:22:30AM -0700, Randy Dunlap wrote:
> On Tue, 29 May 2007 10:58:21 -0700 Venki Pallipadi wrote:
>
> >
> >
> > Below are a bunch of random timers, that were active on my system,
> > that can better be round_jiffies() aligned.
>
> and
round_jiffies() for i386 and x86-64 non-critical/corrected MCE polling.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/arch/x86_64/kernel/mce.c
===
---
round_jiffies for net dev watchdog timer.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
===
--- linux-2.6.22-rc-mm.orig/net/sched/sch_generic.c 2007-05-24
timer round_jiffies in page-writeback.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/mm/page-writeback.c
===
--- linux-2.6.22-rc-mm.orig/mm/page-writeback.c 2007-05-25 10:49:11.0
-0700
Below are a bunch of random timers, that were active on my system,
that can better be round_jiffies() aligned.
I guess we need a audit of all timer usages atleast in kernel-core.
This patch:
Make usb autosuspend timers 1sec jiffy aligned.
Signed-off-by: Venkatesh Pallipadi <[EMAIL
Below are a bunch of random timers, that were active on my system,
that can better be round_jiffies() aligned.
I guess we need a audit of all timer usages atleast in kernel-core.
This patch:
Make usb autosuspend timers 1sec jiffy aligned.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
timer round_jiffies in page-writeback.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/mm/page-writeback.c
===
--- linux-2.6.22-rc-mm.orig/mm/page-writeback.c 2007-05-25 10:49:11.0
-0700
+++
round_jiffies for net dev watchdog timer.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/net/sched/sch_generic.c
===
--- linux-2.6.22-rc-mm.orig/net/sched/sch_generic.c 2007-05-24
round_jiffies() for i386 and x86-64 non-critical/corrected MCE polling.
Signed-off-by: Venkatesh Pallipadi [EMAIL PROTECTED]
Index: linux-2.6.22-rc-mm/arch/x86_64/kernel/mce.c
===
---
On Tue, May 29, 2007 at 11:22:30AM -0700, Randy Dunlap wrote:
On Tue, 29 May 2007 10:58:21 -0700 Venki Pallipadi wrote:
Below are a bunch of random timers, that were active on my system,
that can better be round_jiffies() aligned.
and these 4 patches help with (a) power usage
On Thu, May 24, 2007 at 05:04:13PM -0700, H. Peter Anvin wrote:
If they grow slowly from the bottom, I guess we could simply allocate
space in the vector byte by byte instead. Either way, it means more
work whenever anything has to change.
hpa,
Below patch adds a new word for feature
On Thu, May 24, 2007 at 03:02:23PM -0700, Andrew Morton wrote:
> On Wed, 23 May 2007 15:46:37 -0700
> Venki Pallipadi <[EMAIL PROTECTED]> wrote:
>
> > Display Intel Dynamic Acceleration feature in /proc/cpuinfo. This feature
> > will be enabled automatically by
On Thu, May 24, 2007 at 11:25:27PM +0200, Andi Kleen wrote:
> On Thursday 24 May 2007 23:13:37 Venki Pallipadi wrote:
> > On Thu, May 24, 2007 at 11:08:38PM +0200, Andi Kleen wrote:
> > >
> > > I think it's generally a good idea to push cpuinfo flags in earliest
> &
On Thu, May 24, 2007 at 11:08:38PM +0200, Andi Kleen wrote:
>
> I think it's generally a good idea to push cpuinfo flags in earliest
> as possible; just make sure we actually use the final name (so that we don't
> get
> into a pni->sse3 mess again)
>
ida is official name as in the Software
On Thu, May 24, 2007 at 05:01:04PM -0400, Dave Jones wrote:
> On Thu, May 24, 2007 at 01:55:13PM -0700, Andrew Morton wrote:
> > On Wed, 23 May 2007 15:46:37 -0700
> > Venki Pallipadi <[EMAIL PROTECTED]> wrote:
> >
> > > Display Intel Dynamic A
1 - 100 of 152 matches
Mail list logo
