All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] latest MCA logging patch
Date: Fri, 11 Jan 2002 21:33:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805812@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805745@msgid-missing>

>>>>> On Fri, 11 Jan 2002 13:25:40 -0800, "Mallick, Asit K" <asit.k.mallick@intel.com> said:

  Asit> David, SAL re-entrancy issue was primarily observed with
  Asit> SAL_PCI_READ/WRITE_CONFIG in very early firmwares and earlier
  Asit> kernels. However, this re-entrancy problem is fixed with the
  Asit> use of the pci_lock.

If the pci_lock is sufficient for SAL_PCI_READ/WRITE_CONFIG, we can
remove it for those two cases (with a comment to that effect).  I
don't really see much point in doing this though.  It's not like this
is a performance critical operation.

  Asit> Other SAL calls are used during the
  Asit> initialization time and should have re-entrancy
  Asit> problem. Anyway, Jenna is checking with FW team on re-entrancy
  Asit> and will provide the FW versions.

Will you check only for Intel firmware or all IA-64 firmware in
existence?  The original SAL spec did not require re-entrancy and I
don't think it's safe to remove the lock unless we know for sure that
all existing implementations have been fixed (or are no longer in
use).

	--david


  parent reply	other threads:[~2002-01-11 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-05  2:48 [Linux-ia64] latest MCA logging patch Hall, Jenna S
2002-01-10 19:07 ` David Mosberger
2002-01-11  0:16 ` Hall, Jenna S
2002-01-11  0:19 ` David Mosberger
2002-01-11 21:25 ` Mallick, Asit K
2002-01-11 21:33 ` David Mosberger [this message]
2002-01-11 22:42 ` Jack Steiner
2002-01-15 22:35 ` Hall, Jenna S
2002-01-17  5:20 ` 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-105590698805812@msgid-missing \
    --to=davidm@napali.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.