From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] latest MCA logging patch
Date: Fri, 11 Jan 2002 21:25:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805811@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805745@msgid-missing>
David,
SAL re-entrancy issue was primarily observed with SAL_PCI_READ/WRITE_CONFIG
in very early firmwares and earlier kernels. However, this re-entrancy
problem is fixed with the use of the pci_lock. Other SAL calls are used
during the initialization time and should have re-entrancy problem. Anyway,
Jenna is checking with FW team on re-entrancy and will provide the FW
versions.
Thanks,
Asit
> -----Original Message-----
> From: David Mosberger [mailto:davidm@napali.hpl.hp.com]
> Sent: Thursday, January 10, 2002 4:20 PM
> To: Hall, Jenna S
> Cc: linux-ia64@linuxia64.org
> Subject: RE: [Linux-ia64] latest MCA logging patch
>
>
> >>>>> On Thu, 10 Jan 2002 16:16:33 -0800, "Hall, Jenna S"
> <jenna.s.hall@intel.com> said:
>
> Jenna> OK I've made the local_irq_save() change and here is the new
> Jenna> patch. As per the latest (July 2001) SAL spec, all SAL calls
> Jenna> used in the Linux kernel are re-entrant, except some called
> Jenna> by the bootstrap processor during boot time. See table 9-2.
>
> My understanding is that there is firmware out there that's not fully
> re-entrant. As long as this is the case, I don't believe this change
> is safe.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
>
next prev parent reply other threads:[~2002-01-11 21:25 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 [this message]
2002-01-11 21:33 ` David Mosberger
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-105590698805811@msgid-missing \
--to=asit.k.mallick@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 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.