Re: [PATCH v2] cpuidle-pseries: Fix CEDE latency conversion from tb to us

s a warning in case we discover an extended-cede state with > wakeup latency to be 0. In such a case, ensure that CEDE(0) has a > non-zero wakeup latency. > > Fixes: commit d947fb4c965c ("cpuidle: pseries: Fixup exit latency for > CEDE(0)") > > Signed-off-by: Gautham

Re: [PATCH] Revert "powerpc/powernv/idle: Replace CPU feature check with PVR check"

dle states are enabled and tested on the P10 platform > with this fix. > > This reverts commit 8747bf36f312356f8a295a0c39ff092d65ce75ae. > > Fixes: 8747bf36f312 ("powerpc/powernv/idle: Replace CPU feature check with > PVR check") > Signed-off-by: Pratik Rajes

Re: [PATCH 5/5] cpuidle-pseries: Block Extended CEDE(1) which adds no additional value.

and Extended CEDE(1) map to > the same hardware idle state. Since we already get SMT folding from > the normal CEDE, the Extended CEDE(1) doesn't provide any additional > value. This patch blocks Extended CEDE(1). > > Signed-off-by: Gautham R. Shenoy Reviewed-by: Vaidyanathan Srini

Re: [PATCH 4/5] cpuidle-pseries : Include extended CEDE states in cpuidle framework

.0th: 13648 > 99.5th: 14768 > 99.9th: 15664 > min=0, max=29812 > > With Patch: > Latency percentiles (usec) > 50.0th: 30 > 75.0th: 40 > 90.0th: 51 > 95.0th: 59 > *99.0th: 13616 > 99.5th: 14512 > 99.9th: 15696 &

Re: [PATCH 3/5] cpuidle-pseries : Fixup exit latency for CEDE(0)

: 13104 > 99.5th: 14672 > 99.9th: 15824 > min=0, max=17993 > > With-patch: > Latency percentiles (usec) > 50.0th: 29 > 75.0th: 40 > 90.0th: 50 > 95.0th: 61 > *99.0th: 13648 > 99.5th: 14768 > 99.9th: 1

Re: [PATCH 2/5] cpuidle-pseries: Add function to parse extended CEDE records

= 10 > [5.913183] xcede : Record 0 : hint = 1, latency =0x400 tb-ticks, > Wake-on-irq = 1 > [5.913188] xcede : Record 1 : hint = 2, latency =0x3e8000 tb-ticks, > Wake-on-irq = 0 > [5.913193] cpuidle : Skipping the 2 Extended CEDE idle states > > Signed-off-by: Gaut

Re: [PATCH 1/5] cpuidle-pseries: Set the latency-hint before entering CEDE

cede states through the > cpuidle framework, where each of them will have a different > cede-latency hint. > > Signed-off-by: Gautham R. Shenoy Reviewed-by: Vaidyanathan Srinivasan > --- > drivers/cpuidle/cpuidle-pseries.c | 10 +- > 1 file changed, 9 insertion

Re: [PATCH 0/5] cpuidle-pseries: Parse extended CEDE information for idle.

* Gautham R Shenoy [2020-07-07 16:41:34]: > From: "Gautham R. Shenoy" > > Hi, > > On pseries Dedicated Linux LPARs, apart from the polling snooze idle > state, we currently have the CEDE idle state which cedes the CPU to > the hypervisor with latency-hint = 0. > > However, the PowerVM

Re: [Skiboot] [PATCH v8 3/3] Self save API integration

ing and usage. > > Signed-off-by: Pratik Rajesh Sampat Reviewed-by: Vaidyanathan Srinivasan > --- > doc/opal-api/opal-slw-self-save-reg-181.rst | 51 ++ > doc/opal-api/opal-slw-set-reg-100.rst | 5 + > doc/power-management.rs

Re: [PATCH v8 2/3] API to verify the STOP API and image compatibility

. BRAHMASAMUDRA > Reviewed-by: Gregory S Still > Reviewed-by: Jennifer A Stofer > Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/77614 > Tested-by: Jenkins OP Build CI > Tested-by: Jenkins OP HW > Reviewed-by: Daniel M Crowell > Signed-off-by: Pratik Rajesh Samp

Re: [Skiboot] [PATCH v8 1/3] Self Save: Introducing Support for SPR Self Save

hristian R. Geddes > Signed-off-by: Prem Shanker Jha > Signed-off-by: Akshay Adiga > Signed-off-by: Pratik Rajesh Sampat Reviewed-by: Vaidyanathan Srinivasan > 2. The commit also incorporates changes that make STOP API project > agnostic changes include defining wrapper functions

