From: Thomas Gleixner [EMAIL PROTECTED]
Reintroduce ktimers feature optimized away by the ktimers review
process: multiple hrtimer states to enable the running of hrtimers
without holding the cpu-base-lock.
(The optimized rbtree hack carried only 2 states worth of information
and we need 4
From: Ingo Molnar [EMAIL PROTECTED]
Enable dynamic ticks selection.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
---
arch/i386/Kconfig |2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6.20-rc4-mm1-bo/arch/i386/Kconfig
From: Thomas Gleixner [EMAIL PROTECTED]
Improve kernel/hrtimers.c locking: use a per-CPU base with a lock to
control locking of all clocks belonging to a CPU. This simplifies code
that needs to lock all clocks at once. This makes life easier for
high-res timers and dyntick.
No functional
From: Thomas Gleixner [EMAIL PROTECTED]
The NMI watchdog implementation assumes that the local APIC timer
interrupt is happening. This assumption is not longer true when high
resolution timers and dynamic ticks come into play, as they may switch
off the local APIC timer completely. Take the PIT
From: Thomas Gleixner [EMAIL PROTECTED]
The TSC needs to be verified against another clocksource. Instead of
using hardwired assumptions of available hardware, provide a generic
verification mechanism. The verification uses the best available
clocksource and handles the usability for high
From: Ingo Molnar [EMAIL PROTECTED]
Prepare i386 for dyntick: idle handler callbacks.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Cc: john stultz [EMAIL PROTECTED]
Cc: Roman Zippel [EMAIL PROTECTED]
Cc: Andi Kleen [EMAIL PROTECTED]
Signed-off
From: Thomas Gleixner [EMAIL PROTECTED]
From: Ingo Molnar [EMAIL PROTECTED]
Add functions to provide dynamic ticks and high resolution timers.
The code which keeps track of jiffies and handles the long idle
periods is shared between tick based and high resolution timer based
dynticks. The dyntick
From: Thomas Gleixner [EMAIL PROTECTED]
The local apic timer calibration has two problem cases:
1. The calibration is based on readout of the PIT/HPET timer to detect the
wrap of the periodic tick. It happens that a box gets stuck in the
calibration loop due to a PIT with a broken
safely select it as an timesource
for the highres timers subsystem.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/i386/kernel/tsc.c | 20
include/asm-i386/msr.h |3
From: Thomas Gleixner [EMAIL PROTECTED]
Architectures register their clock event devices, in the clock events
core. Users of the clockevents core can get clock event devices for
their use. The clockevents core code provides notification mechanisms
for various clock related management events
From: Thomas Gleixner [EMAIL PROTECTED]
From: Ingo Molnar [EMAIL PROTECTED]
The tick-management code is the first user of the clockevents layer.
It takes clock event devices from the clock events core and uses them
to provide the periodic tick.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED
From: Thomas Gleixner [EMAIL PROTECTED]
From: Ingo Molnar [EMAIL PROTECTED]
Add broadcast functionality, so per cpu clock event devices can be
registered as dummy devices or switched from/to broadcast on demand.
The broadcast function distributes the events via the broadcast
function of the clock
From: Andrew Morton [EMAIL PROTECTED]
Cc: Thomas Gleixner [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Dmitry Torokhov [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
drivers/input/touchscreen/ads7846.c | 11 ++-
1 file changed, 6 insertions(+), 5
From: Thomas Gleixner [EMAIL PROTECTED]
- hrtimers did not use the hrtimer_restart enum and relied on the implict
int representation. Fix the prototypes and the functions using the enums.
- Use seperate name spaces for the enumerations
- Convert hrtimer_restart macro to inline function
- Add
From: Thomas Gleixner [EMAIL PROTECTED]
Reintroduce ktimers feature optimized away by the ktimers review
process: remove the curr_timer pointer from the cpu-base and use the
hrtimer state.
No functional changes.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL
From: Thomas Gleixner [EMAIL PROTECTED]
apic.h does not get included on UP compiles. That way the
APICTIMER_STOPS_ON_C3 is not there and UP boxen have no support for
timer broadcasting. This was never noticed, because the lapic timer is
only used for profiling on UP.
Signed-off-by: Thomas
From: Thomas Gleixner [EMAIL PROTECTED]
Move the initial hrtimers.txt document to the new directory
Documentation/hrtimers
Add design notes for the high resolution timer and dynamic tick
functionality.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED
From: Thomas Gleixner [EMAIL PROTECTED]
The clocksource code allows direct updates of the rating
of a given clocksource now. Change TSC unstable tracking to
use this interface and remove the update callback.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL
From: Thomas Gleixner [EMAIL PROTECTED]
Provide funtions to:
- check, whether an interrupt can set the affinity
- pin the interrupt to a given cpu
Necessary for the ability to setup clocksources more flexible (e.g. use
the different HPET channels per CPU)
Signed-off-by: Thomas Gleixner [EMAIL
From: Ingo Molnar [EMAIL PROTECTED]
There are loads of fat functions hidden in jiffies.h. Uninline them. No
code changes.
[ export fix from Jeremy Fitzhardinge [EMAIL PROTECTED] ]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Andrew
of -20 is mistakenly converted to 'immediate timeout'.
(The new dyntick code also triggered this, that's how we noticed.)
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
kernel/time.c | 43
From: Ingo Molnar [EMAIL PROTECTED]
Prevent timeout overflow if timer ticks are behind jiffies (due to high
softirq load or due to dyntick), by limiting the valid timeout range to
MAX_LONG/2.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off
From: John Stultz [EMAIL PROTECTED]
Persistent clock support: do proper timekeeping across suspend/resume.
[ cleanup from Adrian Bunk [EMAIL PROTECTED] ]
Signed-off-by: John Stultz [EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED
From: John Stultz [EMAIL PROTECTED]
Persistent clock support: do proper timekeeping across suspend/resume, i386
arch support.
[ cleanup from Adrian Bunk [EMAIL PROTECTED] ]
Build-fixes-from: Andrew Morton [EMAIL PROTECTED]
Signed-off-by: John Stultz [EMAIL PROTECTED]
Signed-off-by: Thomas
From: Thomas Gleixner [EMAIL PROTECTED]
The delayed work code in arch/i386/kernel/tsc.c is an unused leftover of the
GTOD conversion. Remove it.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/i386/kernel/tsc.c | 40
From: Thomas Gleixner [EMAIL PROTECTED]
Enqueue clocksources in rating order to make selection of the
clocksource easier. Also check the match with an user override
at enqueue time.
Preparatory patch for the generic clocksource verification.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED
[EMAIL PROTECTED]
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
---
arch/i386/kernel/Makefile |2
arch/i386/kernel/smpboot.c| 178 ++--
arch/i386/kernel/tsc.c|4
arch/i386/kernel/tsc_sync.c |1
arch/x86_64/kernel/Makefile |2
From: Thomas Gleixner [EMAIL PROTECTED]
Using a flag filed allows to encode more than one information into
a variable. Preparatory patch for the generic clocksource verification.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/i386/kernel
From: Thomas Gleixner [EMAIL PROTECTED]
Fixup the is_contionous replacement by a flag field.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/arm/mach-imx/time.c |2 +-
arch/arm/mach-ixp4xx/common.c |2 +-
arch/arm/mach-netx
From: Thomas Gleixner [EMAIL PROTECTED]
Fixup the is_contionous replacement by a flag field.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.20
From: Thomas Gleixner [EMAIL PROTECTED]
Fixup the is_contionous replacement by a flag field.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/s390/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.20
From: Thomas Gleixner [EMAIL PROTECTED]
Fixup the is_contionous replacement by a flag field.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
---
arch/mips/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.20
From [EMAIL PROTECTED] Wed Dec 20 02:36:15 2006
Distangle the NTP update from HZ. This is necessary for dynamic tick
enabled kernels.
---
include/linux/timex.h |7 +++
kernel/hrtimer.c | 11 ---
kernel/time/ntp.c | 30 +++---
kernel/timer.c
On Wed, 2007-01-24 at 02:23 -0800, Daniel Walker wrote:
the 10th major iteration to his codebase. If you have cleanups to his
code then please work with Thomas to get your changes into his tree.
My code is for clocksouces/timekeeping which has been unrelated to HRT
up until recently. In
On Wed, 2007-01-24 at 03:00 +0100, Pavel Pisa wrote:
stays NULL after clock event registration. Interrupts
runs, but my code doesnot call any function. The notification
chain and clock events list seems to be filled correctly.
I have added
clockevent_imx.cpumask =
On Wed, 2007-01-24 at 12:23 +0100, Ingo Molnar wrote:
convert vmitime.c to the new clocksource flag.
Signed-off-by: Ingo Molnar [EMAIL PROTECTED]
Acked-by: Thomas Gleixner [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Wed, 2007-01-24 at 18:58 -0800, Linus Torvalds wrote:
It's been more than a week since -rc5, but I blame everybody (including
me) being away for Linux.conf.au and then me waiting for a few days
afterwards to let everybody sync up.
2.6.20-rc6-git (today) on a dual core laptop:
PM:
On Wed, 2007-01-24 at 18:58 -0800, Linus Torvalds wrote:
It's been more than a week since -rc5, but I blame everybody (including
me) being away for Linux.conf.au and then me waiting for a few days
afterwards to let everybody sync up.
Reverting commit 44ade178249fe53d055fd92113eaa271e06acddd
On Wed, 2007-01-24 at 18:58 -0800, Linus Torvalds wrote:
It's been more than a week since -rc5, but I blame everybody (including
me) being away for Linux.conf.au and then me waiting for a few days
afterwards to let everybody sync up.
ata_piix survives exactly one suspend resume cylce. After
On Sat, 2007-01-27 at 17:40 -0500, Jeff Garzik wrote:
During the second resume the ATA interrupt gets disabled due to an
unhandled interrupt.
This is 100% reproducible. So I can provide as much info as needed.
Is this a regression, or behavior that's always been present?
No, that's
On Sat, 2007-01-27 at 23:44 +0100, Thomas Gleixner wrote:
If its a regression, what changeset caused the problem?
Hey. I just discovered that crap. I'm going to bisect tomorrow. Bed time
here in good old Europe. :)
It seems to be there in 2.6.18 already, although it takes more
suspend
On Mon, 2007-01-29 at 12:02 +0100, Jiri Kosina wrote:
I guess that it's caused by some timer changes (added Thomas and Ingo to
CC), which confuse the softlockup detector sense of time?
Does the patch below fix this ?
tglx
Index: linux-2.6.20-rc6-mm/kernel/time/tick-common.c
On Mon, 2007-01-29 at 17:22 +0100, Karsten Wiese wrote:
Hi,
with dynticks and highres_timers enabled, cpufreq_ondemand makes mess here on
an AMD64 UP.
cpufreq_ondemand assumes that jiffies advance at exactly the same pace as the
sum of all kstat_cpu(cpu).cpustat.* members.
This isn't the
The softlockup watchdog needs to be touched after resume to avoid a
false positive.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Acked-by: Jiri Kosina [EMAIL PROTECTED]
Index: linux-2.6.20-rc6-mm/kernel/time/tick-common.c
On Mon, 2007-01-29 at 11:31 -0800, Stephen Hemminger wrote:
Does this fix it?
Don't know.
--- sky2-2.6.orig/drivers/net/sky2.c 2007-01-29 10:05:12.0 -0800
+++ sky2-2.6/drivers/net/sky2.c 2007-01-29 10:29:56.0 -0800
@@ -3675,6 +3675,12 @@
sky2_write32(hw,
On Mon, 2007-01-29 at 13:38 -0800, Stephen Hemminger wrote:
Sorry it was against the last patch I sent to Jeff for netdev.
Here is against 2.6.20-rc6
Still the same problem. The only difference of this patch to the
previous version is, that the unhandled interrupt message is gone.
As I said
On Mon, 2007-01-29 at 14:23 -0800, Stephen Hemminger wrote:
Still the same problem. The only difference of this patch to the
previous version is, that the unhandled interrupt message is gone.
As I said before:
Reverting commit 44ade178249fe53d055fd92113eaa271e06acddd, which added
On Mon, 2007-01-29 at 23:38 +0100, Frédéric Riss wrote:
I see the same symptoms on my Intel Mac Mini, and reverting the commit
also allows the driver to seemingly resume correctly.
However after coming out of sleep I need to reconfigure the network
interface. No need to rmmod/insmod, just
On Mon, 2007-01-29 at 23:50 +0100, Frédéric Riss wrote:
That's probably a userspace problem. Are you using DHCP ?
Yep DHCP. Is that a known issue? I never had to reconfigure with older
kernels.
Is dhclient running after resume ? What's the output of ifconfig (before
you do ifdown/up) ? Have
).
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Index: linux-2.6.20-rc6-mm/kernel/time/tick-sched.c
===
--- linux-2.6.20-rc6-mm.orig/kernel/time/tick-sched.c
+++ linux-2.6.20-rc6-mm/kernel/time/tick-sched.c
@@ -43,7 +43,7 @@ struct
On Tue, 2007-01-30 at 00:26 +0100, Frédéric Riss wrote:
Have you checked the syslog ?
Yes of course. Nothing interesting.
Just got the same issue on one of my test boxen. Different network card
though. The interface comes up fine, but DNS is not working. ifdown/up
resolves it.
/me keeps an
commmit 44ade178249fe53d055fd92113eaa271e06acddd breaks sane
MSI/ACPI/BIOS combinations. It's impossible to keep broken and sane
MSI/ACPI/BIOSes happy at the same time.
Revert the patch and disable MSI for sky2 when CONFIG_PM is enabled.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
diff
On Mon, 2007-01-29 at 15:50 -0800, Stephen Hemminger wrote:
The Sony VAIO BIOS resets to INTx on resume. This happens
after device resume, so device irq's get misrouted.
Err? My Sony VAIO does _NOT_ do that. It works fine without that.
It's just the sky2 hackery which fucked up things.
On Tue, 2007-01-30 at 01:22 +0100, Thomas Gleixner wrote:
On Mon, 2007-01-29 at 15:50 -0800, Stephen Hemminger wrote:
The Sony VAIO BIOS resets to INTx on resume. This happens
after device resume, so device irq's get misrouted.
Err? My Sony VAIO does _NOT_ do that. It works fine without
On Mon, 2007-01-29 at 16:21 -0800, Stephen Hemminger wrote:
The Sony VAIO BIOS resets to INTx on resume. This happens
after device resume, so device irq's get misrouted.
Err? My Sony VAIO does _NOT_ do that. It works fine without that.
It's just the sky2 hackery which fucked up
On Wed, 2007-01-31 at 09:02 -0800, Daniel Walker wrote:
well, this implementation is buggy in at least two ways:
firstly, it allows a circular verification dependency in highres+dyntick
mode between the jiffies and tsc clocksources.
In the current implementation, it's only happens if
On Wed, 2007-01-31 at 09:20 -0800, Daniel Walker wrote:
The purpose of clocksource_initcall is so the initcall can be increased
without changing all the individual clocksources .. So I have to
disconnect that from the acpi_pm because it can't tolerate it.
Each clocksource has to decide on its
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
clocksources are fundamentally fragile so we want to default to the
safest behavior. I.e.
On Wed, 2007-01-31 at 12:52 -0500, Jeff Garzik wrote:
Ingo Molnar wrote:
19:2413090 0 IO-APIC-fasteoi uhci_hcd:usb2, libata
Yep, that's a good candidate for such experiments :)
Happens to be the same thing, which causes a stale interrupt on the
second suspend/resume cycle.
On Wed, 2007-01-31 at 10:07 -0800, Daniel Walker wrote:
I'm assuming that programmers will test their code, and others will
review the code .. Catering to any other situation doesn't make sense to
me. On top of that those clocks are rare, and not desirable ..
So what are you arguing about
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 thought one of the changes
that you made was to have both 32k and mpu both registered ..
It is up to the clocksource
On Wed, 2007-01-31 at 17:54 -0600, Robert Hancock wrote:
I'm not sure if there's an inherent max ramdisk size limit, however I
should point out that in most cases, using a tmpfs or ramfs file system
is better than old-style ramdisks. Those filesystems return unused
memory to the kernel
On Wed, 2007-01-31 at 16:15 -0800, Daniel Walker wrote:
clocksource_initcall is simply superfluid.
My position has always been that clocksources should be registered as
early as possible .. The fs_initcall() usage is a compromise stemming
from early resistance that John, and you gave to
On Wed, 2007-01-31 at 18:14 -0600, Robert Hancock wrote:
So either #1 or #2 should have failed in the first place. Failing in #3
is definitely a BUG in #1 or #2.
How does your advise help to fix that BUG ? Ignoring it by using
something else ?
Yes, there is likely a bug here of some
. jiffies are restarting
from the same point as well.
This solves the resume waittime observed by Karsten Wiese.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Index: linux-2.6.20-rc6-mm/kernel/timer.c
===
--- linux-2.6.20-rc6-mm.orig
On Mon, 2005-08-01 at 17:48 +0200, Simon Sudler wrote:
if (nroots 0 || nroots = (1symsize) || nroots 8)
return NULL;
After removing of the nroots 8 my code was working fine...
perhaps someone was to carful to avoid a errors with the kmalloc
function in
The sanity check for no_irq_chip in __set_irq_hander() is unconditional
on both install and uninstall of an handler. This triggers false
warnings and replaces no_irq_chip by dummy_irq_chip in the uninstall
case.
Check only, when a real handler is installed.
Signed-off-by: Thomas Gleixner [EMAIL
On Thu, 2006-12-14 at 22:59 -0800, Tilman Schmidt wrote:
[c021d049] rb_insert_color+0x55/0xbe
[c012d15b] enqueue_hrtimer+0x10a/0x116
[c012d9b4] hrtimer_start+0x78/0x93
[c0123453] get_signal_to_deliver+0xf3/0x74e
[c01026ee] do_notify_resume+0x93/0x655
[c0102ef5] work_notifysig+0x13/0x1a
Subject: [patch] high-res timers: core, do itimer rearming in process context,
fix2
From: Thomas Gleixner [EMAIL PROTECTED]
The rearming code in signal.c has to read the time and can not rely on
the timer-base-softirq time anymore, as it is not longer running in
softirq context.
Ensure
On Fri, 2007-01-12 at 15:25 -0800, Dor Laor wrote:
This is great news for PV guests.
Never-the-less we still need to improve our full virtualized guest
support.
Full virtualized guests, which have their own dyntick support, are fine
as long as we provide local apic emulation for them.
If a
Andrew,
the following series removes the deprecated SA_xx interrupt flags as scheduled.
There are some new users of those flags since the initial cleanup patch. The
fixup of those users is split into two parts:
1) mainline fixups
2) -mm fixups
tglx
--
-
To unsubscribe from this list:
The name space cleanup of the interrupt request flags (SA_xxx - IRQF_xxx)
left a 6 month grace period for the old deprecated flags. Remove them.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Index: linux-2.6.20-rc3-mm1/Documentation/feature-removal-schedule.txt
The obsolete SA_xxx interrupt flags have been used despite the scheduled
removal. Fixup the remaining users.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Index: linux-2.6.20-rc5/kernel/irq/manage.c
===
--- linux-2.6.20-rc5.orig
The obsolete SA_xxx interrupt flags have been used despite the scheduled
removal. Fixup the remaining users in -mm.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Index: linux-2.6.20-rc4-mm1/arch/i386/kernel/vmitime.c
On Thu, 2007-01-11 at 22:26 -0800, Andrew Morton wrote:
- Merged the filesystem AIO patches.
Hotfixes alreday applied.
BUG: at
/home/tglx/work/kernel/vanilla/linux-2.6.20-rc4-mm1/arch/i386/mm/highmem.c:60
kmap_atomic()
[c0105fba] show_trace_log_lvl+0x1a/0x2f
[c01065ff] show_trace+0x12/0x14
On Sun, 2007-01-14 at 10:48 +0100, Thomas Gleixner wrote:
ata_scsi_rbuf_get requests KM_IRQ0 type memory and calls kmap_atomic
with interrupts enabled.
Boot proceeds, but gets stuck hard at:
Remounting root filesystem in read-write mode:
No SysRq-T, nothing.
The above BUG seems
On Sun, 2007-01-14 at 13:42 +0100, Ingo Molnar wrote:
i have tested your patch-queue ontop of rc4-mm1 (trivial reject fixups
are below), it builds and boots fine.
Acked-by: Ingo Molnar [EMAIL PROTECTED]
You tested my yesterday queue against rc2-mm1. The patches in the mail
are against
On Sun, 2007-01-14 at 11:46 +0100, Thomas Gleixner wrote:
Boot proceeds, but gets stuck hard at:
Remounting root filesystem in read-write mode:
No SysRq-T, nothing.
The above BUG seems unrelated to that. Investigating further.
Bisect identified: git-block.patch
Does only happen
On Mon, 2007-01-15 at 09:05 +1100, Jens Axboe wrote:
raid seems to have severe problems with the plugging change. I'll try
and find Neil and have a chat with him, hopefully we can work it out.
Some hints:
mount(1899): WRITE block 16424 on md3
call md_write_start
md3_raid1(438): WRITE block
On Mon, 2007-01-15 at 08:17 +0100, Ingo Molnar wrote:
Debug plan:
- revert md-* patches
- binary search
Does someone have a better idea?
Thomas saw something similar yesterday and he the partial results that
git.block (between rc2-mm1 and rc4-mm1) breaks certain disk drivers or
On Mon, 2007-01-15 at 09:08 +0100, Thomas Gleixner wrote:
Thomas saw something similar yesterday and he the partial results that
git.block (between rc2-mm1 and rc4-mm1) breaks certain disk drivers or
filesystems drivers. For me it worked fine, so it must be only on some
combinations
On Tue, 2007-01-16 at 11:41 +1100, Jens Axboe wrote:
AFAICS this is intentional to avoid checks all over the place, but the
underflow check is missing. All we need to do is make sure, that in case
of ioc-plugged == 0 we return early and bug, if there is either a queue
plugged in or the
On Wed, 2007-01-17 at 16:25 -0800, Daniel Walker wrote:
The patch reworks do_futex, and futex_wait* so a NULL pointer in the timeout
position is infinite, and anything else is evaluated as a real timeout.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
Ack.
tglx
-
To unsubscribe
On Fri, 2007-01-19 at 20:13 +0100, Guennadi Liakhovetski wrote:
+static u32 clockevent_mode = 0;
+
+static void pxa_set_next_event(unsigned long evt,
+ struct clock_event_device *unused)
+{
+ OSMR0 = OSCR + evt;
+}
This doesn't work for me in various
On Sat, 2007-01-20 at 17:08 +0100, Guennadi Liakhovetski wrote:
static int hpet_next_event(unsigned long delta,
struct clock_event_device *evt)
{
unsigned long cnt;
cnt = hpet_readl(HPET_COUNTER);
cnt += delta;
On Tue, 2006-12-05 at 22:44 -0800, [EMAIL PROTECTED] wrote:
It works, the warning disappeared and irqbalance still runs well.
Signed-off-by: Hidetoshi Seto [EMAIL PROTECTED]
Cc: Arjan van de Ven [EMAIL PROTECTED]
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Thomas Gleixner [EMAIL PROTECTED
On Tue, 2006-12-05 at 20:30 -0800, Andrew Morton wrote:
I don't have a clue which review comments remain unaddressed - do you recall?
I never saw an item-by-item accounting of my own (extensive) review
comments, actually. And then an avalanche of new stuff got sent and I
didn't have time
On Tue, 2006-12-12 at 08:46 -0800, Daniel Walker wrote:
What is this accomplishing? My TSC gets marked unstable, and it's not
unstable, in addition I have HRT off .. The else clause above just
doesn't seem right ..
This was a mismerge. It's fixed by now.
Thanks,
tglx
-
To
On Wed, 2006-12-13 at 12:58 -0800, Linus Torvalds wrote:
In other words, I'd like to see code that uses this that is actually
_better_ than an in-kernel driver in some way.
For USB, the user-mode thing made sense. You have tons of random devices,
and the abstraction level is higher to
On Thu, 2006-12-14 at 09:14 +1100, Benjamin Herrenschmidt wrote:
the edge flow is easy. the level one is:
- IRQ happens
- kernel handler masks it and queue a msg for userland
- later on, userland gets the message, talks to the device,
(MMAP'ed mmio, acks the interrupt on the device
On Thu, 2006-12-14 at 09:14 +1100, Benjamin Herrenschmidt wrote:
Oh, it works well enough for non shared iqs if you are really anal about
It works well for shared irqs. Thats the whole reason why you need an in
kernel part.
tglx
-
To unsubscribe from this list: send the line
On Thu, 2006-12-14 at 09:39 +1100, Benjamin Herrenschmidt wrote:
No need for an ioctl. Neither for edge nor for level irqs.
Wait wait wait... your scenario implies that the kernel has knowledge of
the chip to mask the irq in the chip in the first place.
If that is the case, then you have
On Thu, 2006-12-14 at 09:45 +1100, Benjamin Herrenschmidt wrote:
On Wed, 2006-12-13 at 23:40 +0100, Thomas Gleixner wrote:
On Thu, 2006-12-14 at 09:14 +1100, Benjamin Herrenschmidt wrote:
Oh, it works well enough for non shared iqs if you are really anal about
It works well for shared
On Wed, 2006-12-13 at 23:56 +, Alan wrote:
On Wed, 13 Dec 2006 23:30:55 +0100
Thomas Gleixner [EMAIL PROTECTED] wrote:
- IRQ happens
- kernel handler runs and masks the chip irq, which removes the IRQ
request
IRQ is shared with the disk driver, box dead.
Err ?
IRQ happens
IRQ
On Thu, 2006-12-14 at 10:52 +, Alan wrote:
Might be kind of hairy given uio_read() doesn't even return from the
kernel.
We probably talk about different code here, right ? The one, I'm looking
at returns on each interrupt event.
tglx
-
To unsubscribe from this list: send the
On Thu, 2006-12-14 at 09:26 -0800, Linus Torvalds wrote:
On Thu, 14 Dec 2006, Jan Engelhardt wrote:
I don't get you. The rtc module does something similar (RTC generates
interrupts and notifies userspace about it)
The RTC module knows how to shut the interrupt up.
The kernel part of
Linus,
On Thu, 2006-12-14 at 14:59 -0800, Linus Torvalds wrote:
The kernel part of the UIO driver also knows how to shut the interrupt
up, so where is the difference ?
Thomas, you've been discussing some totally different and private
Thomas-only thread than everybody else in this thread
On Fri, 2006-11-17 at 10:11 +0100, John wrote:
value specified by the it_value member of value. If the specified time
has already passed, the function shall succeed and the expiration
notification shall be made.
That's exactly what the implementation does:
The functions succeeds (return
On Sat, 2006-12-02 at 14:05 +, Al Viro wrote:
On Sat, Dec 02, 2006 at 01:59:30PM +0100, Thomas Gleixner wrote:
On Fri, 2006-12-01 at 17:21 +, Al Viro wrote:
Now, there's another question: how do we get there? Or, at least, from
current void (*)(unsigned long) to void (*)(void
On Fri, 2006-12-01 at 17:21 +, Al Viro wrote:
Now, there's another question: how do we get there? Or, at least, from
current void (*)(unsigned long) to void (*)(void *)...
I think the real solution should be
void (*function)(struct timer_list *timer);
and hand the timer itself
1101 - 1200 of 29423 matches
Mail list logo
