Linux Newbie help
 help / color / mirror / Atom feed
From: "Anshuman Rawat" <asr245@nyu.edu>
To: Elias Athanasopoulos <eathan@otenet.gr>
Cc: linux-newbie@vger.kernel.org
Subject: Re: fast interrupts?
Date: Sat, 8 Jun 2002 15:30:03 -0400	[thread overview]
Message-ID: <003a01c20f22$e490e140$4204a5d8@oemcomputer> (raw)
In-Reply-To: 20020608125800.D12928@neutrino.particles.org


> On Sat, Jun 08, 2002 at 05:11:01AM -0400, Anshuman Rawat wrote:
> > 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?
>
> A CPU has some registers in order to store data and process them using
> the internal command set of the architecture. Registers are the internal
> "memory" of the CPU.
>
> In the program flow, when the control is taken by a function
> (this is not only for C), some values are stored to specific registers.
> This helps the CPU to know what to do (i.e. in which mem address will
> start reading) when the function returns.
>
> Elias
>
so it means that only those registers are saved that were being used by the
process which was interrupted? or only those which the process was using and
the intr. handling routine will also use?

-
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

  reply	other threads:[~2002-06-08 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08  9:11 fast interrupts? Anshuman Rawat
2002-06-08  9:58 ` Elias Athanasopoulos
2002-06-08 19:30   ` Anshuman Rawat [this message]
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='003a01c20f22$e490e140$4204a5d8@oemcomputer' \
    --to=asr245@nyu.edu \
    --cc=eathan@otenet.gr \
    --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