On Mon, 22 Oct 2007, Adrian Bunk wrote:
It seems commit 09cadedbdc01f1a4bea1f427d4fb4642eaa19da9 was incomplete
due to a clash with the x86 architecture merge.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Applied, thanks. Will go Linus wards with our next pull request.
tglx
-
To
On Mon, 22 Oct 2007, Arnd Bergmann wrote:
On Monday 22 October 2007, Andrew Morton wrote:
It's almost always a bug to do spin_lock_irq() when local interrupts are
disabled. Â However iirc when we've tried to add runtime debugging to catch
that, it triggered false-positives which made the
On Tue, 23 Oct 2007, Rafael J. Wysocki wrote:
On Monday, 22 October 2007 16:11, Mark Lord wrote:
Rafael,
What happens to the jiffies variable on resume from RAM, and from DISK?
Do we restore it to the value it had at suspend,
or just leave it be with whatever?
The answer has to
lapic_shutdown for x86_64
x86: add safe_smp_processor_id for x86_64
x86: unify crash_32/64.c
Nick Piggin (1):
x86: lock bitops
Rafael J. Wysocki (1):
x86: Save registers in saved_context during suspend and hibernation
Thomas Gleixner (19):
x86: Add BITS to allow simple
On Wed, 24 Oct 2007, Chuck Ebbert wrote:
On 10/24/2007 05:26 PM, Mikhail Kshevetskiy wrote:
I fill something wrong here.
Is it possible to reduce the amount of timer interrupts?
Is it possible to force enable C1,C2 and C3 states when c1e disabled?
How are you disabling C1E?
On Fri, 8 Feb 2008, Venki Pallipadi wrote:
On Fri, Feb 08, 2008 at 11:28:48AM +0100, Andi Kleen wrote:
- set_cpus_allowed(current, tmp);
+ smp_mb();
+ /* kick all the CPUs so that they exit out of pm_idle */
+ smp_call_function(do_nothing, NULL, 0, 0);
I think the last
On Thu, 7 Feb 2008, Chris Holvenstot wrote:
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
Hope you feel better again !
I suspect you often feel the same way after
On Fri, 8 Feb 2008, Andi Kleen wrote:
Not that it matters much, see comment in the code.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
---
arch/x86/kernel/rtc.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
Index: linux/arch/x86/kernel/rtc.c
On Sat, 9 Feb 2008, Alexey Dobriyan wrote:
I enabled pretty much all debugging on
2.6.24-0cf975e16927fd70f34cee20d3856246c13bb4c8 and CPA code
continuosly spams dmesg like this:
[ 24.10] CPA 81008000 no pte level 0
[ 24.52] PGD 8063 PUD 0
[ 24.52] CPA
On Sat, 9 Feb 2008, Chris Holvenstot wrote:
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks
On Fri, 8 Feb 2008, Andi Kleen wrote:
There is a big difference between NX and RO. NX absolutely has to be cleared
or the kernel will fail while RO just can be set, but does not need to.
And for a large page area not setting NX if there is a area below
it that needs it is essential, while
On Sat, 9 Feb 2008, Andi Kleen wrote:
On Sat, Feb 09, 2008 at 03:56:02PM +0100, Thomas Gleixner wrote:
On Fri, 8 Feb 2008, Andi Kleen wrote:
There is a big difference between NX and RO. NX absolutely has to be
cleared
or the kernel will fail while RO just can be set, but does not need
On Fri, 8 Feb 2008, Andi Kleen wrote:
Only force RO in the advisory protection checks when all pages in the
range are RO. Previously it would trigger when any page in the range
was ro.
I believe this will make try_preserve_large_page much safer to use.
It might be quite useful to know
On Sat, 9 Feb 2008, Andi Kleen wrote:
Note the behaviour for pageattr and thus DEBUG_RODATA / debugging
sitations where you don't care about your TLB this
does not change, this makes only a difference for the initial init_32
direct mapping setup.
Your patches do change the
On Sat, 9 Feb 2008, Andi Kleen wrote:
On Saturday 09 February 2008 16:38:35 Thomas Gleixner wrote:
On Fri, 8 Feb 2008, Andi Kleen wrote:
Only force RO in the advisory protection checks when all pages in the
range are RO. Previously it would trigger when any page in the range
/power
x86 PM: consolidate suspend and hibernation code
x86 PM: update stale comments
Thomas Gleixner (6):
x86: avoid unused variable warning in mm/init_64.c
x86: DEBUG_PAGEALLOC: enable after mem_init()
x86: introduce page pool in cpa
x86: cpa, use page pool
On Sun, 10 Feb 2008, Linus Torvalds wrote:
On Sat, 9 Feb 2008, Randy Dunlap wrote:
So Thomas, don't do this. I don't like it. The same way I didn't like
seeing Ingo trying to mix in a kgdb pull into his x86 pull. Keep these
things separate - git is *really* good at having multiple branches
Linus,
please pull hrtimer and ntp bugfixes from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt.git master
Following problems are addressed by these patches:
- ntp: fix incorrect drift compensation
- hrtimer: fix a stupid restart handling thinko, which keeps a
On Sun, 10 Feb 2008, Andi Kleen wrote:
Thomas Gleixner [EMAIL PROTECTED] writes:
2) I care about RO as much as I care about the NX correctness. That's
the same logic and the same problem. If we have overlapping regions,
then we need to split large pages. Otherwise both protections
pageattr-test.c contains a noisy debug printk that people reported.
The condition under which it prints (randomly tapping into a mem_map[]
hole and not being able to c_p_a() there) is valid behavior and not
interesting to report.
Remove it.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Acked
for noting that it is still unfixed.
cu
Adrian
[1] http://lkml.org/lkml/2007/8/1/474
Subject: futex: disable PI/robust on archs w/o valid implementation
From: Thomas Gleixner [EMAIL PROTECTED]
We have to disable the complete PI/robust functionality for those
archs, which do
On Mon, 11 Feb 2008, Andi Kleen wrote:
The AMD64 pci-gart code sets pages not present to prevent
cache coherency problems. When doing this it is safer to flush the
caches too so that there are no cache lines left over from when
the pages were still mapped.
So consider clearing of the
On Mon, 11 Feb 2008, Andi Kleen wrote:
Not much left from the original code and I don't want my name
on it because there is code in there I disagree with.
I don't think any of the Ben inspired code is left in there
either, but I left his name in for now.
Signed-off-by: Andi Kleen
On Mon, 11 Feb 2008, Andi Kleen wrote:
Use correct page sizes and masks for GB pages in try_preserve_large_page()
This prevents a boot hang on a GB capable system with CONFIG_DIRECT_GBPAGES
enabled.
Doh, yes. Applied.
Thanks,
tglx
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
On Sat, 9 Feb 2008, Andi Kleen wrote:
Minor logic fix. The century change was previously always BCD,
even when the CMOS data would report itself not being BCD.
I checked that whole rtc / BCD logic again. We always set RTC_ALWAYS_BCD:
#ifndef RTC_PORT
#define RTC_PORT(x)(0x70 + (x))
On Tue, 12 Feb 2008, Andi Kleen wrote:
On Tuesday 12 February 2008 21:04:06 Thomas Gleixner wrote:
And you just copied the real bug in that logic as well:
set_memory_uc(md-virt_addr, size);
Oops you're right. I wanted to fix that, but didn't. Ok I'll put up
my brown
On Mon, 11 Feb 2008, Andi Kleen wrote:
Even on 32bit 2MB pages can map more memory than is in the true
max_low_pfn if end_pfn is not highmem and not aligned to 2MB.
Add a end_pfn_map similar to x86-64 that accounts for this
fact. This is important for code that really needs to know about
On Mon, 11 Feb 2008, Andi Kleen wrote:
From code review the EFI memory map handling has a couple of problems:
- The test for _WB memory was reversed so it would set cache able memory
to uncached
- It would always set a wrong uninitialized zero address to uncached
(so I suspect it always
On Mon, 11 Feb 2008, Andi Kleen wrote:
So the warning comes a bit late :)
I suspect if this was wrong before it would not have been noticed
because user space hwclock would work around it.
And how exaclty does it work around ? By setting the binary cmos clock
with BCD values ?
The
On Tue, 12 Feb 2008, Andi Kleen wrote:
There would be several possible ways to fix this:
- Simply don't set the NX bit in the original ioremap and drop
set_memory_x and add a ioremap_exec(). That would be my preferred solution,
but unfortunately has been dismissed before
- Drop all __pas and
On Tue, 12 Feb 2008, Kevin Winchester wrote:
Kevin Winchester wrote:
CC arch/x86/mm/pageattr.o
arch/x86/mm/pageattr.c: In function ‘change_page_attr_set_clr’:
arch/x86/mm/pageattr.c:778: error: incompatible type for argument 1 of
‘cpa_check_alias’
make[1]: ***
On Tue, 12 Feb 2008, Andi Kleen wrote:
@@ -36,7 +36,7 @@
#define max_pfn_mapped end_pfn_map
#else
#include asm/page_32.h
-#define max_pfn_mapped max_low_pfn
+#define max_pfn_mapped end_pfn_map
We can nuke either max_pfn_mapped or end_pfn_map
On Tue, 12 Feb 2008, Andrew Morton wrote:
On Sun, 10 Feb 2008 14:40:21 +0100 Frans Pop [EMAIL PROTECTED] wrote:
the hrtimer code is preparing an invalid ktime_t. Note that
clockevents_program_event() actually fails when this happens - I am
surprised that this is not causing observeable
On Wed, 13 Feb 2008, Frans Pop wrote:
On Wednesday 13 February 2008, Thomas Gleixner wrote:
On Tue, 12 Feb 2008, Andrew Morton wrote:
On Sun, 10 Feb 2008 14:40:21 +0100 Frans Pop [EMAIL PROTECTED] wrote:
the hrtimer code is preparing an invalid ktime_t. Note
On Wed, 13 Feb 2008, Frans Pop wrote:
On Wednesday 13 February 2008, Thomas Gleixner wrote:
can you please apply the following patch ? I really should have
thought about that, when I fixed the above one.
I still get the bug with this patch. At least I'm now certain it happens
during
On Wed, 13 Feb 2008, Rafael J. Wysocki wrote:
Hi Thomas,
On Thursday, 7 of February 2008, Thomas Gleixner wrote:
current mainline triggers:
Has the issue been fixed in the meantime?
Nope.
Just for reference: http://lkml.org/lkml/2007/1/14/38 looks
frighteningly similar.
Thanks
On Thu, 14 Feb 2008, Greg KH wrote:
On Thu, Feb 14, 2008 at 10:19:23PM +0100, Thomas Gleixner wrote:
Linus,
please pull hrtimer fixes from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt.git
master
The first patch fixes an overflow problem, which
() in clockevents_program_event().
The second patch prevents a false positive of the same WARN_ON().
Fixes are confirmed to solve http://lkml.org/lkml/2008/2/10/137
Thanks,
tglx
---
Thomas Gleixner (2):
hrtimer: check relative timeouts for overflow
hrtimer: catch expired
On Thu, 14 Feb 2008, Greg KH wrote:
On Thu, Feb 14, 2008 at 10:37:49PM +0100, Thomas Gleixner wrote:
On Thu, 14 Feb 2008, Greg KH wrote:
On Thu, Feb 14, 2008 at 10:19:23PM +0100, Thomas Gleixner wrote:
Linus,
please pull hrtimer fixes from:
ssh
On Thu, 14 Feb 2008, Andrew Morton wrote:
This patch is intended for easy backporting and needs to be cleaned up
further for current mainline.
So...
I queued up this version with a cc to stable under the assumption that this
is the patch which should be applied to 2.6.x.y, but this
queues before the filesystem.
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Acked-by: Ingo Molnar [EMAIL PROTECTED]
---
kernel/futex.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Index: linux-2.6/kernel/futex.c
and the PI/robust features are enabled.
The relevant syscalls return -ENOSYS and the robust list exit code is
blocked, when the detection fails.
Fixes http://lkml.org/lkml/2008/2/11/149
Originally reported by: Lennart Buytenhek
Signed-off-by: Thomas Gleixner [EMAIL PROTECTED]
Acked-by: Ingo Molnar
On Mon, 29 Oct 2012, Tvrtko Ursulin wrote:
On 29/10/12 20:14, Tvrtko Ursulin wrote:
Unless RT patchset is the culprit. Hm.. that would be unexpected, but I
guess it is worth a shot. I'll let you know what happens without -rt.
Ha, this is exciting, vanilla 3.6.4 works, with -rt10 patch it
On Mon, 29 Oct 2012, Thomas Gleixner wrote:
Dear RT Folks,
I'm pleased to announce the 3.6.4-rt10 release. This is just an update
to 3.6.4 with no RT related changes
FYI, please disable SLUB and switch back to SLAB. Seems I took a bit
too naive approach of making it suitable for RT.
Thanks
On Tue, 30 Oct 2012, Christoph Lameter wrote:
On Sat, 27 Oct 2012, Thomas Gleixner wrote:
Correct this by extending the arguments of unfreeze_partials with the
target cpu number and use per_cpu_ptr instead of this_cpu_ptr.
Passing the kmem_cache_cpu pointer instead simplifies this a bit
On Tue, 30 Oct 2012, Milan Broz wrote:
Fix crypto api for 3.6.4-rt10 (broken only in realtime patchset)
In peterz-srcu-crypto-chain.patch the blocking notifier is changed
to srcu notifier and added initialization to module init fucntion.
Later, in
On Tue, 30 Oct 2012, Peter LaDow wrote:
Anyway, based on earlier discussion, is there any reason not to use a
lock (presuming any solution properly takes into account possible
recursion)? I understand that the mainline is protected, but perhaps
in the RT version we can use seqlock (and
Dear RT Folks,
I'm pleased to announce the 3.6.4-rt11 release.
Changes since 3.6.3-rt10:
* Crypto wreckage fix (Milan Broz)
Another proof why copy and paste should be forbidden, but if that
would happen most of us would be serving time.
* Another attempt to tame SLUB
My
On Wed, 31 Oct 2012, Paul Gortmaker wrote:
[[ANNOUNCE] 3.6.4-rt11] On 31/10/2012 (Wed 02:19) Thomas Gleixner wrote:
Dear RT Folks,
I'm pleased to announce the 3.6.4-rt11 release.
The rt11 content is present on master in the 3.6-rt patch repo:
http://git.kernel.org/?p=linux/kernel
Dear RT Folks,
I'm pleased to announce the 3.6.5-rt14 release. 3.6.4-rt12 is an
intermediate release with a few changes. 3.6.5-rt13 is an update to
3.6.5 and 3.6.5-rt14 has a fix for my stupidity to release from the
wrong tree missing a fix for x86-32.
Changes since 3.6.3-rt11:
* Fix the
On Wed, 31 Oct 2012, Peter LaDow wrote:
On Tue, Oct 30, 2012 at 5:33 PM, Steven Rostedt rost...@goodmis.org wrote:
From: Thomas Gleixner t...@linutronix.de
The netfilter code relies only on the implicit semantics of
local_bh_disable() for serializing wt_write_recseq sections. RT breaks
On Thu, 1 Nov 2012, Liu, Chuansheng wrote:
From: Oliver Neukum [mailto:oneu...@suse.de]
On Thursday 01 November 2012 00:20:55 Chuansheng Liu wrote:
When do code reviewing, found no special requirement to
use spin_lock_irqsave/spin_unlock_irqrestore, because
alarmtimer_get_rtcdev() is
On Thu, 1 Nov 2012, Chuansheng Liu wrote:
Some posix clock interface directly use the variable rtcdev,
cleanup it here by alarmtimer_get_rtcdev().
Signed-off-by: liu chuansheng chuansheng@intel.com
---
kernel/time/alarmtimer.c | 13 ++---
1 files changed, 6 insertions(+),
On Thu, 1 Nov 2012, Peter LaDow wrote:
On Thu, Nov 1, 2012 at 2:26 PM, Thomas Gleixner t...@linutronix.de wrote:
Cough. You are missing a boat load of crucial fixes. There is a damned
good reason why 3.0.stable got 12 updates and the -rt version 14.
I don't doubt there are. But we've
On Fri, 2 Nov 2012, Steven Rostedt wrote:
On Fri, 2012-11-02 at 22:24 +0900, anish kumar wrote:
From: anish kumar anish198519851...@gmail.com
As no one is using the return value of irq_work_queue function
it is better to just make it void.
Acked-by: Steven Rostedt rost...@goodmis.org
Dear RT Folks,
I'm pleased to announce the 3.6.5-rt15 brown paper bag release.
Changes since 3.6.5-rt14:
* Fix typos and other stupidities^Wcrimes committed by an
overworked and tired RT maintainer (courtesy Paul Gortmaker)
The embarrasing delta patch against 3.6.5-rt14 is appended
Dear RT Folks,
I'm pleased to announce the 3.6.2-rt4 release. rt4 is just an update
to 3.6.2. The not announced 3.6.1-rt3 is an intermediate release with
a single change.
Changes since 3.6.1-rt2:
* Remove the softirq noise printk
The delta patch against 3.6.1-rt2 is appended below and
B1;2601;0cOn Tue, 23 Oct 2012, Stanislav Kinsbursky wrote:
Patch replaces global idr with global hash table for posix timers and
makes timer ids unique not globally, but per process. Next free timer id is
type of integer and stored on signal struct (posix_timer_id). If free timer id
reaches
Darren, Siddhesh,
On Tue, 23 Oct 2012, Darren Hart wrote:
Hi Siddesh,
Thanks for the patch and your work to isolate it in the glibc bug 14076.
On 10/21/2012 08:20 PM, Siddhesh Poyarekar wrote:
In futex_lock_pi_atomic, we consider that if the value in the futex
variable is 0 with
On Tue, 23 Oct 2012, Al Viro wrote:
On Tue, Oct 23, 2012 at 01:30:26PM -0400, Chris Metcalf wrote:
I fetched the series from your arch-tile branch and built it, and it works
fine. It looks good from my inspection:
Acked-by: Chris Metcalf cmetc...@tilera.com
Thanks; Acked-by
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt6 release. rt6 is just an update
to 3.6.3. The not announced 3.6.2-rt5 is an intermediate release with
a single change.
Changes since 3.6.2-rt4:
* Make the early printk changes work (hopefully) everywhere
The new patch queue also
On Tue, 23 Oct 2012, Jeff King wrote:
On Tue, Oct 23, 2012 at 10:47:28PM +0200, Thomas Gleixner wrote:
I agree that this is a common issue. Acked-by/Reviewed-by mails come
in after the fact that the patch has been committed to an immutable
(i.e no-rebase mode) branch or if the change
On Tue, 23 Oct 2012, Eric Dumazet wrote:
On Tue, 2012-10-23 at 11:40 +0400, Stanislav Kinsbursky wrote:
This patch is required CRIU project (www.criu.org).
To migrate processes with posix timers we have to make sure, that we can
restore posix timer with proper id.
Currently, this is not
On Tue, 23 Oct 2012, Eric Dumazet wrote:
On Tue, 2012-10-23 at 23:47 +0200, Thomas Gleixner wrote:
Not so good to me.
Signed-off-by: Eric Dumazet eduma...@google.com
And that should be either an Acked-by or a Reviewed-by. You can't sign
off on patches which have not been
On Tue, 23 Oct 2012, Kevin Hilman wrote:
Russell King - ARM Linux li...@arm.linux.org.uk writes:
On Tue, Oct 16, 2012 at 03:07:49PM -0700, Kevin Hilman wrote:
From: Thomas Gleixner t...@linutronix.de
Attempts to retrigger nested threaded IRQs currently fail because they
have
On Sun, 21 Oct 2012, anish kumar wrote:
ping...
Oh well.
On Sat, 2012-10-13 at 00:32 +0900, anish kumar wrote:?
Hello tglx,
I just found the below inconsistency while going through the code.
kernel/irq/manage.c
if (new-flags IRQF_ONESHOT) {
/*
*
On Wed, 24 Oct 2012, Siddhesh Poyarekar wrote:
Now there is a different solution to that problem. Do not look at the
user space value at all and enforce a lookup of possibly available
pi_state. If pi_state can be found, then the new incoming locker T3
blocks on that pi_state and
Dear RT Folks,
I'm pleased to announce the 3.6.1-rt1 release.
This is a pretty straight forward move from the 3.4-rt series which
includes a few significant updates which need to be backported to the
3.x-rt stable series:
* Make interrupt randomness work again on RT. Based on the 3.x.y
On Tue, 9 Oct 2012, Steven Rostedt wrote:
On Tue, 2012-10-09 at 15:46 +0200, Thomas Gleixner wrote:
So instead of splitting the softirq threads I split the softirq
locks so different softirqs can be handled seperately. If a
softirq is raised in the context of a thread
either need to replace the call to set_irq_flags with something
else or export that function. This patch does the latter.
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: Magnus Damm d...@opensource.se
Cc: Linus Walleij linus.wall...@linaro.org
Cc: Rafael J. Wysocki r...@sisk.pl
Cc: Thomas
On Tue, 9 Oct 2012, Steven Rostedt wrote:
On Tue, 2012-10-09 at 18:19 +0200, Thomas Gleixner wrote:
I've started looking at playing with the NAPI code again, and trying to
see if I can add an ENAPI interface (Even Newer API), where the driver
uses its own interrupt thread
On Tue, 9 Oct 2012, Steven Rostedt wrote:
On Tue, 2012-10-09 at 15:46 +0200, Thomas Gleixner wrote:
The RT patch against 3.6.1 can be found here:
http://www.kernel.org/pub/linux/kernel/projects/rt/3.6/patch-3.6.1-rt1.patch.xz
The split quilt queue is available
On Wed, 5 Sep 2012, Steven Rostedt wrote:
On Wed, 2012-09-05 at 18:07 -0500, Sankara Muthukrishnan wrote:
Hi there,
This also affects mainline. Please Cc LKML (as I did).
As irq_thread_check_affinity is called inside the while loop in the
IRQ thread, the core affinity is set only
On Tue, 9 Oct 2012, Steven Rostedt wrote:
On Tue, 2012-10-09 at 20:21 -0400, Steven Rostedt wrote:
0007-stomp-machine-deal-clever-with-stopper-lock.patch
With this one, things have changed quite a bit. I'll take a deeper look
at what you did and figure out how this applies to
Linus,
please pull the latest timers-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-for-linus
Thanks,
tglx
--
Arnd Bergmann (1):
time/jiffies: bring back unconditional LATCH definition
Dan Carpenter (1):
On Fri, 12 Oct 2012, Thomas Gleixner wrote:
Linus,
please pull the latest timers-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-core-for-linus
Forgot to add the short description:
* Bug fixes (one for a long standing dead loop
On Fri, 12 Oct 2012, Chuansheng Liu wrote:
In our system, there is one edge interrupt, and we want it to be
irq thread with IRQS_ONESHOT, and found in handle_edge_irq(),
even with IRQS_ONESHOT, the irq is still unmasked without care of
flag IRQS_ONESHOT.
It causes IRQS_ONESHOT can not
On Fri, 12 Oct 2012, Liu, Chuansheng wrote:
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: Friday, October 12, 2012 8:32 PM
To: Liu, Chuansheng
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: for edge interrupt IRQS_ONESHOT support
On Fri, 12 Oct 2012, Liu, Chuansheng wrote:
-Original Message-
From: Thomas Gleixner [mailto:t...@linutronix.de]
Sent: Friday, October 12, 2012 8:46 PM
To: Liu, Chuansheng
Cc: linux-kernel@vger.kernel.org
Subject: RE: [PATCH] genirq: for edge interrupt IRQS_ONESHOT support
On Fri, 12 Oct 2012, Liu, Chuansheng wrote:
-Original Message-
From: anish kumar [mailto:anish198519851...@gmail.com]
Sent: Friday, October 12, 2012 11:25 PM
To: Liu, Chuansheng
Cc: Thomas Gleixner; linux-kernel@vger.kernel.org
Subject: RE: [PATCH] genirq: for edge interrupt
On Fri, 12 Oct 2012, Liu, Chuansheng wrote:
On SMP an interrupt which is raised after the ack() again before the
handler finishes, can invoke another delivery on a different CPU,
which then sees the IRQ_INPROGESS flag, masks it and flags it
PENDING. When the primary handler on the first
On Fri, 12 Oct 2012, Liu, Chuansheng wrote:
But IRQS_ONESHOT does not work well for edge interrupt.
And pasting the IRQS_ONESHOT description:
* IRQS_ONESHOT- irq is not unmasked in primary handler
Right, and edge type interrupts doe not support it.
Can we do
On Wed, 24 Oct 2012, Darren Hart wrote:
On 10/23/2012 01:29 PM, Thomas Gleixner wrote:
Now the proposed change
- if (unlikely(ownerdied || !(curval FUTEX_TID_MASK))) {
+ if (unlikely(ownerdied ||
+ !(curval (FUTEX_TID_MASK | FUTEX_WAITERS
On Fri, 26 Oct 2012, he, bo wrote:
From: Yanmin Zhang yanmin.zh...@intel.com
We hit a kernel panic at __run_hrtimer=BUG_ON(timer-state !=
HRTIMER_STATE_CALLBACK).
2[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
Basically,
On Fri, 26 Oct 2012, Yanmin Zhang wrote:
Basically, __run_hrtimer has a race with enqueue_hrtimer. When __run_hrtimer
calls
NAK. See my reply to V1. It's not a race in the core code.
Thanks,
tglx
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On Fri, 26 Oct 2012, Peter Zijlstra wrote:
On Fri, 2012-10-26 at 11:42 +0200, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Fri, 2012-10-26 at 11:24 +0200, Ingo Molnar wrote:
So can we control this by restricting the users and avoiding
the overflow?
On Fri, 26 Oct 2012, Zhang, Yanmin wrote:
From: Thomas Gleixner [mailto:t...@linutronix.de]
Your code is returning HRTIMER_RESTART from the timer callback and at
the same time it starts the timer from some other context. That's what
needs to be fixed.
The timer user should fix it. But could
On Fri, 26 Oct 2012, Steven Rostedt wrote:
On Fri, 2012-10-26 at 11:12 -0700, Juri Lelli wrote:
- scale down (right by 10) incoming parameters as to do internal
math with ~1us resolution (and scale up outgoing params)
Would scaling down by 9 be sufficient? That way the resolution is
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt7 release.
Changes since 3.6.3-rt6:
* Enable SLUB for RT
Last time I looked at SLUB for RT (some years ago) it was just
way more painful than dealing with SLAB, but Christoph Lameter
has done major surgery on the SLUB code
On Fri, 26 Oct 2012, Peter LaDow wrote:
(I've added netfilter and linux-rt-users to try to pull in more help).
On Fri, Oct 26, 2012 at 9:48 AM, Eric Dumazet eric.duma...@gmail.com wrote:
Upstream kernel is fine, there is no race, as long as :
local_bh_disable() disables BH and
On Fri, 26 Oct 2012, Peter LaDow wrote:
On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet eric.duma...@gmail.com wrote:
If this were safe, we wouldn't be seeing this lockup and your patch
wouldn't be needed. So it seems that your patch doesn't really
address the issue that we are not sure a
On Fri, 26 Oct 2012, Thomas Gleixner wrote:
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt7 release.
Changes since 3.6.3-rt6:
* Enable SLUB for RT
Last time I looked at SLUB for RT (some years ago) it was just
way more painful than dealing with SLAB, but Christoph
On Sat, 27 Oct 2012, Anca Emanuel wrote:
On Sat, Oct 27, 2012 at 1:08 AM, Thomas Gleixner t...@linutronix.de wrote:
Looks like CONFIG_NUMA=y exposes explosions. I just noticed that none
of the machines which are in my basic set of test systems have that
enabled.
/me goes to do some
...@kernel.org
Cc: Rafael J. Wysocki r...@sisk.pl
Cc: Andreas Herrmann andreas.herrma...@amd.com
Cc: sta...@vger.kernel.org
Signed-off-by: Thomas Gleixner t...@linutronix.de
---
drivers/cpufreq/powernow-k8.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
Index: linux-2.6/drivers
of the cpu on which this is called. So we fail
to look at the partials of the dead cpu.
Correct this by extending the arguments of unfreeze_partials with the
target cpu number and use per_cpu_ptr instead of this_cpu_ptr.
Signed-off-by: Thomas Gleixner t...@linutronix.de
---
mm/slub.c |8
On Sat, 27 Oct 2012, Tejun Heo wrote:
Hello, Thomas.
On Sat, Oct 27, 2012 at 07:29:25PM +0200, Thomas Gleixner wrote:
This is fully preemptible non cpu bound context though the comment in the
code says:
* Must run on @pol-cpu. cpufreq core is responsible for ensuring
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt8 release.
Changes since 3.6.3-rt7:
* Fix the SLUB fallout on NUMA machines
I missed to fixup the smp function calls which can result in a
deadlock on RT.
* Fix a mainline issue with cpufreq/powernow-k8 (Same patch is
On Sun, 28 Oct 2012, Roland Stigge wrote:
consider arch/arm/mach-lpc32xx/irq.c: irq_set_chained_handler() is
called at a point where it accesses
irq_to_desc(IRQ_LPC32XX_SUB2IRQ)-irq_data.hwirq but which is not yet
initialized.
None of the functions which are called inside of
On Sun, 28 Oct 2012, Roland Stigge wrote:
On 28/10/12 18:34, Thomas Gleixner wrote:
On Sun, 28 Oct 2012, Roland Stigge wrote:
consider arch/arm/mach-lpc32xx/irq.c: irq_set_chained_handler() is
called at a point where it accesses
irq_to_desc(IRQ_LPC32XX_SUB2IRQ)-irq_data.hwirq but which
Dear RT Folks,
I'm pleased to announce the 3.6.3-rt9 release.
Changes since 3.6.3-rt8:
* hrtimer fix for interrupt stall case (Watanabe)
* Disable RCU_FAST_NO_HZ. Uses a timer_list timer in the guts of
the irq disable idle code. Needs some thought
* Netfilter RT workaround
*
401 - 500 of 29421 matches
Mail list logo
