From: "Kevin D. Kissell" <kevink@mips.com>
To: "zhuzhenhua" <zzh.hust@gmail.com>
Cc: "Bin Chen" <binary.chen@gmail.com>,
"linux-mips" <linux-mips@linux-mips.org>
Subject: Re: how to disable interrupt in application?
Date: Wed, 31 May 2006 11:39:56 +0200 [thread overview]
Message-ID: <002501c68496$2e7f8df0$10eca8c0@grendel> (raw)
In-Reply-To: 50c9a2250605310037n42dd6ddct2238cf9c56eac40d@mail.gmail.com
> actually i don't want the pipelining be interrupted while run our user
> defined instructions.
If you want to guarantee that, you need to put that code into a kernel
module that turns off interrupts during processing - and you need to
accept responsibility for the fact that a problem in your code may be
irrecoverably fatal to the system, and that errors in system timing may
accumulate due to clock interrupts not being serviced.
Regards,
Kevin K.
next prev parent reply other threads:[~2006-05-31 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 0:33 how to disable interrupt in application? zhuzhenhua
2006-05-31 6:11 ` Bin Chen
2006-05-31 6:58 ` Kevin D. Kissell
2006-05-31 7:37 ` zhuzhenhua
2006-05-31 9:39 ` Kevin D. Kissell [this message]
2006-05-31 7:02 ` Freddy Spierenburg
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='002501c68496$2e7f8df0$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=binary.chen@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=zzh.hust@gmail.com \
/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