[Top] [All Lists]

Re: how to disable interrupt in application?

To: "Kevin D. Kissell" <>
Subject: Re: how to disable interrupt in application?
From: zhuzhenhua <>
Date: Wed, 31 May 2006 15:37:04 +0800
Cc: "Bin Chen" <>, linux-mips <>
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KTvnLEpzBkGsePsh6W6/xPxSC2ryphw/2eOxc0pv53ueJQaqI4vB72N3fQSeDgnVOHKL79KEW+HmcKchfTEU49E0NI1//+htAGCbqJDJQsE3q2dPQMArj+tENYoWd88xc2TlyiFmaGdCbDhIZIZ64nRDmyhNFR65NcY2wppwwOQ=
In-reply-to: <002a01c6847f$98409480$0602a8c0@Ulysses>
Original-recipient: rfc822;
References: <> <> <002a01c6847f$98409480$0602a8c0@Ulysses>
On 5/31/06, Kevin D. Kissell <> wrote:
sigprocmask manages signals, which are user-mode abstractions
of exceptions.  It does not affect hardware interrupt behavior.
If by "uninterruptable", ZhuZhenHua means that the decoder
process will not get switched out in favor of another user-mode
process, then getpriority()/setpriority() provide some control
that may be sufficient.  If what is desired is that hardware interrupts
are actually masked during some critical sequence, the critical
sequence must be executed with kenel privilege - you need to
look at putting the critical sequence into a driver or other loadable
kernel module that can be invoked by the application code.


            Kevin K.

----- Original Message -----
From: "Bin Chen" <>
To: "zhuzhenhua" <>
Cc: "linux-mips" <>
Sent: Wednesday, May 31, 2006 8:11 AM
Subject: Re: how to disable interrupt in application?

> man sigprocmask
> On 5/31/06, zhuzhenhua <> wrote:
> > our project have a video decoder code run as application. there is
> > some short code want to be run uninterruptable. is there anyway to do
> > it?
> > thanks for any hints
> > Best Regards
> >
> >
> > zhuzhenhua
> >
> >

actually i don't want the pipelining be interrupted while run our user
define instructions.

<Prev in Thread] Current Thread [Next in Thread>