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:	Mon, 21 Jul 2008 11:04:03 -0700 (PDT)
From:	soohoon lee <soohoon_lee@...oo.com>
To:	linux-kernel@...r.kernel.org
Subject: Question: queuing timer interrupts


Hi,
I like to ask you experts what would be a better way to solve following problem and side effects of my solution.

There is a system and sometimes it should unavoidably block interrupts for critical jobs for couple of 10ms so will lost timer ticks.
But keeping the wall clock is also critical.
I thought about two solutions.
1. update wall clock when OS gets out of the critical section.
2. Add a hardware to count lost timer ticks, it's easy for this system.
   So when the OS is able to process interrupts again, the hardware generates timer interrupts back to back to compensate lost ticks.

Thanks in advance,
Soohoon.



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