linux-kernel - Re: Kernel code interrupted by Timer

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 09 Feb 2013 13:21:56 +0530
From:	anish kumar <anish198519851985@...il.com>
To:	Peter Teoh <htmldeveloper@...il.com>
Cc:	Gaurav Jain <gjainroorkee@...il.com>,
	Kernel Newbies <kernelnewbies@...nelnewbies.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Kernel code interrupted by Timer

On Sat, 2013-02-09 at 14:57 +0800, Peter Teoh wrote:
> 
> 
> On Sat, Feb 9, 2013 at 1:47 PM, anish kumar 
> .
>         Timer interrupts is supposed to cause scheduling and scheduler
>         may or
>         may not pick up your last process(we always use the term
>         "task" in
>         kernel space) after handling timer interrupt.
>         >
>         
> 
> 
> Sorry if I may disagree, correct me if wrong.   Timer interrupt and
> scheduler is two different thing.   I just counted in the "drivers"
> subdirectory, there are at least more than 200 places where
> "setup_timer()" is called, and these have nothing to do with
> scheduling.   For eg, heartbeat operation etc.  Not sure I
> misunderstood something?
Have a look at kernel/timer.c and kernel/hrtimer.c.
There are many sched() calls in these files.This will invoke scheduler.
> 
> 
> -- 
> Regards,
> Peter Teoh


--
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/