All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Replacements for local_irq_xxx()
Date: Thu, 10 May 2001 14:26:38 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005563@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005562@msgid-missing>

>>>>> On Thu, 10 May 2001 18:55:13 +1000, Keith Owens <kaos@ocs.com.au> said:

  Keith> Existing local_irq_xxx() routines clear psr.i which masks all
  Keith> interrupts, including NMI.  Then the only way to get the
  Keith> attention of a cpu in a disabled spin loop is via INIT which
  Keith> is too drastic.  How about these alternatives which set
  Keith> cr.tpr.mmi instead, masking all external interrupts except
  Keith> NMI?

I'd rather not do that.  Accessing tpr is slow and requires explicit
serialization.

	--david


  reply	other threads:[~2001-05-10 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10  8:55 [Linux-ia64] Replacements for local_irq_xxx() Keith Owens
2001-05-10 14:26 ` David Mosberger [this message]
2001-05-10 15:39 ` David Mosberger
2001-05-14 12:52 ` Keith Owens
2001-05-14 17:22 ` DE-DINECHIN,CHRISTOPHE (HP-Cupertino,ex1)
2001-05-15 15:11 ` David Mosberger

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-105590693005563@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.