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-next>] [day] [month] [year] [list]
Date:	Wed, 7 Jan 2009 10:38:11 +0530
From:	"melwyn lobo" <linux.melwyn@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: SMP timer issue

Hello All,
Following reply from Russell on the ARM mailing list, I have posted my
question on this list.

We have ported the arm kernel 2.6.24 to ARM Cortex dual core
processor. My question is regarding timer optimization.
At present we have three timers for the two cores as follows;
1. MTU which provides the system tick and in the absence of local
timers provides IPI_TIMER messages to other processors.
2. Localtimer for CPU0
3. Localtimer for CPU1

So presently (when local timers are enabled) there are 3 interrupts
for every tick. I want to optimize the logic performed by MTU into the
local timer of CPU0 so that this one serves as the system tick. Thus
there would be no need for MTU interrupts and it would serve only as a
clock source.

My question in particular:
1. Is there some platform which has already done this ?
2. Is this possible without modifying existing kernel framework?
3. How to update jiffies during boot when localtimer has not yet been setup?

Eagerly awaiting for some advice/comments.

Thanks & Regards,
Melwyn

On Tue, Jan 6, 2009 at 11:44 PM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Tue, Jan 06, 2009 at 03:07:15PM +0530, melwyn lobo wrote:
>> Hello All,
>
> I suggest you ask your question of the kernel timer folk, who would
> be more knowledgable of the code you're asking about.  See the
> MAINTAINERS file for their contact info.
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