From: Frederic Marmond <fmarmond@eprocess.fr>
To: Mateusz Srebrny <ms189442@zodiac.mimuw.edu.pl>
Cc: linux-assembly@vger.kernel.org
Subject: Re: interupts...
Date: Mon, 23 Sep 2002 15:37:49 +0200 [thread overview]
Message-ID: <3D8F192D.5040901@eprocess.fr> (raw)
In-Reply-To: Pine.LNX.4.44.0209231456470.21172-100000@zodiac.mimuw.edu.pl
on x86 architecture, you have two 'pic' (programmable interrupt
controlers, which are 8259x chips in serial).
In your handler, you can ask them if it is an hard or soft interrupt
(ports 20h-3fh for the 1rst 8259 and a0h-bfh for the second).
I don't remember exactly which port for this, but you can find docs on
the net with thoses references.
Other way: test if the hard you are handling is the source of the interrupt.
If you have doc of your hard drive, you may find registers where you can
find infos about its state.
good luck!
Fred
Mateusz Srebrny wrote:
>Hi!
>
>This question is out of concern of this group (I think).
>But...
>
>Does proccessor (somehow) know if an interrupt it gets was hard- or soft-
>ware generated? I mean if hard disk finishes for example his asynchronous
>IO operation it generates the disk interrupt. But if I want something from
>the disk I do it all the same...
>
>Is there the same int-handler for hardware and for software, but the
>execution differs by means of some parameters? Or there are two separate
>interrupt accidentally called by the same number?
>
>Thanks for any help...
> Mateusz Srebrny
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2002-09-23 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 13:04 interupts Mateusz Srebrny
2002-09-23 13:26 ` interupts Rudolf Marek
2002-09-23 13:37 ` Frederic Marmond [this message]
2002-10-16 20:14 ` linux distribution based on asmutils Rudolf Marek
[not found] <Pine.VMS.3.91-2(vms).1020923151918.31945B-100000@cs.felk.cvut.cz>
2002-09-23 13:46 ` interupts Frederic Marmond
2002-09-23 13:50 ` interupts Rudolf Marek
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=3D8F192D.5040901@eprocess.fr \
--to=fmarmond@eprocess.fr \
--cc=linux-assembly@vger.kernel.org \
--cc=ms189442@zodiac.mimuw.edu.pl \
/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;
as well as URLs for NNTP newsgroup(s).