linux-kernel - Re: Load interrupt code dynamically

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]

Message-ID: <20070801010304.757f4963@the-village.bc.nu>
Date:	Wed, 1 Aug 2007 01:03:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Haifeng He" <hehaifeng2nd@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Load interrupt code dynamically

> dealing with the concurrency in the kernel. Interrupt is one of them.

Its extremely hard as you've probably noticed by now.

> My first question is, what are other interrupts in the kernel that can
> allow other interrupts
> to be issued? Second question is, how does the kernel switch between

The kernel IRQ handling is pretty flexible. A concious decision was made
many years ago not to try and limit it to do a pageable kernel as RAM was
far cheaper than the pain, and getting cheaper by the day.

> different interrupts? Last, any suggestion on how to change my current
> implementation to enable loading interrupt code dynamically?

Realistically - the one case it is done right now is by the mainframe
people, simply because the underlying hypervisor does it. You probably
have much more chance that way using a microkernel (real one not MACH)
underneath. Still a huge task.
-
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/