Re: [PATCH 3/3] powercap, intel_rapl, Add ignore_max_time_window_check module parameter for broken BIOSes

J. Wysocki" > Cc: Prarit Bhargava > Cc: Radivoje Jovanovic > Cc: Seiichi Ikarashi > Cc: Mathias Krause > Cc: Ajay Thomas > Signed-off-by: Prarit Bhargava > --- > drivers/powercap/intel_rapl.c | 18 +++--- > 1 file changed, 15 insertions(+), 3 del

Re: [PATCH 1/3] powercap, intel_rapl, implement get_max_time_window

us; > egrep ^ > /sys/devices/virtual/powercap/intel-rapl/intel-rapl\:0/constraint_0_time_window_us > > -bash: echo: write error: Invalid argument > /sys/devices/virtual/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us:1:976 > > Cc: "Rafael J. Wysocki"

Re: [PATCH 3/3] powercap, intel_rapl, Add ignore_max_window_check module parameter for broken BIOSes

with a small window (albeit through some > trial and error). This patch adds a ignore_max_window_check module > parameter to avoid the maximum time window check in set_time_window(). > > Cc: "Rafael J. Wysocki" > Cc: Prarit Bhargava > Cc: Radivoje Jovanovic >

Re: [PATCH 1/3] powercap, intel_rapl, implement get_max_time_window

On 2015-12-15 22:02, Prarit Bhargava wrote: > The MSR_PKG_POWER_INFO register (Intel ASDM, section 14.9.3 > "Package RAPL Domain") provides a maximum time window which the > system can support. This window is read-only and is currently > not examined when setting the time windows for the package.

Re: [PATCH] powercap, intel_rapl.c, fix BIOS lock check

c: "Rafael J. Wysocki" > Cc: Jacob Pan > Cc: Radivoje Jovanovic > Cc: Seiichi Ikarashi > Cc: Mathias Krause > Cc: Ajay Thomas > Signed-off-by: Prarit Bhargava > --- > drivers/powercap/intel_rapl.c |6 -- > 1 file changed, 4 insertions(+), 2 del

[PATCH] clocksource: Add CPU info to clocksource watchdog reporting

The clocksource watchdog reporting was improved by 0b046b217ad4c6. I want to add the info of CPU where the watchdog detects a deviation because it is necessary to identify the trouble spot if the clocksource is TSC. Signed-off-by: Seiichi Ikarashi --- kernel/time/clocksource.c |4 ++-- 1

Re: [PATCH] [v2] intel_pstate: Fix user input of min/max to legal policy region

0 > > Fix this problem by 2 steps: > 1.Normalize the user input to [min_policy, max_policy]. > 2.Make sure max_perf_pct>=min_perf_pct, suggested by Seiichi Ikarashi. > > Signed-off-by: Chen Yu > --- > v2: > - Add logic to ensure max_perf_pct>=min_perf_pct. > --- >

Re: [PATCH] irq: Remove unnecessary warning with affinity_hint

On 2015-04-08 16:39, Ingo Molnar wrote: > > * Seiichi Ikarashi wrote: > >> Hi, >> >> On 2015-04-08 15:28, Ingo Molnar wrote: >>> >>> * Seiichi Ikarashi wrote: >>> >>>> Hi, >>>> >>>> If you turn off a P

Re: [PATCH] irq: Remove unnecessary warning with affinity_hint

Hi, On 2015-04-08 15:28, Ingo Molnar wrote: > > * Seiichi Ikarashi wrote: > >> Hi, >> >> If you turn off a PCI device whose driver has set affinity_hint, >> you will get warning message which does _not_ explain the reason >> why it appeared from the

[PATCH] irq: Remove unnecessary warning with affinity_hint

ally for a debug purpose for driver developers and has incidentally been left. Just remove the warning is good and enough. Signed-off-by: Seiichi Ikarashi --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -1335,7 +1335,7 @@ static struct irqaction *__free_irq(unsi #ifdef CO

[PATCH] irq: Remove unnecessary warning with affinity_hint

ning was originally for a debug purpose for driver developers and has incidentally been left. Just remove the warning is good and enough. Signed-off-by: Seiichi Ikarashi --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -1335,7 +1335,7 @@ static struct irqaction *__free_irq(unsi #ifdef CO

[PATCH] irq: Remove unnecessary warning with affinity_hint

iginally for a debug purpose for driver developers and has incidentally been left. Just remove the warning is good and enough. Signed-off-by: Seiichi Ikarashi --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -1335,7 +1335,7 @@ static struct irqaction *__free_irq(unsi #ifdef CO

[PATCH] ntp: fix return value of adjtimex() calling for STA_INS/DEL

Hi, Since commit 6b43ae8a619d17c4935c3320d2ef9e92bdeed05d, adjtimex() system call returns TIME_OK even if STA_INS/DEL calling. But the man page says it should be TIME_INS/TIME_DEL, respectively. I have no idea except for such an ad-hoc fix. Signed-off-by: Seiichi Ikarashi --- a/kernel/time

Re: [PATCH] ipc/sem.c: prevent ENOMEM in semop() w/ SEM_UNDO flag

Hi Manfred, (2012-08-07 20:10), Manfred Spraul wrote: > Hi Seiichi, > > 2012/8/6 Seiichi Ikarashi >> >> >> A real case was as follows. >> semget(IPC_PRIVATE, 7, IPC_CREAT | IPC_EXCL); >> sops[0].sem_num = 0; >> sops[0].se

Re: [PATCH] ipc/sem.c: prevent ENOMEM in semop() w/ SEM_UNDO flag

Hi Manfred, (2012-08-04 02:39), Manfred Spraul wrote: > Hi Seiichi, > > On 08/03/2012 02:49 PM, Seiichi Ikarashi wrote: >> semop() with SEM_UNDO sem_flg can result in ENOMEM even after >> succeeding semget() with large nsems. > How large is nsems, what is the use case? &g

[PATCH] ipc/sem.c: prevent ENOMEM in semop() w/ SEM_UNDO flag

: Seiichi Ikarashi --- a/ipc/sem.c 2012-08-03 16:52:01.0 +0900 +++ b/ipc/sem.c 2012-08-03 20:40:57.0 +0900 @@ -1258,11 +1258,12 @@ static struct sem_undo *find_alloc_undo( sem_getref_and_unlock(sma); /* step 2: allocate new undo structure */ - new = kzalloc