From: "Anshuman Rawat" <asr245@nyu.edu>
To: linux-newbie@vger.kernel.org
Subject: fast interrupts?
Date: Sat, 8 Jun 2002 05:11:01 -0400 [thread overview]
Message-ID: <046701c20ecc$69f3d560$9e03a5d8@oemcomputer> (raw)
Hi,
I am new both to this list and linux and i need help. have started reading
the book by Michael Beck...
am not clear about register saving in fast interrupts...
the book says...
while handling a fast interrupt, only those registers are saved that are
modified by a normal C function (?). This means that , if assmbler code is
to be used in the handling routine, the remaining registers (?) must be
saved beforehand and restored afterwards.
what does the author mean by registers modified by a normal C function, and
the remaining registers?
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2002-06-08 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 9:11 Anshuman Rawat [this message]
2002-06-08 9:58 ` fast interrupts? Elias Athanasopoulos
2002-06-08 19:30 ` Anshuman Rawat
2002-06-08 23:38 ` Elias Athanasopoulos
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='046701c20ecc$69f3d560$9e03a5d8@oemcomputer' \
--to=asr245@nyu.edu \
--cc=linux-newbie@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