From: "Haifeng He" <hehaifeng2nd@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Load interrupt code dynamically
Date: Tue, 31 Jul 2007 14:26:33 -0700 [thread overview]
Message-ID: <ab08258e0707311426r32dc15cexb6867648bc6a45a4@mail.gmail.com> (raw)
Hi, all,
I am working on a project to reduce the memory requirement of Linux
kernel code. The idea is to keep infrequent executed code on disk and
load them into a
buffer (code buffer) in memory at runtime. The idea is simple but
there are many issues
dealing with the concurrency in the kernel. Interrupt is one of them.
Since interrupt is executed asynchronously, my current solution is to
assign two buffers: one for regular (non-interrupt code) and one
specifically for
interrupt code. However, the scheme still does not work well. The
problem is that, it seems,
there can multiple interrupt occur at the same in the kernel and
therefore, if interrupt
A is using the code buffer, another interrupt B can be issued and
overwrite the code
buffer(where A's code is stored). I found couples of such examples,
including, driver code
for ide (driver/ide/) and video (driver/video/vgacon.c) and console
(driver/char/). My
feeling is that since handling ide interrupt may take a while, kernel
will enable
other interrupts when handling an ide request.
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
different interrupts? Last, any suggestion on how to change my current
implementation to
enable loading interrupt code dynamically?
Thank you
Haifeng
next reply other threads:[~2007-07-31 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:26 Haifeng He [this message]
2007-08-01 0:03 ` Alan Cox
2007-08-01 11:06 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab08258e0707311426r32dc15cexb6867648bc6a45a4@mail.gmail.com \
--to=hehaifeng2nd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®