linux-kernel - Acceptable Interrupt Latency in Linux kernel

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>] [day] [month] [year] [list]

Date:	Thu, 25 Sep 2008 14:12:50 -0700
From:	"Singaravelan Nallasellan" <singaravelann@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Acceptable Interrupt Latency in Linux kernel

What is the tolerable interrupt latency for the Linux interrupt handler?

I need to write a driver which will require to invoke a function from
other driver
to read the hardware register. That function will send a message to
the firmware in the some other hardware.

The firmware will go into a bus to read the register and return the
value. This firmware generates an interrupt of the completion of the
register read.

So the whole process of register read will take time to know the
interrupt source.

Currently I dont have the exact duration to read a single register. I
am also planning to push the register read to work queue and return
with IRQ handled from the ISR without knowing the hardware
status.There is a potential to mis handle the interrupt.

If I know the acceptable interrupt latency, It will simplify the ISR handling.

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