Re: [PATCH] pseries/energy: Use OF accessor functions to read ibm,drc-indexes

t; Fixes: commit e83636ac3334 ("pseries/drc-info: Search DRC properties for CPU > indexes") > Cc: #v4.16+ > Reported-by: Pavithra R. Prakash > Signed-off-by: Gautham R. Shenoy Reviewed-by: Vaidyanathan Srinivasan > --- > arch/powerpc/platforms/pseries/pseries_energy.

Re: [PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

* Gautham R Shenoy [2018-07-03 10:54:16]: > From: "Gautham R. Shenoy" > > In the situations where snooze is the only cpuidle state due to > firmware not exposing any platform idle states, the idle CPUs will > remain in snooze for a long time with interrupts disabled causing the > Hard-lockup

Re: [PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

* Gautham R Shenoy [2018-07-03 10:54:16]: > From: "Gautham R. Shenoy" > > In the situations where snooze is the only cpuidle state due to > firmware not exposing any platform idle states, the idle CPUs will > remain in snooze for a long time with interrupts disabled causing the > Hard-lockup

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

was using fast_swtich then > @@ -718,10 +728,8 @@ void gpstate_timer_handler(struct timer_list *t) > if (gpstate_idx != gpstates->last_lpstate_idx) > queue_gpstate_timer(gpstates); > > + set_pstate(_data); > spin_unlock(>gpstate_lock); > - > - /* Timer may get migrated to a different cpu on cpu hot unplug */ > - smp_call_function_any(policy->cpus, set_pstate, _data, 1); > } Fix looks good. Acked-by: Vaidyanathan Srinivasan <sva...@linux.vnet.ibm.com>

Re: [PATCH V3] cpufreq: powernv: Fix the hardlockup by synchronus smp_call in timer interrupt

queue_gpstate_timer(gpstates); > > + set_pstate(_data); > spin_unlock(>gpstate_lock); > - > - /* Timer may get migrated to a different cpu on cpu hot unplug */ > - smp_call_function_any(policy->cpus, set_pstate, _data, 1); > } Fix looks good. Acked-by: Vaidyanathan Srinivasan

Re: [RESEND][PATCH] cpuidle/powernv : Restore different PSSCR for idle and hotplug

* Benjamin Herrenschmidt [2018-03-01 08:40:22]: > On Thu, 2018-03-01 at 01:03 +0530, Akshay Adiga wrote: > > commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle > > states via stop API.") uses stop-api provided by the firmware to restore > > PSSCR. PSSCR

Re: [RESEND][PATCH] cpuidle/powernv : Restore different PSSCR for idle and hotplug

* Benjamin Herrenschmidt [2018-03-01 08:40:22]: > On Thu, 2018-03-01 at 01:03 +0530, Akshay Adiga wrote: > > commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle > > states via stop API.") uses stop-api provided by the firmware to restore > > PSSCR. PSSCR restore is required

Re: [PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

* Rafael J. Wysocki <raf...@kernel.org> [2017-03-23 16:28:31]: > On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan > <sva...@linux.vnet.ibm.com> wrote: > > drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). > > On PowerNV platfo

