linux-kernel - Re: [RFC PATCH] hrtimer: removing all ur callback modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Dec 2008 23:46:19 +0100
From:	Oliver Hartkopp <oliver@...tkopp.net>
To:	Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Miller <davem@...emloft.net>
Subject: Re: [RFC PATCH] hrtimer: removing all ur callback modes

Ingo Molnar wrote:
> * Peter Zijlstra <peterz@...radead.org> wrote:
>
>   
>>> ps. What is the intended release for this hrtimer cleanup? 2.6.29?
>>>       
>> I think so, Thomas, Ingo?
>>     
>
> yes, 2.6.29.
>
> 	Ingo
>   

AFAICS the commit ca109491f612aab5c8152207631c0444f63da97f

"hrtimer: removing all ur callback modes" with "Impact: cleanup, move 
all hrtimer processing into hardirq context"

did not find it's way into linux-2.6.git - is there any reason for this?

I reworked some of my code in net/can/bcm.c so that it uses tasklets in 
the cases i needed the soft-irq context and therefore it can cope with 
the hrtimers running always in hard-irq context now.

I'll send a patch to Dave the next days after some more testing on your 
latest sched-devel -tip tree. It works fine so far. From my side you can 
go ahead with the hrtimer reduction to hard-irq context (for 2.6.29).

Regards,
Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/