On Wed, 2007-02-07 at 00:14 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2007-02-06 at 23:56 +0100, Ingo Molnar wrote:
> >
> > > changing the current 'timer' entry (which is line 2 of /proc/interrupts)
> >
On Tue, 2007-02-06 at 18:15 -0500, Rob Landley wrote:
> On Tuesday 06 February 2007 3:40 pm, Daniel Walker wrote:
> > In this case "different" goes into userspace .. So different could mean
> > userspace regression, which is something that we don't want. I have no
On Wed, 2007-02-07 at 00:28 +0100, Ingo Molnar wrote:
> actually, i quoted what you said:
>
> | If we change the current "timer" entry to be listed as "lapic-timer"
> | and not "IO-APIC-edge" (or one of the other names) and replace it with
> | the count from LOC
>
> this is a pretty clear sent
On Wed, 2007-02-07 at 00:36 +0100, Thomas Gleixner wrote:
> There are no other clock event devices in a PC system at the moment
> and /proc/interrupt does not care, whether the interrupt was setup for a
> clock event device or something else. It displays the name which is
> given in the irqaction
I guess I will respond
On Wed, 2007-02-07 at 00:51 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > > | If we change the current "timer" entry to be listed as
> > > | "lapic-timer" and not "IO-APIC-edge&qu
After looking at the scheduler timing I was thinking it might be a fair
trade off to convert sched_clock to return cycles instead of converting
to nanosecond each time it reads ..
I'm just probing for anyone thoughts on this ..
I'm not promoting a specific implementation, but I would think the
On Sat, 2007-02-10 at 20:51 +0100, Miguel Ojeda wrote:
> Andrew, Daniel who reported the crash has tested this patch and says that it
> works fine avoiding it, so you can merge.
>
Yes, I tested it with the ks0108 enabled alone, and with both ks0108 and
CFAG12864B .. Both booted fully..
Daniel
On Mon, 2007-02-12 at 21:35 -0800, Andrew Morton wrote:
>
> This looks hacky.
>
One other thing that could be added is a change in the initcalls .
ks0108 should be subsys_initcall() and the LCD devices
device_initcall(). That would make sure one runs before the other. I
don't think that alone w
On Fri, 2007-02-16 at 22:28 +0800, Adam J. Richter wrote:
> My system clock runs at approximately half speed in
> linux-2.6.20, 2.6.20-git10 and 2.6.20-git11. That is, it takes about
> two hours for "date" to report that one hour has elapsed. "hwclock"
> returns the correct time, of course.
On Fri, 2007-02-16 at 11:30 -0500, Frank Ch. Eigler wrote:
> Jeff Muizelaar <[EMAIL PROTECTED]> writes:
>
> > I've built a tool with the goal of logging mmio writes and reads by
> > device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
>
> FWIW, this is exactly a type of add-on trace
On Fri, 2007-02-16 at 13:10 -0500, Jeff Muizelaar wrote:
> On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
> > I've been working on a patch set (below), to expose the clocksources
> > used by generic time to multiple users . It would allow timestamps from
>
On Fri, 2007-02-16 at 14:34 -0500, Jeff Muizelaar wrote:
> On Fri, Feb 16, 2007 at 10:28:50AM -0800, Daniel Walker wrote:
> > On Fri, 2007-02-16 at 13:10 -0500, Jeff Muizelaar wrote:
> > > On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
> > > > I&
On Fri, 2007-02-16 at 17:10 -0500, Jeff Muizelaar wrote:
>
> I still meant for _with_features to have same semantics so calling:
>
> clocksource_get_clock_with_features(CLOCKSOURCE_PM_UNAFFECTED|CLOCKSOURCE_STABLE
> |CLOCKSOURC_ATOMIC|CLOCKSOURCE_64BITS|CLOCKSOURCE_CONTINUOUS);
>
> would be eq
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/timer.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.20/kernel/timer.c
===
--- linux-2.6.20.orig/kernel/timer.c
+++ linux-2.6.20/
a more
interesting order. It's forward looking.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/tsc.c |2
arch/x86_64/kernel/tsc.c|2
include/linux/clocksource.h |8 +-
kernel/time/clocksource.c | 132 +---
Update mips for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/mips/kernel/time.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6.19/arch/mips/kernel/time.c
===
--- linux-2.6.19.orig/arch/mips/
Update drivers/ for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
drivers/clocksource/acpi_pm.c|2 +-
drivers/clocksource/cyclone.c|1 -
drivers/clocksource/scx200_hrt.c |1 -
3 files changed, 1 insertion(+), 3 deletions(-)
Index: linux-2.6.19/d
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/tsc.c | 31 +--
1 file changed, 21 insertions(+), 10 deletions(-)
Index: linux-2.6.19/arch/x86_64/kernel
This is something Thomas already dropped, and I'm just sticking
with that .. If you register your clocksource _twice_ your kernel will
likely not work correctly (and might crash).
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/time/clocksource.c | 19 ++--
, and moves all
the changes included in -mm.
This is also moving do_timer and the load calculation code which was
connect to the timekeeping code. Moving it provided for slightly better
compiler optimization.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h
One new API call clocksource_get_clock() which allows clocks to be selected
based on their name, or if the name is null the highest rated clock is returned.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 12
kernel/time/clocksource.c
Uses the block notifier to replace the functionality of update_callback().
update_callback() was a special case specifically for the tsc, but including
it in the clocksource structure duplicated it needlessly for other clocks.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arc
Update x86_64 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/hpet.c |1 -
arch/x86_64/kernel/tsc.c | 11 ---
2 files changed, 4 insertions(+), 8 deletions(-)
Index: linux-2.6.19/arch/x86_64/kernel/
Update i386 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c|1 -
arch/i386/kernel/i8253.c |1 +
arch/i386/kernel/tsc.c | 23 +++
arch/i386/kernel/vmitime.c |2 +-
4 files changed, 13 insertions(
Compile patch .. This just adds some code so the next few patches will compile.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |6 ++
1 file changed, 6 insertions(+)
Index: linux-2.6.19/include/linux/clockso
Update ARM for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/arm/mach-imx/time.c |1 -
arch/arm/mach-ixp4xx/common.c |1 -
arch/arm/mach-netx/time.c |1 -
arch/arm/mach-pxa/time.c |1 -
4 files changed, 4 deletions(-)
Index: linux-
he flags.
The point is to list all the negative side effects that some clocks have
which the programmer knows in advance that their code can not tolerate.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 35 +--
Adds a call back interface for register/rating change events. This is also used
later in this series to signal other interesting events.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 37 +
include/linux/timekee
Update avr32 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/avr32/kernel/time.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6.19/arch/avr32/kernel/time.c
===
--- linux-2.6.19.orig/arch
x27;s needed.
The fast path is also reduced to checking a single atomic value.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |5
include/linux/timekeeping.h |4 ---
kernel/time/clocksource.c |6 +
kernel/time/timekeeping
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |3 -
kernel/time/clocksource.c | 118 ++--
2 files changed, 61 insertions(+), 60 deletions(-)
Index: linux-2.6.19/include/linux/clockso
This tree is mostly cleanups . I move timekeeping code into it's own
file, and I modify the clocksource interface to provide a more robust
API.
I've dropped some duplication off the hrt/dynamic tick patch set which
is all new to that tree and new to -mm. This is an -mm patch set , it's
not meant
This moves the timekeeping sysfs override layer into timekeeping.c and
removes the get_next_clocksource and select_clocksource functions, and
their component variables, since they are no longer used.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h
register their clocksources during time_init()
instead of using initcalls.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c |2 +-
arch/i386/kernel/i8253.c |2 +-
arch/i386/kernel/tsc.c |2 +-
arch/x86_64/kernel/hpet.c
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/tsc.c | 51 +---
include/linux/clocksource.h | 11 ++---
kernel/timer.c |3 ++
3 files changed, 45 insertions(+), 20 deletions(-)
Index:
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/Kconfig |4 -
arch/i386/kernel/tsc.c | 49 +
include/linux/clocksource.h | 15 -
kernel/time/clocksource.c | 125 +---
kernel/t
e the timer. It should work with an
HPET.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/tsc.c | 55
include/linux/clocksource.h | 16
2 files changed, 51 insertions(+), 20 deletions(-)
Index: l
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/time/clocksource.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
Index: linux-2.6.19/kernel/time/clocksource.c
===
--- linux-2.6.1
On Wed, 2007-01-31 at 09:59 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Move the generic timekeeping code from kernel/timer.c to
> > kernel/time/timekeeping.c. [...]
>
> please lets not do this just yet. While i have no problems wit
On Wed, 2007-01-31 at 10:34 +0100, Ingo Molnar wrote:
> a rating change can occur due to other things as well, not only due to
> 'tsc unstable' events. So keeping an API around that changes the rating
> (and propagates all related changes), makes more sense to me.
>
> also, a pure function call
On Wed, 2007-01-31 at 10:59 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > This is something Thomas already dropped, [...]
>
> (i think you forgot to Cc: Thomas here, nor is this something that
> Thomas' change dropped.)
Yes your
On Wed, 2007-01-31 at 11:17 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Adds a call back interface for register/rating change events. This is
> > also used later in this series to signal other interesting events.
>
> Th
On Wed, 2007-01-31 at 11:46 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Uses the block notifier to replace the functionality of
> > update_callback(). update_callback() was a special case specifically
> > for the tsc, but i
On Wed, 2007-01-31 at 12:07 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Modifies the way clocks are switched to in the timekeeping code. The
> > original code would constantly monitor the clocksource list checking
> > for newly
On Wed, 2007-01-31 at 12:46 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > One new API call clocksource_get_clock() which allows clocks to be
> > selected based on their name, or if the name is null the highest rated
> > clock is re
On Wed, 2007-01-31 at 12:50 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > -module_init(init_acpi_pm_clocksource);
> > +/*
> > + * This clocksource is removed from the clocksource_initcall
> > + * macro since it's man
On Wed, 2007-01-31 at 13:43 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > I've included this as another user of the clocksource interface. I
> > don't see a usage for this across all achitectures. So a fully generic
> &g
On Wed, 2007-01-31 at 18:10 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2007-01-31 at 12:50 +0100, Ingo Molnar wrote:
> > > * Daniel Walker <[EMAIL PROTECTED]> wrote:
> > >
> > > > -module_init(i
On Wed, 2007-01-31 at 18:55 +0100, Thomas Gleixner wrote:
> On Wed, 2007-01-31 at 09:39 -0800, Daniel Walker wrote:
> > > please read my reply above! To repeat: such flags tend to get forgotten,
> > > resulting in a less safe default behavior. Clock hardware and thus
&
On Wed, 2007-01-31 at 11:43 -0800, David Brownell wrote:
> > As a note, arm and mips both register their clocksources during
> > time_init() instead of using initcalls.
>
> That's actually platform-specific. If there's only one possible
> clocksource, that'd be the normal answer.
>
> Otherwise,
On Thu, 2007-02-01 at 00:23 +0100, Thomas Gleixner wrote:
> Daniel,
>
> On Wed, 2007-01-31 at 14:47 -0800, Daniel Walker wrote:
> > > So don't assume any platform doesn't use clocksource initcalls.
> >
> > What does your OMAP clocksource do now ? I thou
On Thu, 2007-02-01 at 16:16 +0100, Miguel Ojeda wrote:
> The problem is easy:
>
> ks0108_init() prints the error message and exit with -EINVAL, so the
> module isn't loaded properly.
>
> However, cfag12864b_init() is called, although ks0108 failed. It
> returns 0 and after a while cfag12864b call
On Thu, 2007-02-01 at 18:13 +0100, Miguel Ojeda wrote:
> >
> >
>
> Well, I use the word "module" for both cases: When I modprobe
> cfag12864b, if ks0108 fails, it doesn't get linked. So I thought the
> same happen for built-in drivers (in other words, I didn't think
> cfag12864b would be linked i
On Thu, 2007-02-01 at 18:39 +0100, Miguel Ojeda wrote:
> On 2/1/07, Daniel Walker <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-02-01 at 18:13 +0100, Miguel Ojeda wrote:
> >
> > > >
> > > >
> > >
> > > Well, I use the word "modul
On Mon, 2007-01-29 at 20:45 -0800, Andrew Morton wrote:
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-rc6-mm3/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/
>
I was running likely profiling and
This gave me some really odd compile errors.. Theres
a static inline for this function right above this define
so I just dropped the define.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/spinlock.h |1 -
1 files changed, 1 deletion(-)
Index: linux-2.6.19/include
I'm not sure about this code. It's checking the PM timer, and
doesn't seem to touch the TSC, then it marks the TSC unstable
based on the stability of the PM timer.
The reason that this caught my attention is that it
marks my (AFAIK stable) tsc as unstable when it first
runs.
Is there something
On Thu, 2006-12-07 at 10:58 +1030, Jonathan Woithe wrote:
> Upon an attempt to compile 2.6.19-rt3 I encountered the following compile
> error:
>
This was fix in -rt5 or 6 I think . The !PREEMPT_RT case. Current
version is -rt7
http://people.redhat.com/~mingo/realtime-preempt/patch-2.6.19-rt7
Da
On Mon, 2006-12-11 at 10:27 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > Sent this a long time ago, still exists.
> >
> > Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
>
> hm, what does this do, and why isnt it upstr
On Mon, 2006-12-11 at 16:59 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 2006-12-11 at 10:27 +0100, Ingo Molnar wrote:
> > > * Daniel Walker <[EMAIL PROTECTED]> wrote:
> > >
> > > > Sent this a long t
On Mon, 2006-12-11 at 20:05 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > + /*
> > +* Some boards will disable an interrupt when it
> > +* sets IRQ_PENDING . So we have to remove the flag
> > +* and re-enable to han
On Mon, 2006-12-11 at 19:54 +, Russell King wrote:
> > > what if the irq got disabled meanwhile? Also, chip->enable is a
> > > compatibility method, not something we should use in a flow handler.
> >
> > I don't know how other arches deal with IRQ_PENDING, but ARM (OMAP at
> > least) disable
> +
> + if (pm == last_pm) {
> + interval_tsc = now_tsc - last_tsc;
> + interval_tsc *= HZ;
> + do_div(interval_tsc, cpu_khz*1000);
> + } else {
> + if (pm < last_pm)
> + pm += ACPI_PM_OVRRUN;
> + pm_delta = pm
On Mon, 2006-12-18 at 16:53 +0100, Ingo Molnar wrote:
> an allyesconfig bootup generates the driver core warning below, in
> alsa_card_dummy_init().
>
> Ingo
>
> -->
> Calling initcall 0xc1ee1d35: alsa_card_dummy_init+0x0/0x8a()
> PM: Adding info for platform:snd_dummy.0
>
On Mon, 2006-12-18 at 16:31 +0100, Ingo Molnar wrote:
> crash in adummy_init() - allyesconfig bootup.
>
> Ingo
>
> >
> Calling initcall 0xc1eb1f7e: adummy_init+0x0/0xb9()
> adummy: version 1.0
> swapper/1[CPU#0]: BUG in kref_get at lib/kref.c:32
> [] show_trace_log_lvl+0x34
On Fri, 2006-12-15 at 14:27 -0800, [EMAIL PROTECTED] wrote:
> +
> +unsigned long long vmi_sched_clock(void)
> +{
> + return read_available_cycles();
> +}
> +
This sched_clock is likely broken if it's returning something other than
nanoseconds. It looks like cycles, but it's also getting pi
On Fri, 2006-12-15 at 14:27 -0800, [EMAIL PROTECTED] wrote:
> +
> +config NO_IDLE_HZ
> + bool
> + depends on PARAVIRT
> + default y
> + help
> + Switches the regular HZ timer off when the system is going
> idle.
> + This helps a hypervisor detect that the Lin
On Sat, 2007-01-06 at 12:37 -0800, Zachary Amsden wrote:
> >
> > There is already a dynamic tick (NO_HZ) system in the -mm tree .. Given
> > that this implementation seems unnecessary. Why do you need another
> > different system to do this?
> >
>
> We don't. This was written before the dynam
On Wed, 2007-01-03 at 13:12 -0800, [EMAIL PROTECTED] wrote:
> -# define __raw_spin_lock_irq(lock) __raw_spin_lock(lock)
> +
> +static inline void __raw_spin_lock_irq(raw_spinlock_t *lock)
> +{
> + asm volatile("\n1:\t"
> +LOCK_PREFIX " ; decb %0\n\t"
> +
On Sat, 2007-01-06 at 23:26 -0800, Andrew Morton wrote:
> diff -puN
> include/asm-i386/spinlock.h~spin_lock_irq-enable-interrupts-while-spinning-i386-implementation-fix
> include/asm-i386/spinlock.h
> ---
> a/include/asm-i386/spinlock.h~spin_lock_irq-enable-interrupts-while-spinning-i386-implem
(forgot to CC LKML)
The options,
CONFIG_CFAG12864B=y
CONFIG_CFAG12864B_RATE=20
causes a crash at boot in 2.6.20-rc3-mm1. I don't have the hardware
associated with the options. It looks like it just doesn't have guards
to detect if the hardware doesn't exists.
Here is the crash,
ks0108: ERROR:
On Mon, 2007-01-08 at 13:20 +0100, Peter Zijlstra wrote:
>
> Well, no. Draining after the inspect 'all' loop doesn't make sense, but
> looking at 2.6.20-rc3-rt0 remove_proc_entry() looks sane.
When it was inside the loop it drained every iteration . So it made more
sense to put it after the loop
On Tue, 2007-01-09 at 17:16 +0100, Pierre Peiffer wrote:
> @@ -133,8 +133,8 @@ struct futex_q {
>* Split the global futex_lock into every hash list lock.
>*/
> struct futex_hash_bucket {
> - spinlock_t lock;
> - struct list_head chain;
> + spinlock_t
On Tue, 2007-01-09 at 17:16 +0100, Pierre Peiffer wrote:
> @@ -1358,7 +1366,7 @@ static int futex_unlock_pi(u32 __user *u
> struct futex_hash_bucket *hb;
> struct futex_q *this, *next;
> u32 uval;
> - struct list_head *head;
> + struct plist_head *head;
>
On Wed, 2007-01-10 at 17:29 +0100, Pierre Peiffer wrote:
> >
> > Is this really necessary? The rtmutex will priority sort the waiters
> > when you enable priority inheritance. Inside the wake_futex_pi() it
> > actually just pulls the new owner off another plist inside the the
> > rtmutex structur
On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
> included. It includes the latest -hrt-dynticks tree and more.
Does the zero carry and meaning or did you just decide start using zero
instead of one?
Daniel
-
To uns
On Thu, 2006-11-16 at 22:12 +0100, Esben Nielsen wrote:
> On Thu, 16 Nov 2006, Daniel Walker wrote:
>
> > On Thu, 2006-11-16 at 16:35 +0100, Ingo Molnar wrote:
> >
> >> -rt0 is a rebase of -rt to 2.6.19-rc6, with lots of updates and fixes
> >> included. It in
On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > [...] Should we start a known regression list?
>
> please resend the bugs that still trigger for you with 2.6.19-rt0.
Did you look at the BKL reacquire issue I sen
On Fri, 2006-11-17 at 17:17 +0100, Ingo Molnar wrote:
> * Lee Revell <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 2006-11-16 at 23:07 +0100, Ingo Molnar wrote:
> > > * Daniel Walker <[EMAIL PROTECTED]> wrote:
> > >
> > > > [...] Should we start a
On Fri, 2006-11-17 at 12:36 -0500, Alan Stern wrote:
> void percpu_free(void *__pdata)
> {
> + if (!__pdata)
> + return;
Should be unlikely() right?
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
M
On Fri, 2006-11-17 at 13:07 -0500, Alan Stern wrote:
> On Fri, 17 Nov 2006, Daniel Walker wrote:
>
> > On Fri, 2006-11-17 at 12:36 -0500, Alan Stern wrote:
> >
> > > void percpu_free(void *__pdata)
> > > {
> > > + if (!__pdata)
> > >
On Tue, 2006-11-28 at 21:14 +0100, Ingo Molnar wrote:
> * Lee Revell <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2006-11-28 at 11:58 -0800, Fernando Lopez-Lezcano wrote:
> > > Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> > > using jackd and jack clients. This is a sample from
On Wed, 29 Nov 2006, Ingo Molnar wrote:
please talk to John and Thomas about GTOD interfaces. Right now the
solution used by the latency tracer is working out pretty OK - but if
something better comes along i can use that too. It's not a burning
issue though, unless you know of some bug. (i'm no
/*
* Spinlocks are used for interfaces that can be possibly called at
* interrupt level
*/
ACPI_EXTERN raw_spinlock_t _acpi_gbl_gpe_lock; /* For GPE data structs and
registers */
ACPI_EXTERN raw_spinlock_t _acpi_gbl_hardware_lock; /* For ACPI H/W except
GPE registers */
The problem i
On Tue, 2007-06-19 at 16:17 -0400, Steven Rostedt wrote:
> The show all regs sysrq uses the nmi function to do it. But this
> function expects preemption to be off, or funny things happen.
>
> Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
>
> Index: linux-2.6.21-rt9/drivers/char/sysrq.c
> ===
On Wed, 2007-06-20 at 16:57 +1000, Tony Breeds wrote:
> On Sat, Jun 16, 2007 at 08:51:23AM -0700, Daniel Walker wrote:
> > On Sat, 2007-06-16 at 10:36 +, Thomas Gleixner wrote:
> > > plain text document attachment
> > > (clocksource-add-settimeofday-hook.patch)
>
On Fri, 2007-06-22 at 00:00 -0400, Steven Rostedt wrote:
> plain text document attachment (tasklet-driver-hacks.patch)
> Update the DRM driver to use the new tasklet API, which does not rely
> on the tasklet implementation details.
>
> Signed-off-by: Steven Rostedt <[EMAIL PROTECTED]>
>
>
> Inde
On Fri, 2007-06-22 at 00:00 -0400, Steven Rostedt wrote:
> plain text document attachment (tasklets-to-workqueues.patch)
> This patch creates an alternative for drivers from using tasklets.
> It creates a "work_tasklet". When configured to use work_tasklets
> instead of tasklets, instead of creatin
On Fri, 2007-06-22 at 08:49 +0200, Thomas Gleixner wrote:
> On Thu, 2007-06-21 at 23:36 -0700, Daniel Walker wrote:
> > On Fri, 2007-06-22 at 00:00 -0400, Steven Rostedt wrote:
> > > plain text document attachment (tasklet-driver-hacks.patch)
> > > Update the DRM driver
On Fri, 2007-06-22 at 08:15 -0400, Steven Rostedt wrote:
> On Fri, 2007-06-22 at 00:08 -0700, Daniel Walker wrote:
>
> > > > No sense in having a patch just for this, may as well merge this with
> > > > patch 3 ..
> > >
> > > Wrong. patch 3 ad
On Fri, 2007-06-22 at 22:40 +0200, Ingo Molnar wrote:
>
> - tasklets have certain fairness limitations. (they are executed in
>softirq context and thus preempt everything, even if there is some
>potentially more important, high-priority task waiting to be
>executed.)
Since -rt has b
On Fri, 2007-06-22 at 15:09 -0700, [EMAIL PROTECTED] wrote:
> On Fri, 22 Jun 2007, Daniel Walker wrote:
>
> >
> > On Fri, 2007-06-22 at 22:40 +0200, Ingo Molnar wrote:
> >
> >>
> >> - tasklets have certain fairness limitations. (they are executed i
On Sat, 2007-06-23 at 00:38 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > > The two patches have two different objectives, even though they are
> > > related and currently on a 1 to 1 basis. The patches regardless,
> > >
On Sat, 2007-06-23 at 00:44 +0200, Ingo Molnar wrote:
> * Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > > remember, these changes have been in use in -rt for a while. there's
> > > reason to believe that they aren't going to cause drastic problems.
>
On Mon, 2007-06-11 at 21:45 +0200, Thomas Gleixner wrote:
> On Mon, 2007-06-11 at 20:36 +0100, Rui Nuno Capela wrote:
> > > I'm spinning -rt10 with a couple of fixes. Should be out sometimes
> > > tomorrow. If the problem persists, we need to dig deeper.
> > >
> >
> > Uhoh. I'm sorry to tell, but
On Mon, 2007-06-11 at 23:42 +0200, Thomas Gleixner wrote:
> On Mon, 2007-06-11 at 22:25 +0100, Rui Nuno Capela wrote:
> > Nope. It's a Fujitsu-Siemens Amilo Si 1520 -- Intel Core2 Duo [EMAIL
> > PROTECTED]
>
> Yeah, there are Dell ones which have similar or worse symptoms.
>
> > Works great with
On Sat, 2007-06-16 at 10:36 +, Thomas Gleixner wrote:
> plain text document attachment
> (clocksource-add-settimeofday-hook.patch)
> From: Tony Breeds <[EMAIL PROTECTED] >
>
> I'm working on a clocksource implementation for all powerpc platforms.
> some of these platforms needs to do a little
On Fri, 2007-07-06 at 10:34 -0400, Steven Rostedt wrote:
> thing is that in RT an IRQ thread might service a softirq if that
> softirq thread is of the same priority as the IRQ thread. The difference
> between an IRQ thread and a softirq thread is that the IRQ thread may
> migrate but the softirq
On Tue, 2007-07-03 at 17:16 -0700, Andrew Morton wrote:
> On Wed, 4 Jul 2007 02:14:42 +0200 (CEST) Jiri Kosina <[EMAIL PROTECTED]>
> wrote:
>
> > From: Jiri Kosina <[EMAIL PROTECTED]>
> >
> > Two trivial whitespace fixes in lockdep/spinlock code
> >
> > Cc: Ingo Molnar <[EMAIL PROTECTED]>
> > S
On Wed, 2007-07-11 at 20:58 -0400, Gregory Haskins wrote:
> Hi Ingo, Thomas, and the greater linux-rt community,
>
> I just wanted to let you guys know that our team has a port of the
> 21.5-rt20 patch for the 2.6.22 kernel available. It in no way should be
> construed as a substitute for
401 - 500 of 808 matches
Mail list logo
