This stray down would cause a permanent sleep which doesn't seem correct.
The other uses of this semaphore appear fairly mutex like it's even initialized
with init_MUTEX() .. So here a patch for removing this one down().
Signed-off-by: Geoff Levand <[EMAIL PROTECTED]>
Signe
On Tue, 2007-12-18 at 17:10 -0800, Andrew Morton wrote:
> is correct. Although not exactly a thing of beauty.
This isn't the worst I've seen ;( .. Do you think the ending should fall
through instead of having two returns?
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linu
On Wed, 2007-12-19 at 10:06 -0500, Miles Lane wrote:
> [ 11.827653] PM: Creating hibernation image:
> [ 11.827658] WARNING: at arch/x86/kernel/smp_32.c:561
> native_smp_call_function_mask()
> [ 11.827661] Pid: 9940, comm: pm-hibernate Not tainted
> 2.6.24-rc5-mm1 #8
> [ 11.827665] [] show
On Wed, 2007-12-19 at 10:42 -0800, Daniel Walker wrote:
> On Wed, 2007-12-19 at 10:06 -0500, Miles Lane wrote:
> > [ 11.827653] PM: Creating hibernation image:
> > [ 11.827658] WARNING: at arch/x86/kernel/smp_32.c:561
> > native_smp_call_function_mask()
> > [ 11.
On Tue, 2007-12-18 at 19:04 -0800, Geoff Levand wrote:
> Unfortunately there wasn't enough context in the patch to see
> that there is a down() earlier in the routine, and that the patch
> does indeed remove an incorrectly placed down(). Here is the
> entire routine, marked with what the patch re
On Thu, 2007-12-20 at 12:06 -0800, Andrew Morton wrote:
> On Thu, 20 Dec 2007 11:32:25 -0800 Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2007-12-18 at 19:04 -0800, Geoff Levand wrote:
> >
> > > Unfortunately there wasn't enough context in the p
On Mon, 2008-01-28 at 10:32 -0800, Max Krasnyanskiy wrote:
> Just this patches. RT patches cannot achieve what I needed. Even RTAI/Xenomai
> can't do that.
> For example I have separate tasks with hard deadlines that must be enforced
> in 50usec kind
> of range and basically no idle time whatso
On Mon, 2008-01-28 at 16:12 -0800, Max Krasnyanskiy wrote:
> Not accurate enough and way too much overhead for what I need. I know at this
> point it probably
> sounds like I'm talking BS :). I wish I've released the engine and examples
> by now. Anyway let
> me just say that SW MAC has crazy
The lock field in plist_head_init() is used for debugging the plist,
and if a NULL is sent in it spews constant errors with debugging enabled ..
So I added what looks like the correct spinlocks into the plist_head_init().
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/workq
On Wed, 2005-02-09 at 04:50, Russell King wrote:
> What you'll find is that the ARM interrupt structure is designed to
> efficiently meet the requirements of our wide range of hardware interrupt
> controllers, with chained interrupt controllers, with as low latency as
> possible.
>
> In essence,
On Tue, 2005-02-08 at 23:43, Ingo Molnar wrote:
> eventually ARM should be merged to the generic IRQ subsystem and in the
> process it is very likely that the generic IRQ subsystem has to be
> changed to fit ARM's needs as well. But separating out new features and
> keeping the old ARM blob in plac
I found some points during schedule when interrupts are off for
long periods . These two patches seem to help. One enables interrupts
inside schedule() , so that interrupts are enabled after each
need-resched loop, then disabled again before __schedule() is called.
The other patch
On Fri, 2005-02-11 at 09:30, Ingo Molnar wrote:
>
> i'm wondering what the best approach would be. Right now if
> DIRECT_PREEMPT is enabled [it's disabled currently] and a higher-prio
> task has been woken up we switch to it without ever enabling interrupts
> again. Re-enabling interrupts during s
On Fri, 2005-02-11 at 12:04, Russell King wrote:
>
> Please substantiate your claim that up() is very expensive on ARM.
> I disagree:
I should have made it clear that I was talking about the RT version of
up() . The RT version doesn't have any assembly in it, and it is
expensive.
> Plus
time.patch
The patch order is as follows
http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.11-rc3.bz2
http://people.redhat.com/~mingo/realtime-preempt/realtime-preempt-2.6.11-rc3-V0.7.38-01
common_arm_realtime.patch
Enjoy!
Daniel Walker
-
To unsubscribe from this list: sen
There is a problem with *_sleep_on() functions when they call schedule() .
Interrupts
should be enabled , but they aren't. So a warning message is printed letting
everyone
know that your calling schedule() from an invalid context.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]
with this, and it makes ARM
integration a little easier .
I also modified the make files so that individual files in kernel/irq/
can be compiled depending on config options.
The full ARM RT patch is here,
ftp://source.mvista.com/pub/realtime/arm/common_arm_realtime.patch
Daniel Walker
On Sat, 2007-11-17 at 12:44 +0100, Remy Bohmer wrote:
> Hello Steven,
>
> > The taker of a mutex must also be the one that releases it. I don't see
> > how you could use a mutex for this. It really requires some kind of
> > completion, or a compat_semaphore.
>
> I tried several ways of working a
On Sat, 2007-11-17 at 18:09 +0100, Remy Bohmer wrote:
> Actually, IMO, compat_semaphores behave like semaphores should behave,
> and thus the same as they behave on a non-RT kernel, and at the
> locations where the semaphores are now misused as mutexes on RT, we
> should replace them by differentl
On Sat, 2007-11-17 at 18:46 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > > Actually, IMO, compat_semaphores behave like semaphores should
> > > behave, and thus the same as they behave on a non-RT kernel, and at
> > > the
On Sat, 2007-11-17 at 19:04 +0100, Ingo Molnar wrote:
>
> split the list with you? Feel free to take any of those :-) dev->sem is
> nontrivial and probably not possible right now - and some of the others
> might be problematic too. But there might be fixable ones in the list.
> This shouldnt b
t the problem was,
instead of causing an endless recursive crash.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/exit.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6.23.1/kernel/exit.c
===
--- linux-2.
On Tue, 2007-10-30 at 19:44 -0400, Steven Rostedt wrote:
> I did this change once before, while debugging. I had the same issue. This
> BUG_ON was giving me recursive crashes that prevented me knowing WTF was
> going on. I thought I even submitted a patch to remove it. Perhaps I
> forgot to. Nope
I reworked the broken out series for 2.6.22.1-rt5 (note not -rt3) so
that it's a little more bisectable. I found that many of the patches
would compile but wouldn't boot.
Combined patch,
ftp://source.mvista.com/pub/dwalker/rt/patch-2.6.22.1-rt4-dw1
The broken out series is here,
ftp://source.m
On Thu, 2007-07-19 at 20:37 -0700, Daniel Walker wrote:
> I reworked the broken out series for 2.6.22.1-rt5 (note not -rt3) so
Woops , I mean , 2.6.22.1-rt4 here..
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
On Sat, 2007-07-21 at 13:59 +0200, Ingo Molnar wrote:
> * Mark Tiefenbruck <[EMAIL PROTECTED]> wrote:
>
> > IO window: disabled.
> > MEM window: c020-c02f
> > PREFETCH window: disabled.
> > PCI: Bridge: :00:14.4
> > IO window: disabled.
> > MEM window: c030-c03f
> > PREFE
Strange rcu_read_unlock() which causes a imbalance, and boot hang.. I
didn't notice a reason for it, and removing it allows my system to make
progress.
This should go into the preempt-realtime-sched.patch
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
Index: linux-2.6.22.1/ker
could
trigger or not depending on when/if certain threads run.
Here is a patch to comment them out. This should go into the
preempt-realtime-sched.patch
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
Index: linux-2.6.22.1/ker
I released another version of my tree .. It's still based on
2.6.22.1-rt4 . It's even more bisectable, but still not fully
bisectable.
I included the two fixes I post earlier today,
[PATCH -rt] temporary WARN_ON removal
[PATCH -rt] drop spurious rcu unlock
Here's the combined patch,
ftp://sour
On Sun, 2007-07-22 at 20:13 -0700, Paul E. McKenney wrote:
> On Sun, Jul 22, 2007 at 10:22:37AM -0700, Daniel Walker wrote:
> >
> > Strange rcu_read_unlock() which causes a imbalance, and boot hang.. I
> > didn't notice a reason for it, and removing it allows my s
es+0x54/0x12c
> > > [] add_preempt_count+0x12/0xcc
> > > [] unmap_region+0xeb/0x13b
> > > [] do_munmap+0xea/0xff
> > > [] sys_munmap+0x31/0x40
> > > [] syscall_call+0x7/0xb
> > > [] _shift_data_right_pages+0xb9/0xd1
> > > ===
> > > ---
>
whole function.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
mm/quicklist.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Index: linux-2.6.22.1/mm/quicklist.c
===
--- linux-2.6.22.1.orig/mm/quicklist.
On Sat, 2007-07-21 at 23:07 +0100, Rui Nuno Capela wrote:
> Call Trace:
> [] show_trace_log_lvl+0x1a/0x30
> [] show_stack_log_lvl+0xb6/0xe0
> [] show_registers+0x201/0x330
> [] die+0x118/0x260
> [] do_page_fault+0x193/0x600
> [] error_code+0x72/0x78
> [] activate_task+0x4f/0xb0
> [] try_to
On Mon, 2007-07-23 at 18:32 +0200, Peter Zijlstra wrote:
> On Mon, 2007-07-23 at 08:21 -0700, Daniel Walker wrote:
> > Resolves,
> >
> > BUG: sleeping function called from invalid context cc1(29651) at
> > kernel/rtmutex.c:636
> > in_atomic():1 [0001], irqs_d
On Mon, 2007-07-23 at 20:23 +0200, Ingo Molnar wrote:
>
> how about: "if you've got some time then please also add a few comments,
> because the code was quite non-obvious to me and I misunderstood it when
> I tried to fix it. Thanks."
Not exactly what I was thinking of .. More like,
"LOCKING
On Mon, 2007-07-23 at 20:58 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > (btw, your comment above comes off very snide, which I don't
> > appreciate. I haven't done anything that remotely warrants that.)
>
> That snide
On Mon, 2007-07-23 at 21:55 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > These two WARN_ON calls send my system into a boot hang. They trigger
> > over and over , some examples below.
>
> hm, could you try to figure out why they
On Mon, 2007-07-23 at 09:08 -0700, Daniel Walker wrote:
> On Sat, 2007-07-21 at 23:07 +0100, Rui Nuno Capela wrote:
>
> > Call Trace:
> > [] show_trace_log_lvl+0x1a/0x30
> > [] show_stack_log_lvl+0xb6/0xe0
> > [] show_registers+0x201/0x330
> > [] die+0x1
me-preempt/
> >
> > more info about the -rt patchset can be found in the RT wiki:
> >
> > http://rt.wiki.kernel.org
> >
> > Changes since -rt4:
> >
> > - MM fix: PCP pages locking (Peter Zijlstra)
> >
> > - yield() fix: remove s
On Mon, 2007-08-27 at 15:55 -0700, Stephane Eranian wrote:
> Yet the model name looks strange. So we need to run one more test,
> as the fam/model is not enough. What we need to check is whether or
> not this processor implements architectural perfmon or not.
>
> Could you please compile and run
On Tue, 2007-08-28 at 12:39 +0200, John Sigler wrote:
> Why does pdflush kick in to ruin my party? :-)
> The expected latency is ~600 µs.
> http://linux.kernel.free.fr/latency/pdflush.trace
> Does ide_inb mean I'm reading from the disk?
Does your real time application lock it's memory, or allow i
On Tue, 2007-08-28 at 02:12 -0700, Stephane Eranian wrote:
> Daniel,
>
> On Mon, Aug 27, 2007 at 04:07:54PM -0700, Daniel Walker wrote:
> > On Mon, 2007-08-27 at 15:55 -0700, Stephane Eranian wrote:
> >
> > > Yet the model name looks strange. So we need to run o
On Tue, 2007-08-28 at 10:05 -0700, Stephane Eranian wrote:
> Daniel,
>
> On Tue, Aug 28, 2007 at 07:34:44AM -0700, Daniel Walker wrote:
> > On Tue, 2007-08-28 at 02:12 -0700, Stephane Eranian wrote:
> > > Daniel,
> > >
> > > On Mon, Aug 27, 200
The patch below fixes the hang (not the stuck NMI) .. Not totally sure
why, but the cpus are stuck in a loop waiting for the endflag which
never comes .. This also plays with the nmi hz which might do
something.. /proc/interrupt doesn't show any nmi's either..
Daniel
Here's a simpler patch that fixes the boot hang ..
We have to call off the IPI looping regardless of the check_nmi_watchdog
outcome..
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
Index: linux-2.6.22/arch/i386/k
Lines are too long..
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/fork.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Index: linux-2.6.22/kernel/fork.c
===
--- linux-2.6.22.orig/kernel/
Just get_monotonic_cycles() switched to now() ..
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/latency_trace.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
Index: linux-2.6.22/kernel/latency_t
without this the idle routine still gets traced.. This is done already
for ACPI idle , but it should also be done for other idle routines.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/process.c |9 +
arch/x86_64/kernel/process.c | 10 ++
2
This enables the /proc/preempt_max_latency facility for timing modes,
even if event tracing is disabled. Wakeup latency was the only one
that had this feature in the past.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/sysctl.c |2 +-
1 file changed, 1 insertion(+), 1 de
Replace the old PICK_OP style macros with PICK_FUNCTION. Although,
seqlocks has some alien code, which I also replaced as can be seen
from the line count below.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/pickop.h |4
include/linux/seqlock.h
Reaplace old PICK_OP style macros with the new PICK_FUNCTION macro.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/sched.h| 13 -
include/linux/spinlock.h | 345 ++-
kernel/rtmutex.c |2
lib/dec_and_
. Although the seqlock changes are larger than the originals
I think over all the patchset is worth while.
Incorporated peterz's suggestion to not require TYPE_EQUAL() to only
use pointers.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/pickop.h | 36 +
in
just used num_possible_cpus() . I also drop
a string which only hold "CPU" and just inserted it where it was used.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/latency_hist.h |1
kernel/latency_hist.c| 119 +
On Wed, 2007-08-29 at 09:44 +1000, Nick Piggin wrote:
> Daniel Walker wrote:
> > PICK_FUNCTION() is similar to the other PICK_OP style macros, and was
> > created to replace them all. I used variable argument macros to handle
> > PICK_FUNC_2ARG/PICK_FUNC_1ARG. Otherwise the
On Tue, 2007-08-28 at 22:18 -0400, Theodore Tso wrote:
> On Mon, Aug 27, 2007 at 02:12:56PM +0200, Jes Sorensen wrote:
> > Yes, as well as 12 committee members, of which 5 didn't even comply with
> > their own git commit requirement last time I checked.
>
> Note that the git commit metric is not
I've updated to 2.6.23-rc4 .. This is an "Ingo appears to be busy.."
release .. I've been waiting for a -rt update , but there hasn't been
one for a while. So my tree is the best everyone will get for now.
ftp://source.mvista.com/pub/dwalker/rt/patch-2.6.23-rc4-dw1
ftp://source.mvista.com/pub/dwa
On Fri, 2007-08-10 at 08:14 -0600, Gregory Haskins wrote:
> ---
>
> include/linux/sched.h |7 +--
> kernel/latency_trace.c | 18 +++---
> 2 files changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 8ebb43c..233d2
On Wed, 2007-08-29 at 14:24 -0700, Stephane Eranian wrote:
> Now on Core Duo, there is no PEBS anyway, so it is okay to use counter 0
> for NMI. The problem is that the detection code in perfctr-watchdog.c
> treats a Core Duo and a Core 2 Duo the same way as they both have the
> X86_FEATURE_ARCH_
On Thu, 2007-08-30 at 14:05 -0700, Stephane Eranian wrote:
> Daniel,
> Yes, I realized I missed a small detail in the switch statement.
> Could you try the new version?
This patch still has the stuck NMI .. Essentially the same thing that
happened without the patch..
Feel free to keep sending pa
On Fri, 2007-08-31 at 09:21 -0700, Stephane Eranian wrote:
> Daniel,
>
> On Fri, Aug 31, 2007 at 07:43:20AM -0700, Daniel Walker wrote:
> > On Thu, 2007-08-30 at 14:05 -0700, Stephane Eranian wrote:
> > > Daniel,
> >
> > > Yes, I realized I missed
McKenney): needs proper integration
> - latency tracer changes (Daniel Walker): needs review
> - PICK_OP changes (Daniel Walker): needs review
The PICK_OP changes got reviewed by Ingo , as of,
http://marc.info/?l=linux-rt-users&m=118638506125380&w=2
They do need one small fix tho .. Be
On Fri, 2007-08-31 at 20:06 +0200, Björn Steinbrink wrote:
> > something to do with the nmi hertz adjustment that happens after
> > check_nmi_watchdog() ..
>
> Hm hm, does the same thing (watchdog stuck after check) happen with
> older kernels, ie. those before Stephane's changeset that made it
On Sat, 2007-09-01 at 03:00 +0200, Björn Steinbrink wrote:
> On 2007.08.31 17:24:46 -0700, Daniel Walker wrote:
> > On Fri, 2007-08-31 at 20:06 +0200, Björn Steinbrink wrote:
> >
> >
> > > > something to do with the nmi hertz adjustment that happens
On Sat, 2007-09-01 at 09:27 +0200, Thomas Gleixner wrote:
>
> Yeah, I know. Still I wanted to go through it myself.
>
Ok,
Here are some other trivial fixes,
http://lkml.org/lkml/2007/8/28/331
http://lkml.org/lkml/2007/8/28/334
Daniel
-
To unsubscribe from this list: send the line "unsubscri
On Fri, 2007-08-31 at 22:59 +0200, Thomas Gleixner wrote:
> - loadavgrt fix (Luis Claudio R. Goncalves)
Sven caught that this patch was broken, I think there is an updated
one.. It's also breaking !PREEMPT_RT compiles..
dwalker2/140 failed
kernel/timer.c: In function 'calc_load':
kernel/timer.c
g one of the ia64 guys can help
test this?
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
drivers/char/hpet.c | 32
1 file changed, 20 insertions(+), 12 deletions(-)
Index: linux-2.6.22/drivers/char/hpet.c
==
On Sat, 2007-09-01 at 08:51 -0700, Daniel Walker wrote:
> The warnings,
>
> drivers/char/hpet.c:72: warning: 'clocksource_hpet' defined but not used
> drivers/char/hpet.c:81: warning: 'hpet_clocksource' defined but not used
>
> from,
>
> commit 3b2b6
On Sat, 2007-09-01 at 22:32 +0200, Andi Kleen wrote:
> On Saturday 01 September 2007 21:51:42 Stephane Eranian wrote:
> > Hello,
> >
> > Here is a patch to fix the NMI watchdog problem on CoreDuo processor.
> > I think we still need Daniel's patch to make the error path (when you
> > are stuck) do
checking
if the test was successful or not.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/nmi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.22/arch/i386/kernel/nmi.c
===
---
On Sat, 2007-09-01 at 14:33 -0700, Stephane Eranian wrote:
> Daniel,
>
> Thanks for your help tracking down this bug. Maybe we can close
> the bugzilla report now.
No problem , and thanks for taking the time to dig into it ..
I'll close the bugzilla report.
Daniel
-
To unsubscribe from this li
On Sat, 2007-09-01 at 23:45 +0200, Andi Kleen wrote:
> On Saturday 01 September 2007 22:54:17 Daniel Walker wrote:
> > In the case when an nmi gets stucks the endflag stays equal to zero. This
> > causes the busy looping on other cpus to continue, even tho the nmi test
> > is
On Fri, 2007-08-31 at 04:05 +0200, Roman Zippel wrote:
> Hi,
>
> I'm glad to announce a working prototype of the basic algorithm I
> already suggested last time.
> As I already tried to explain previously CFS has a considerable
> algorithmic and computational complexity. This patch should now make
On Sat, 2007-09-01 at 22:46 -0400, Matthew Wilcox wrote:
> */
> if (task == current) return 0;
>
> - if ((task->state != TASK_STOPPED) && (task->state !=
> TASK_TRACED)) {
> + if (!is_task_stopped_or_traced(task->state)) {
> DPRINT(("cannot attach to no
On Sun, 2007-09-02 at 16:47 +0200, Roman Zippel wrote:
> > > (1) time = sum_{t}^{T}(time_{t})
> > > (2) weight_sum = sum_{t}^{T}(weight_{t})
> >
> > I read your description, but I was distracted by this latex style
> > notation .. Could you walk through in english what these two equat
On Mon, 2007-09-03 at 20:20 +0200, Roman Zippel wrote:
> Basically that's it and I hope that explains the basic math a bit easier. :-)
>
It helps a tiny bit .. However, I appreciate that you took the time to
write this .. Thanks you.
Daniel
-
To unsubscribe from this list: send the line "unsubs
On Tue, 2007-09-04 at 17:12 -0700, Fernando Lopez-Lezcano wrote:
> Hi Ingo... I'm getting reports from some of my Planet CCRMA users (which
> I confirmed) that the latest rt kernel I released has broken suspend
> (tested on fc6 & fc7, stock Fedora kernel works fine - the rt
> configuration files ar
On Wed, 2007-09-05 at 14:43 +0100, Denys Vlasenko wrote:
> Build system: section garbage collection for vmlinux
>
>
> Newer gcc and binutils can do dead code and data removal
> at link time. It is achieved using combination of
> -ffunction-sections -fdata-sections options for gcc and
> --gc-secti
On Wed, 2007-09-05 at 19:37 +0100, Denys Vlasenko wrote:
> On Wednesday 05 September 2007 17:29, Daniel Walker wrote:
> > On Wed, 2007-09-05 at 14:43 +0100, Denys Vlasenko wrote:
> > > Build system: section garbage collection for vmlinux
> > >
> > >
> >
On Wed, 2007-09-05 at 20:14 +0100, Denys Vlasenko wrote:
> On Wednesday 05 September 2007 19:38, Daniel Walker wrote:
> > > > You version doesn't work with CONFIG_MODULES right?
> > >
> > > It works with CONFIG_MODULES.
> >
> > Really? Take a l
On Wed, 2007-09-05 at 21:31 +0200, Adrian Bunk wrote:
> On Wed, Sep 05, 2007 at 08:14:12PM +0100, Denys Vlasenko wrote:
> > On Wednesday 05 September 2007 19:38, Daniel Walker wrote:
> > > > > You version doesn't work with CONFIG_MODULES right?
> > > &
On Wed, 2007-09-05 at 20:49 +0100, Denys Vlasenko wrote:
> What does "it" stand for in this sentence?
"it" is your patches, and I think we got to bottom of it .. "it" (i.e.
your patches) don't actually work with modules, which is what you
originally contended ..
> My patch was tested to work in
On Thu, 2007-09-06 at 11:57 +0100, Denys Vlasenko wrote:
> On Wednesday 05 September 2007 20:46, Daniel Walker wrote:
> > On Wed, 2007-09-05 at 20:49 +0100, Denys Vlasenko wrote:
> >
> > > What does "it" stand for in this sentence?
> >
> > "it&q
On Mon, 2007-08-06 at 10:55 +0200, John Sigler wrote:
> John Sigler wrote:
>
> Would anyone care to comment?
I'm not sure if this is the answer that you looking for, but yes you
certainly will find fixed bug is older version of the tree.
> Perhaps I could also test a different strategy, such as
On Tue, 2007-08-07 at 10:27 +0200, John Sigler wrote:
> Daniel Walker wrote:
>
> > John Sigler wrote:
> >
> >> Would anyone care to comment?
> >
> > I'm not sure if this is the answer that you're looking for, but yes you
> > certainly will
On Mon, 2007-08-06 at 15:07 -0400, Gregory Haskins wrote:
> Hi Ingo,
> I think there is a latent race condition somewhere in the code. We
> find that -rt works on our 4-way (and under) systems, but have problems
> on our 8-ways.
>
> If you run without nmi_watchdog, the system will sometimes boo
This patch below hangs my system on boot if I set nmi_watchdog=2 . It
shows the NMI as stuck then the system hangs .. nmi_watchdog=1 works
fine, and the system boots without any watchdog options ..
The machine is an Intel allagash development board, and it has two dual
core Pentium-M cpus. I atta
On Wed, 2007-08-08 at 16:20 +0200, Björn Steinbrink wrote:
> On 2007.08.07 17:06:49 -0700, Daniel Walker wrote:
> >
> > This patch below hangs my system on boot if I set nmi_watchdog=2 . It
> > shows the NMI as stuck then the system hangs .. nmi_watchdog=1 works
> >
On Mon, 2007-08-06 at 09:21 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Replace the old PICK_OP style macros with PICK_FUNCTION. Although,
> > seqlocks has some alien code, which I also replaced as can be seen
> > from the line cou
Simple WARN_ON to catch any underflow in rcu_read_lock_nesting.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/rcupreempt.c |6 ++
1 file changed, 6 insertions(+)
Index: linux-2.6.22/kernel/rcupre
This mismerge caused my networking to malfunction. The interface would
come up, but no traffic would make it in/out ..
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
net/sched/sch_generic.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.22/net
In prior -rt verisons the last_tick value was called wall_jiffies
and was initialized in this same way as below. If this value isn't
initialized the calc_load function gets skewed for several minutes
right after boot up. Skewed meaning always zero.
Signed-off-by: Daniel Walker <[EMAIL P
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/rt_lock.h |6 --
include/linux/spinlock.h |5 +++--
2 files changed, 7 insertions(+), 4 deletions(-)
Index: linux-2.6.22/include/linux/rt_
least one thread running on every invocation.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/softirq.c |2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6.22/kernel/softirq.c
===
--- linux-2.6.22.
. Although the seqlock changes are larger than the originals
I think over all the patchset is worth while.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/pickop.h | 32 +++
include/linux/rt_lock.h | 129 +++-
2 files chang
Reaplace old PICK_OP style macros with the new PICK_FUNCTION macro.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/sched.h| 13 -
include/linux/spinlock.h | 345 ++-
kernel/rtmutex.c |2
lib/dec_and_
Replace the old PICK_OP style macros with PICK_FUNCTION. Although,
seqlocks has some alien code, which I also replaced as can be seen
from the line count below.
Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/seqlock.h
From: Steven Rostedt <[EMAIL PROTECTED]>
Ingo,
I think this was sent before, and it did cause problems before. Would
there be *any* reason to have non-threaded softirqs but threaded hardirqs.
I can see lots of issues with that.
This patch has selecting hardirqs also select softirqs as threads.
I've released another version of the real-time tree. It's just a
slightly more bisectable tree, and it includes the fixes I've just
released.
You can download a combined patch from,
ftp://source.mvista.com/pub/dwalker/rt/patch-2.6.23-rc1-rt6-dw1
Or a broken out set from,
ftp://source.mvista.c
On Mon, 2007-07-30 at 10:28 +0530, Ankita Garg wrote:
> On Sun, Jul 29, 2007 at 07:45:40PM -0700, Daniel Walker wrote:
> > Signed-off-by: Daniel Walker <[EMAIL PROTECTED]>
> >
> > ---
> > include/linux/rt_lock.h |6 --
> > include/linux/spinlock
On Mon, 2007-07-30 at 11:22 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > + /*
> > +* If our rcu_read_lock_nesting went negative, likely
> > +* something is wrong..
> > +*/
> > + WARN_ON(current->rcu_r
201 - 300 of 808 matches
Mail list logo