Re: [PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

* Rafael J. Wysocki [2017-03-23 16:28:31]: > On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan > wrote: > > drv->cpumask defaults to cpu_possible_mask in __cpuidle_driver_init(). > > On PowerNV platform cpu_present could be less than cpu_possible in cases >

Re: [PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs

* Rafael J. Wysocki <raf...@kernel.org> [2017-03-23 16:27:31]: > On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan > <sva...@linux.vnet.ibm.com> wrote: > > If a given cpu is not in cpu_present and cpu hotplug > > is disabled, arch can skip setting up the

Re: [PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs

* Rafael J. Wysocki [2017-03-23 16:27:31]: > On Thu, Mar 23, 2017 at 4:22 PM, Vaidyanathan Srinivasan > wrote: > > If a given cpu is not in cpu_present and cpu hotplug > > is disabled, arch can skip setting up the cpu_dev. > > > > Arch cpuidle drive

[PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs

] Registration of powernv driver failed. Signed-off-by: Vaidyanathan Srinivasan <sva...@linux.vnet.ibm.com> --- drivers/cpuidle/sysfs.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/cpuidle/sysfs.c b/drivers/cpuidle/sysfs.c index c5adc8c..f2c3bce 100644 --- a/drivers/c

[PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

e30] c000b564 ret_from_kernel_thread+0x5c/0x78 This patch fixes the bug by passing correct cpumask from powernv-cpuidle driver. Signed-off-by: Vaidyanathan Srinivasan <sva...@linux.vnet.ibm.com> --- drivers/cpuidle/cpuidle-powernv.c | 18 ++ 1 file changed, 18 insertions(+) d

[PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs

] Registration of powernv driver failed. Signed-off-by: Vaidyanathan Srinivasan --- drivers/cpuidle/sysfs.c | 12 1 file changed, 12 insertions(+) diff --git a/drivers/cpuidle/sysfs.c b/drivers/cpuidle/sysfs.c index c5adc8c..f2c3bce 100644 --- a/drivers/cpuidle/sysfs.c +++ b/drivers/cpuidle

[PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration

e30] c000b564 ret_from_kernel_thread+0x5c/0x78 This patch fixes the bug by passing correct cpumask from powernv-cpuidle driver. Signed-off-by: Vaidyanathan Srinivasan --- drivers/cpuidle/cpuidle-powernv.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/drivers/cpuidle/cpui

[PATCH v1 0/2] cpuidle: Fixes in cpuidle driver

ess incorrect address and crash. The following patch series fixes the cpuidle-powernv driver and also adds additional checks in cpuidle_add_sysfs() This patch set is against v4.11-rc3. Changed from v1: Updated commit message and comments. Signed-off-by: Vaidyanathan Srinivasan <sva...@linux.vnet.ibm.com>

[PATCH v1 0/2] cpuidle: Fixes in cpuidle driver

ess incorrect address and crash. The following patch series fixes the cpuidle-powernv driver and also adds additional checks in cpuidle_add_sysfs() This patch set is against v4.11-rc3. Changed from v1: Updated commit message and comments. Signed-off-by: Vaidyanathan Srinivasan

Re: [PATCH 4.4 54/58] powerpc: Convert cmp to cmpd in idle enter sequence

instance the code comes directly from ISA v2.07, including the > cmp, but cmpd is correct. Backport to stable so that new toolchains can > build old kernels. > > Fixes: 948cf67c4726 ("powerpc: Add NAP mode support on Power7 in HV mode") > Reviewed-by: Vaidyanathan Srinivasan

Re: [PATCH 4.4 54/58] powerpc: Convert cmp to cmpd in idle enter sequence

but cmpd is correct. Backport to stable so that new toolchains can > build old kernels. > > Fixes: 948cf67c4726 ("powerpc: Add NAP mode support on Power7 in HV mode") > Reviewed-by: Vaidyanathan Srinivasan > Signed-off-by: Segher Boessenkool > Signed-off-by: Michae

Re: [patch 10/15] sched/migration: Move calc_load_migrate() into CPU_DYING

As a result a cpu unplug leakes a load of 1 into the global load > accounting mechanism. > > Fix it by adjusting for the currently running thread which calls > calc_load_migrate(). > > Fixes: e9cd8fa4fcfd: "sched/migration: Move calc_load_migrate() into > CPU_DYING" > Reported

Re: [patch 10/15] sched/migration: Move calc_load_migrate() into CPU_DYING

t; accounting mechanism. > > Fix it by adjusting for the currently running thread which calls > calc_load_migrate(). > > Fixes: e9cd8fa4fcfd: "sched/migration: Move calc_load_migrate() into > CPU_DYING" > Reported-by: Anton Blanchard Tested-by: Vaidyanathan Srinivas

Re: [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency

* Benjamin Herrenschmidt [2015-05-30 20:38:22]: > On Sat, 2015-05-30 at 11:31 +0530, Vaidyanathan Srinivasan wrote: > > In shared lpar case, spinning in guest context may potentially take > > away cycles from other lpars waiting to run on the same physical cpu. > > > &

Re: [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency

* Benjamin Herrenschmidt b...@au1.ibm.com [2015-05-30 20:38:22]: On Sat, 2015-05-30 at 11:31 +0530, Vaidyanathan Srinivasan wrote: In shared lpar case, spinning in guest context may potentially take away cycles from other lpars waiting to run on the same physical cpu. So the policy

Re: [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency

* Preeti U Murthy [2015-05-29 19:17:17]: [snip] > > + if (max_idle_state > 1) { > > + snooze_timeout_en = true; > > + snooze_timeout = cpuidle_state_table[1].target_residency * > > +tb_ticks_per_usec; > > + } > > Any idea why we don't have

Re: [PATCH] cpuidle: powernv/pseries: Decrease the snooze residency

* Preeti U Murthy pre...@linux.vnet.ibm.com [2015-05-29 19:17:17]: [snip] + if (max_idle_state 1) { + snooze_timeout_en = true; + snooze_timeout = cpuidle_state_table[1].target_residency * +tb_ticks_per_usec; + } Any idea why we

[tip:sched/core] sched: Fix asymmetric scheduling for POWER7

Commit-ID: 2042abe7977222ef606306faa2dce8fd51e98e65 Gitweb: http://git.kernel.org/tip/2042abe7977222ef606306faa2dce8fd51e98e65 Author: Vaidyanathan Srinivasan AuthorDate: Wed, 30 Oct 2013 08:42:42 +0530 Committer: Ingo Molnar CommitDate: Wed, 6 Nov 2013 12:37:54 +0100 sched: Fix

[tip:sched/core] sched: Fix asymmetric scheduling for POWER7

Commit-ID: 2042abe7977222ef606306faa2dce8fd51e98e65 Gitweb: http://git.kernel.org/tip/2042abe7977222ef606306faa2dce8fd51e98e65 Author: Vaidyanathan Srinivasan sva...@linux.vnet.ibm.com AuthorDate: Wed, 30 Oct 2013 08:42:42 +0530 Committer: Ingo Molnar mi...@kernel.org CommitDate: Wed, 6

[PATCH 3/3] sched: Aggressive balance in domains whose groups share package resources

ame group. Signed-off-by: Preeti U Murthy Signed-off-by: Vaidyanathan Srinivasan --- kernel/sched/fair.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 828ed97..bbcd96b 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fai

[PATCH 2/3] sched: Fix asymmetric scheduling for POWER7

its if this domain has no idle cpu. Hence, nr_busy check against group weight can be removed. Reported-by: Michael Neuling Signed-off-by: Vaidyanathan Srinivasan Signed-off-by: Preeti U Murthy --- kernel/sched/fair.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sc

[PATCH 1/3] sched: Fix nohz_kick_needed to consider the nr_busy of the parent domain's group

CE comes before the check for ASYM_PACKING. Priority is given to avoid more than one busy thread in a core as much as possible before attempting asymmetric packing. Signed-off-by: Preeti U Murthy Signed-off-by: Vaidyanathan Srinivasan --- kernel/sched/fair.c | 19 +-- 1 f

[PATCH 0/3] sched: Fixes for task placement in SMT threads

. This series applies on v3.12-rc6 and tested on x86 and powerpc. --Vaidy --- Preeti U Murthy (2): sched: Fix nohz_kick_needed to consider the nr_busy of the parent domain's group sched: Aggressive balance in domains whose groups share package resources Vaidyanathan Srinivasan (1

[PATCH 0/3] sched: Fixes for task placement in SMT threads

. This series applies on v3.12-rc6 and tested on x86 and powerpc. --Vaidy --- Preeti U Murthy (2): sched: Fix nohz_kick_needed to consider the nr_busy of the parent domain's group sched: Aggressive balance in domains whose groups share package resources Vaidyanathan Srinivasan (1

[PATCH 1/3] sched: Fix nohz_kick_needed to consider the nr_busy of the parent domain's group

for SD_SHARE_PKG_RESOURCE comes before the check for ASYM_PACKING. Priority is given to avoid more than one busy thread in a core as much as possible before attempting asymmetric packing. Signed-off-by: Preeti U Murthy pre...@linux.vnet.ibm.com Signed-off-by: Vaidyanathan Srinivasan sva...@linux.vnet.ibm.com

[PATCH 2/3] sched: Fix asymmetric scheduling for POWER7

if this domain has no idle cpu. Hence, nr_busy check against group weight can be removed. Reported-by: Michael Neuling michael.neul...@au1.ibm.com Signed-off-by: Vaidyanathan Srinivasan sva...@linux.vnet.ibm.com Signed-off-by: Preeti U Murthy pre...@linux.vnet.ibm.com --- kernel/sched/fair.c |4

[PATCH 3/3] sched: Aggressive balance in domains whose groups share package resources

for other cpus in the same group. Signed-off-by: Preeti U Murthy pre...@linux.vnet.ibm.com Signed-off-by: Vaidyanathan Srinivasan sva...@linux.vnet.ibm.com --- kernel/sched/fair.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index

Re: [RFC PATCH 4/5] cpuidle/ppc: CPU goes tickless if there are no arch-specific constraints

* Preeti U Murthy [2013-07-27 13:20:37]: > Hi Ben, > > On 07/27/2013 12:00 PM, Benjamin Herrenschmidt wrote: > > On Fri, 2013-07-26 at 08:09 +0530, Preeti U Murthy wrote: > >> *The lapic of a broadcast CPU is active always*. Say CPUX, wants the > >> broadcast CPU to wake it up at timeX. Since

Re: [RFC PATCH 4/5] cpuidle/ppc: CPU goes tickless if there are no arch-specific constraints

* Benjamin Herrenschmidt [2013-07-27 16:30:05]: > On Fri, 2013-07-26 at 08:09 +0530, Preeti U Murthy wrote: > > *The lapic of a broadcast CPU is active always*. Say CPUX, wants the > > broadcast CPU to wake it up at timeX. Since we cannot program the lapic > > of a remote CPU, CPUX will need to

Re: [RFC PATCH 4/5] cpuidle/ppc: CPU goes tickless if there are no arch-specific constraints

* Benjamin Herrenschmidt b...@kernel.crashing.org [2013-07-27 16:30:05]: On Fri, 2013-07-26 at 08:09 +0530, Preeti U Murthy wrote: *The lapic of a broadcast CPU is active always*. Say CPUX, wants the broadcast CPU to wake it up at timeX. Since we cannot program the lapic of a remote CPU,

Re: [RFC PATCH 4/5] cpuidle/ppc: CPU goes tickless if there are no arch-specific constraints

* Preeti U Murthy pre...@linux.vnet.ibm.com [2013-07-27 13:20:37]: Hi Ben, On 07/27/2013 12:00 PM, Benjamin Herrenschmidt wrote: On Fri, 2013-07-26 at 08:09 +0530, Preeti U Murthy wrote: *The lapic of a broadcast CPU is active always*. Say CPUX, wants the broadcast CPU to wake it up at

Re: [RFC PATCH 0/8][Sorted-buddy] mm: Linux VM Infrastructure to support Memory Power Management

* Mel Gorman [2012-11-08 18:02:57]: > On Wed, Nov 07, 2012 at 01:22:13AM +0530, Srivatsa S. Bhat wrote: > > Hi Mel, Thanks for detailed review and comments. The goal of this patch series is to brainstorm on ideas that enable Linux

Re: [RFC PATCH 0/8][Sorted-buddy] mm: Linux VM Infrastructure to support Memory Power Management

* Mel Gorman mgor...@suse.de [2012-11-08 18:02:57]: On Wed, Nov 07, 2012 at 01:22:13AM +0530, Srivatsa S. Bhat wrote: Hi Mel, Thanks for detailed review and comments. The goal of this patch series is to brainstorm on ideas that

Re: [PATCH 33/36] autonuma: powerpc port

* Benjamin Herrenschmidt [2012-08-23 08:56:34]: > On Thu, 2012-08-23 at 08:01 +1000, Benjamin Herrenschmidt wrote: > > On Wed, 2012-08-22 at 16:59 +0200, Andrea Arcangeli wrote: > > > From: Vaidyanathan Srinivasan > > > > > > * PMD flaging is not r

Re: [PATCH 33/36] autonuma: powerpc port

* Benjamin Herrenschmidt b...@kernel.crashing.org [2012-08-23 08:56:34]: On Thu, 2012-08-23 at 08:01 +1000, Benjamin Herrenschmidt wrote: On Wed, 2012-08-22 at 16:59 +0200, Andrea Arcangeli wrote: From: Vaidyanathan Srinivasan sva...@linux.vnet.ibm.com * PMD flaging

Re: Analysis of sched_mc_power_savings

* Ingo Molnar <[EMAIL PROTECTED]> [2008-01-09 12:35:07]: > > * Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote: > > > How do we take this technique to the next step where we can > > consolidate short running jobs as well? Did you face any difficulty >

Re: Analysis of sched_mc_power_savings

* Siddha, Suresh B <[EMAIL PROTECTED]> [2008-01-08 13:24:00]: > On Tue, Jan 08, 2008 at 11:08:15PM +0530, Vaidyanathan Srinivasan wrote: > > Hi, > > > > The following experiments were conducted on a two socket dual core > > intel processor based machine

Re: Analysis of sched_mc_power_savings

* Siddha, Suresh B [EMAIL PROTECTED] [2008-01-08 13:24:00]: On Tue, Jan 08, 2008 at 11:08:15PM +0530, Vaidyanathan Srinivasan wrote: Hi, The following experiments were conducted on a two socket dual core intel processor based machine in order to understand the impact

Re: Analysis of sched_mc_power_savings

* Ingo Molnar [EMAIL PROTECTED] [2008-01-09 12:35:07]: * Vaidyanathan Srinivasan [EMAIL PROTECTED] wrote: How do we take this technique to the next step where we can consolidate short running jobs as well? Did you face any difficulty biasing the CPU for short running jobs

Analysis of sched_mc_power_savings

CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y tick-sched.c has been instrumented to collect idle entry and exit time stamps. Instrumentation patch: Instrument tick-sched nohz code and generate time stamp trace data. Signed-off-by: Vaidyanathan

Analysis of sched_mc_power_savings

CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y tick-sched.c has been instrumented to collect idle entry and exit time stamps. Instrumentation patch: Instrument tick-sched nohz code and generate time stamp trace data. Signed-off-by: Vaidyanathan

Re: 1.0.0.0 DNS replies for many domain names (network)

* Amogh Hooshdar <[EMAIL PROTECTED]> [2007-12-14 17:20:17]: > I am having a strange problem with Debian Etch 4.0 (both 64-bit and > 32-bit) using 2.6.18 kernel. Most websites do not open with browser, > Pidgin and most other GUI applicatoins. but I am able to ping them > fine. I am also able to

Re: 1.0.0.0 DNS replies for many domain names (network)

* Amogh Hooshdar [EMAIL PROTECTED] [2007-12-14 17:20:17]: I am having a strange problem with Debian Etch 4.0 (both 64-bit and 32-bit) using 2.6.18 kernel. Most websites do not open with browser, Pidgin and most other GUI applicatoins. but I am able to ping them fine. I am also able to do

Re: 2.6.24-rc1 on PPC64: machine check exception

> >> http://patchwork.ozlabs.org/linuxppc/patch?id=14475 > > Thanks for pointing me to this patch. I will try out and let you know if > this fixed the problem. Hi Anton, This patch fixed the problem. I am able to run and profile ebizzy on 128-way PPC64. However this fix is not included in

Re: 2.6.24-rc1 on PPC64: machine check exception

http://patchwork.ozlabs.org/linuxppc/patch?id=14475 Thanks for pointing me to this patch. I will try out and let you know if this fixed the problem. Hi Anton, This patch fixed the problem. I am able to run and profile ebizzy on 128-way PPC64. However this fix is not included in

Re: 2.6.24-rc1 on PPC64: machine check exception

Anton Blanchard wrote: > Hi > >> I got the following exception on a 128-way PPC64 machine while running >> ebizzy-0.2 benchmark. > > Is it a 64bit application? Im guessing its fixed by this: Hi Anton, The ebizzy application I tried is 64-bit. >

2.6.24-rc1 on PPC64: machine check exception

Hi, I got the following exception on a 128-way PPC64 machine while running ebizzy-0.2 benchmark. cpu 0x48: Vector: 200 (Machine Check) at [c06df1bb37c0] pc: c007a26c: .exit_robust_list+0x78/0x228 lr: c007a240: .exit_robust_list+0x4c/0x228 sp: c06df1bb3a40

2.6.24-rc1 on PPC64: machine check exception

Hi, I got the following exception on a 128-way PPC64 machine while running ebizzy-0.2 benchmark. cpu 0x48: Vector: 200 (Machine Check) at [c06df1bb37c0] pc: c007a26c: .exit_robust_list+0x78/0x228 lr: c007a240: .exit_robust_list+0x4c/0x228 sp: c06df1bb3a40

Re: 2.6.24-rc1 on PPC64: machine check exception

Anton Blanchard wrote: Hi I got the following exception on a 128-way PPC64 machine while running ebizzy-0.2 benchmark. Is it a 64bit application? Im guessing its fixed by this: Hi Anton, The ebizzy application I tried is 64-bit. http://patchwork.ozlabs.org/linuxppc/patch?id=14475

Re: Question about free/used memory on Linux

Ravinandan Arakali (rarakali) wrote: > Hi Vaidy, > Thanks for clarifying several of my doubts. > > To answer your question about my intention, we currently have a > system with 2 GB RAM and I need to find out the actual used and > free memory so that we can decide if the same

Re: Question about free/used memory on Linux

Ravinandan Arakali (rarakali) wrote: > Hi kernel gurus, > I am trying to find out the memory that's used on my linux box. > I find that there are quite a few confusing metrics. How do > I find out the "true" used memory ? pagecache pages may be the reason for the confusion. Most free memory can

Re: Question about free/used memory on Linux

Ravinandan Arakali (rarakali) wrote: Hi kernel gurus, I am trying to find out the memory that's used on my linux box. I find that there are quite a few confusing metrics. How do I find out the true used memory ? pagecache pages may be the reason for the confusion. Most free memory can be

Re: Question about free/used memory on Linux

Ravinandan Arakali (rarakali) wrote: Hi Vaidy, Thanks for clarifying several of my doubts. To answer your question about my intention, we currently have a system with 2 GB RAM and I need to find out the actual used and free memory so that we can decide if the same setup(applications,

Re: [-mm PATCH 0/9] Memory controller introduction (v4)

KAMEZAWA Hiroyuki wrote: > On Wed, 8 Aug 2007 12:51:39 +0900 > KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote: > >> On Sat, 28 Jul 2007 01:39:37 +0530 >> Balbir Singh <[EMAIL PROTECTED]> wrote: >>> At OLS, the resource management BOF, it was discussed that we need to manage >>> RSS and unmapped

Re: [-mm PATCH 0/9] Memory controller introduction (v4)

KAMEZAWA Hiroyuki wrote: On Wed, 8 Aug 2007 12:51:39 +0900 KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote: On Sat, 28 Jul 2007 01:39:37 +0530 Balbir Singh [EMAIL PROTECTED] wrote: At OLS, the resource management BOF, it was discussed that we need to manage RSS and unmapped page cache together.

Re: [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v4)

Vaidyanathan Srinivasan wrote: > > YAMAMOTO Takashi wrote: >>> +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan, >>> + struct list_head *dst, >>> +

Re: [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v4)

Vaidyanathan Srinivasan wrote: YAMAMOTO Takashi wrote: +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan, + struct list_head *dst, + unsigned long *scanned, int order

Re: [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v4)

YAMAMOTO Takashi wrote: >> +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan, >> +struct list_head *dst, >> +unsigned long *scanned, int order, >> +int mode, struct zone

Re: [-mm PATCH 4/9] Memory controller memory accounting (v4)

YAMAMOTO Takashi wrote: >> +lock_meta_page(page); >> +/* >> + * Check if somebody else beat us to allocating the meta_page >> + */ >> +race_mp = page_get_meta_page(page); >> +if (race_mp) { >> +kfree(mp); >> +mp = race_mp; >> +

Re: [-mm PATCH 4/9] Memory controller memory accounting (v4)

YAMAMOTO Takashi wrote: +lock_meta_page(page); +/* + * Check if somebody else beat us to allocating the meta_page + */ +race_mp = page_get_meta_page(page); +if (race_mp) { +kfree(mp); +mp = race_mp; +atomic_inc(mp-ref_cnt); +

Re: [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v4)

YAMAMOTO Takashi wrote: +unsigned long mem_container_isolate_pages(unsigned long nr_to_scan, +struct list_head *dst, +unsigned long *scanned, int order, +int mode, struct zone *z, +

Re: [-mm PATCH 4/7] Memory controller memory accounting

Balbir Singh wrote: > Add the accounting hooks. The accounting is carried out for RSS and Page > Cache (unmapped) pages. There is now a common limit and accounting for both. > The RSS accounting is accounted at page_add_*_rmap() and page_remove_rmap() > time. Page cache is accounted at

Re: [-mm PATCH 4/7] Memory controller memory accounting

Balbir Singh wrote: Add the accounting hooks. The accounting is carried out for RSS and Page Cache (unmapped) pages. There is now a common limit and accounting for both. The RSS accounting is accounted at page_add_*_rmap() and page_remove_rmap() time. Page cache is accounted at

Re: IRQ handling difference between i386 and x86_64

Arjan van de Ven wrote: > On Sat, 2007-06-30 at 16:55 +0200, Krzysztof Oledzki wrote: >> Hello, >> >> It seems that IRQ handling is somehow different between i386 and x86_64. >> >> In my Dell PowerEdge 1950 is it possible to enable interrupts spreading >> over all CPUs. This a single CPU, four

Re: IRQ handling difference between i386 and x86_64

Arjan van de Ven wrote: On Sat, 2007-06-30 at 16:55 +0200, Krzysztof Oledzki wrote: Hello, It seems that IRQ handling is somehow different between i386 and x86_64. In my Dell PowerEdge 1950 is it possible to enable interrupts spreading over all CPUs. This a single CPU, four CORE system

[RFC][PATCH 3/3] Pagecache reclaim

Pagecache controller reclaim changes Reclaim path needs performance improvement. For now it is minor changes to include unmapped pages in our list of page_container. Signed-off-by: Vaidyanathan Srinivasan <[EMAIL PROTECTED]> --- mm/rss_container.c

[RFC][PATCH 2/3] Pagecache and RSS accounting hooks

. Signed-off-by: Vaidyanathan Srinivasan <[EMAIL PROTECTED]> --- fs/exec.c |4 ++-- mm/filemap.c| 17 + mm/memory.c | 18 +- mm/migrate.c|4 ++-- mm/rmap.c | 12 ++-- mm/swap_state.c | 16 mm/swap

[RFC][PATCH 1/3] Pagecache accounting

page_container list only once independent of repeated calls from pagecache, swapcache and mmap to RSS. No setup patch is required since rss_limit and rss_usage has been generalised as the resource counter for pagecache as well. Signed-off-by: Vaidyanathan Srinivasan <[EMAIL PROTECTED]> --- include

[RFC][PATCH 0/3] Containers: Integrated RSS and pagecache control v5

Containers: Integrated RSS and pagecache accounting and control v5 -- Based on the discussions at OLS yesterday, the consensus was to try an integrated pagecache controller along with RSS controller under the same usage limit. This

[RFC][PATCH 0/3] Containers: Integrated RSS and pagecache control v5

Containers: Integrated RSS and pagecache accounting and control v5 -- Based on the discussions at OLS yesterday, the consensus was to try an integrated pagecache controller along with RSS controller under the same usage limit. This

[RFC][PATCH 1/3] Pagecache accounting

page_container list only once independent of repeated calls from pagecache, swapcache and mmap to RSS. No setup patch is required since rss_limit and rss_usage has been generalised as the resource counter for pagecache as well. Signed-off-by: Vaidyanathan Srinivasan [EMAIL PROTECTED] --- include/linux

[RFC][PATCH 2/3] Pagecache and RSS accounting hooks

. Signed-off-by: Vaidyanathan Srinivasan [EMAIL PROTECTED] --- fs/exec.c |4 ++-- mm/filemap.c| 17 + mm/memory.c | 18 +- mm/migrate.c|4 ++-- mm/rmap.c | 12 ++-- mm/swap_state.c | 16 mm/swapfile.c

[RFC][PATCH 3/3] Pagecache reclaim

Pagecache controller reclaim changes Reclaim path needs performance improvement. For now it is minor changes to include unmapped pages in our list of page_container. Signed-off-by: Vaidyanathan Srinivasan [EMAIL PROTECTED] --- mm/rss_container.c |3

Re: [RFC] mm-controller

Paul Menage wrote: > On 6/25/07, Paul Menage <[EMAIL PROTECTED]> wrote: >> On 6/22/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote: >>> Merging both limits will eliminate the issue, however we would need >>> individual limits for pagecache and RSS

Re: [RFC] mm-controller

Peter Zijlstra wrote: > On Fri, 2007-06-22 at 22:05 +0530, Vaidyanathan Srinivasan wrote: > >> Merging both limits will eliminate the issue, however we would need >> individual limits for pagecache and RSS for better control. There are >> use cases for pagecache_limit

Re: [RFC] mm-controller

Peter Zijlstra wrote: On Fri, 2007-06-22 at 22:05 +0530, Vaidyanathan Srinivasan wrote: Merging both limits will eliminate the issue, however we would need individual limits for pagecache and RSS for better control. There are use cases for pagecache_limit alone without RSS_limit like

Re: [RFC] mm-controller

Paul Menage wrote: On 6/25/07, Paul Menage [EMAIL PROTECTED] wrote: On 6/22/07, Vaidyanathan Srinivasan [EMAIL PROTECTED] wrote: Merging both limits will eliminate the issue, however we would need individual limits for pagecache and RSS for better control. There are use cases

Re: [RFC] mm-controller

Peter Zijlstra wrote: > On Thu, 2007-06-21 at 16:33 +0530, Balbir Singh wrote: >> Peter Zijlstra wrote: [snip] > Not quite sure on 2, from reading the pagecache controller, I got the > impression that enforcing both limits got you into trouble. Merging the > limits would rid us of that issue,

Re: [RFC] mm-controller

Peter Zijlstra wrote: On Thu, 2007-06-21 at 16:33 +0530, Balbir Singh wrote: Peter Zijlstra wrote: [snip] Not quite sure on 2, from reading the pagecache controller, I got the impression that enforcing both limits got you into trouble. Merging the limits would rid us of that issue, no?

[RFC][PATCH 3/4] Pagecache and RSS accounting hooks

. Signed-off-by: Vaidyanathan Srinivasan <[EMAIL PROTECTED]> --- fs/exec.c |4 ++-- mm/filemap.c| 18 ++ mm/memory.c | 18 +- mm/migrate.c|4 ++-- mm/rmap.c | 12 ++-- mm/swap_state.c | 16 mm/swap

[RFC][PATCH 4/4] Pagecache reclaim

Pagecache controller reclaim changes Reclaim path needs performance improvement. For now it is minor changes to include unmapped pages in our list of page_container. Signed-off-by: Vaidyanathan Srinivasan <[EMAIL PROTECTED]> --- mm/rss_container.c

  1   2   >