From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] re-enabling interrupts and interrupt collect
Date: Wed, 08 Nov 2000 16:46:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205669@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205670@msgid-missing>
Yes, psr.ic needs to be on before psr.i can be turned on. That's what
we are doing in ivt.S, for example. I thought the manual was quite
clear on that topic.
--david
>>>>> On Wed, 08 Nov 2000 08:28:32 -0500, Jonathan Case Nicklin <nicklin@missioncriticallinux.com> said:
Jonathan> All, Recently, i was working on a section of code that
Jonathan> disabled/enable interrupts and interrupt collection like
Jonathan> so.
Jonathan> rsm psr.i | psr.ic ;; ... //body ;; ssm psr.i | psr.ic
Jonathan> ;; srlz.d ;;
Jonathan> I found however that this implementation did not work
Jonathan> under heavy loads.
Jonathan> It took a while to figure out that a pending interrupt
Jonathan> that had occurred in the body of code, executed while
Jonathan> interrupts were turned off, was delivered after the ssm
Jonathan> call as expected. However, it was delivered before the ic
Jonathan> bit serialized. In the code this caused undesirable
Jonathan> results. I found that the proper way to implement the
Jonathan> above is to re-enable the ic bit and serialize before
Jonathan> re-enabling the interrupt bit. Has anyone else come across
Jonathan> this problem and can anybody shed some light on whether
Jonathan> this is the expected operation.
Jonathan> Sincerely, Jonathan Case Nicklin
Jonathan> Mission Critical Linux www.missioncriticallinux.com
Jonathan> ps. The manual gives an example of the implementation that
Jonathan> works, but does not provide any explanation of
Jonathan> implementation itself (as far as I can see ;-P )
next prev parent reply other threads:[~2000-11-08 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 10:06 [Linux-ia64] re-enabling interrupts and interrupt collect Chuck Fleckenstein
2000-11-08 13:28 ` Jonathan Case Nicklin
2000-11-08 16:46 ` David Mosberger [this message]
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-105590678205669@msgid-missing \
--to=davidm@hpl.hp.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