From: Chuck Fleckenstein <cfleck@co.intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] re-enabling interrupts and interrupt collect
Date: Wed, 08 Nov 2000 10:06:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205670@msgid-missing> (raw)
Since the ssm of psr.i does not require serialization then I believe this
would
be expected.
so as you said the guaranteed method of safely reenabling ic and i would
be:
ssm psr.ic
;;
srlz.d
ssm psr.i
Chuck
Jonathan Case Nicklin wrote:
> All,
>
> Recently, i was working on a section of code that disabled/enable
> interrupts
> and interrupt collection like so.
>
> rsm psr.i | psr.ic
> ;;
> ... //body
> ;;
> ssm psr.i | psr.ic
> ;;
> srlz.d
> ;;
>
> I found however that this implementation did not work under heavy loads.
>
> It took a while to figure out that a pending interrupt that had occurred
>
> in the body of code, executed while interrupts were turned off, was
> delivered
> after the ssm call as expected. However, it was delivered before the ic
> bit
> serialized. In the code this caused undesirable results. I found that
> the
> proper way to implement the above is to re-enable the ic bit and
> serialize
> before re-enabling the interrupt bit. Has anyone else come across this
> problem and can anybody shed some light on whether this is the expected
> operation.
>
> Sincerely,
> Jonathan Case Nicklin
>
> Mission Critical Linux
> www.missioncriticallinux.com
>
> ps. The manual gives an example of the implementation that works, but
> does
> not provide any explanation of implementation itself (as far as I can
> see ;-P )
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next reply other threads:[~2000-11-08 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 10:06 Chuck Fleckenstein [this message]
2000-11-08 13:28 ` [Linux-ia64] re-enabling interrupts and interrupt collect Jonathan Case Nicklin
2000-11-08 16:46 ` David Mosberger
2000-11-08 18:37 ` Mallick, Asit K
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=marc-linux-ia64-105590678205670@msgid-missing \
--to=cfleck@co.intel.com \
--cc=linux-ia64@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