On 09/09/2016 03:30 PM, Thomas Gleixner wrote:
> On Thu, 8 Sep 2016, Binoy Jayan wrote:
>> On 8 September 2016 at 12:40, Thomas Gleixner wrote:
> [..]
+ latency = ktime_to_ns(ktime_sub(basenow,
+ ktime_to_ns(timer->praecox) ?
+
- not to your version. I am appending it just
for your information. I would be more than happy to convert the patch so it
applies on top of yours. However, I would not do it, if there were no chance
that it ever gets considered. Please let me know.
Thanks,
-Carsten.
--
From: Carsten Emde
Hi Sebastian,
I'm pleased to announce the v4.0.4-rt1 patch set.
First smoke test on an Intel Gulftown 980X: Compiled and booted without
problem, no regression of real-time capabilities so far.
[..]
Known issues:
- My AMD box throws a lot of "cpufreq_stat_notifier_trans: No
po
Hi Daniel,
BTW, are you also taking care of the latency-hist.patch patch?
I do.
However, the request (and the challenge) is not to simply rewrite the
code. The idea is to provide a general histogram framework that can be
used from anywhere in the kernel and to equip it with everything needed
y: */
- new_base = switch_hrtimer_base(timer, base, mode & HRTIMER_MODE_PINNED);
-
timer_stats_hrtimer_set_start_info(timer);
leftmost = enqueue_hrtimer(timer, new_base);
--- END ---
or something else?
Tested-by: Carsten Emde
Thanks,
-Carsten.
--
To unsubscribe
Hi Steven,
[..] I added Carsten to the Cc, so I'll post the entire change log
of v1 here again.
I've been listening and testing boxes all the time ...
[..] If you have any benchmark on large machines I would be very
happy if you could test this patch against the unpatched version of
-rt.
Thr
On 01/27/2014 07:24 PM, Steven Rostedt wrote:
On Mon, 27 Jan 2014 13:42:29 +0400
Pavel Vasilyev wrote:
27.01.2014 12:44, Sebastian Andrzej Siewior пишет:
On 01/26/2014 10:25 PM, Pavel Vasilyev wrote:
25.01.2014 17:45, Sebastian Andrzej Siewior пишет:
Dear RT folks!
Gentlemen, let's have
On 01/25/2014 02:45 PM, Sebastian Andrzej Siewior wrote:
Dear RT folks!
I'm pleased to announce the v3.12.8-rt11 patch set.
[..]
Thanks a lot, Sebastian, excellent work!
I have upgraded about 40 different QA Farm systems (x86: 32-bit, 64-bit,
single-core, multi-core 2 to 32, single-socket, du
On 08/13/2013 02:47 AM, Paul Gortmaker wrote:
On Mon, Aug 12, 2013 at 3:48 PM, Steven Rostedt wrote:
On Mon, 12 Aug 2013 18:34:13 +0200
Sebastian Andrzej Siewior wrote:
Dear RT folks!
I'm pleased to announce the v3.10.6-rt3 patch set.
Does this mean that I can drop 3.6-rt in favor of 3.8-
Hi Paul,
Although all articles declare that rcu read site is deadlock-immunity.
It is not true for rcu-preempt, it will be deadlock if rcu read site
overlaps with scheduler lock.
The real rule is that if the scheduler does its outermost rcu_read_unlock()
with one of those locks held, it has to
Hi Sebastian,
I'm pleased to announce the 3.8.9-rt4 release. [..]
This patch is needed to prevent the compiler error
drivers/gpu/drm/i915/i915_gem_execbuffer.c:1072:27:
error: 'seqno' undeclared (first use in this function)
Signed-off-by: Carsten Emde
Index: linux-3.8.4-rt2/
Hi Steven,
I'm pleased to announce the 3.6.11.1-rt32 stable release.
Unfortunately, there is another compile error:
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_wait_for_error’:
drivers/gpu/drm/i915/i915_gem.c:118:3: warning: passing argument 1 of
‘rt_spin_lock’ from incompatible poin
Steven,
I'm pleased to announce the 3.6.11.1-rt32 stable release.
Unfortunately, there is another compile error:
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_wait_for_error’:
drivers/gpu/drm/i915/i915_gem.c:118:3: warning: passing argument 1 of
‘rt_spin_lock’ from incompatible pointe
Steven,
I'm pleased to announce the 3.6.11.1-rt32 stable release.
Thank you.
Your patch-3.6.11.1 additionally needs
23d3b8bfb8eb20e7d96afa09991e6a5ed1c83164 (net: qdisc busylock needs
lockdep annotations) to avoid the compile error
drivers/net/ppp/ppp_generic.c: In function ‘ppp_dev_init’:
On 08/07/2012 02:23 PM, Alexey Khoroshilov wrote:
Do not leak memory by updating pointer with potentially
NULL realloc return value.
Found by Linux Driver Verification project (linuxtesting.org).
Thanks, Alexey!
Reviewed-by: Carsten Emde
Signed-off-by: Alexey Khoroshilov
---
drivers/gpu
On 07/19/2012 11:48 PM, Rafael J. Wysocki wrote:
On Thursday, July 19, 2012, Carsten Emde wrote:
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if CONFIG_CPU_IDLE is selected, the
menu governor additionally requires CONFIG_NO_HZ.
A particular C
does not
reflect it. Likewise, if one enables a deep state but a lighter state
still is disabled, then this has no effect. A related section has been
added to the documentation.
Signed-off-by: Carsten Emde
---
Documentation/cpuidle/sysfs.txt| 10 +-
drivers/cpuidle/governors/ladder.c
Rafael,
> Your patch doesn't seem to take this linux-next commit:
> http://git.kernel.org/?p=linux/kernel/git/rafael/linux-pm.git;a=commit;h=dc7fd275ae60ef8edf952aff2a62462f5d892fd4
> into account, does it?
Hmm, oops, you're right. This one came in after I checked it last time.
Changes in v2: A
does not
reflect it. Likewise, if one enables a deep state but a lighter state
still is disabled, then this has no effect. A related section has been
added to the documentation.
Signed-off-by: Carsten Emde
---
Documentation/cpuidle/sysfs.txt| 10 +-
drivers/cpuidle/governors/ladder.c
Rafael,
>> [..]
>> I could implement a sanitize mechanism of the ladder governor that
>> takes care the "disable" variables of all deeper states are set to 1,
>> if a state is disabled, and those of all lighter states are set to 0,
>> if a state is enabled. Do you wish me to do
Deepthi,
[..]
I could implement a sanitize mechanism of the ladder governor that
takes care the "disable" variables of all deeper states are set to 1,
if a state is disabled, and those of all lighter states are set to 0,
if a state is enabled. Do you wish me to do that?
No, I dont think thats
On 07/18/2012 01:48 PM, Deepthi Dharwar wrote:
On 07/18/2012 04:32 PM, Carsten Emde wrote:
On 07/18/2012 08:36 AM, Deepthi Dharwar wrote:
On 07/18/2012 12:29 AM, Carsten Emde wrote:
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if
On 07/18/2012 01:48 PM, Deepthi Dharwar wrote:
On 07/18/2012 04:32 PM, Carsten Emde wrote:
On 07/18/2012 08:36 AM, Deepthi Dharwar wrote:
On 07/18/2012 12:29 AM, Carsten Emde wrote:
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if
On 07/18/2012 08:36 AM, Deepthi Dharwar wrote:
On 07/18/2012 12:29 AM, Carsten Emde wrote:
There are two cpuidle governors ladder and menu. While the ladder
governor is always available, if CONFIG_CPU_IDLE is selected, the
menu governor additionally requires CONFIG_NO_HZ.
A particular C state
Hi,
when trying to disable a specific C state in order to improve the
idle responsiveness of a system but still enjoy some power saving,
we noted that writing to the related sysfs variable had no effect.
This patch allows to disable C states of the ladder governor.
-Carsten.
--
To unsub
not been disabled, and it will demote, if the
current C state was disabled.
Signed-off-by: Carsten Emde
---
drivers/cpuidle/governors/ladder.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-3.4.4-rt14-rc2-64/drivers/cpuidle/governors/ladder.c
Avi Kivity wrote:
David Brown wrote:
I thought I'd try out the realtime patch set and it didn't work at all
with kvm. The console didn't dump anything and the system completely
locked up.
Up to now, the unmodified kvm module never worked with any RT kernel.
This would only change, if RT patched
Thomas,
we are pleased to announce the v2.6.22.1-rt3 kernel
Thanks a lot!
Using the .config file from the previous stable version (2.6.21.6-rt21),
the new version runs okay on an x86_64 system. On an i386 system,
however, the system is crashing at an early boot stage displaying an
INT13 reg
28 matches
Mail list logo
