public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* SAL functions related questions...
@ 2004-04-01 14:11 Francois Wellenreiter
  2004-04-01 22:48 ` Keith Owens
  0 siblings, 1 reply; 2+ messages in thread
From: Francois Wellenreiter @ 2004-04-01 14:11 UTC (permalink / raw)
  To: linux-ia64



		Hi,


	I'm still working about INIT management problematics.

	I just have a question about SAL_GET_STATE_INFO function.
What does exactly mean a return code equal to "1" (e.g. "Call completed
without error but some information was lost due to overflow") ?
I always get this "error" back when pushing on the dump button on a 
Tiger4. What is it due to ?

And which size does exactly SAL_GET_STATE_INFO_SIZE return ? When should
this function be called to allocate large enough buffers (after 
receiving INIT interrupt or at kernel startup) ?

Thanks for your help.

Kind regards,


				Francois WELLENREITER


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: SAL functions related questions...
  2004-04-01 14:11 SAL functions related questions Francois Wellenreiter
@ 2004-04-01 22:48 ` Keith Owens
  0 siblings, 0 replies; 2+ messages in thread
From: Keith Owens @ 2004-04-01 22:48 UTC (permalink / raw)
  To: linux-ia64

On Thu, 01 Apr 2004 16:11:08 +0200, 
Francois Wellenreiter <Francois.Wellenreiter@Ext.Bull.Net> wrote:
>And which size does exactly SAL_GET_STATE_INFO_SIZE return ?

It returns the maximum size of the specified record type.

>When should
>this function be called to allocate large enough buffers (after 
>receiving INIT interrupt or at kernel startup) ?

In theory you could use SAL_GET_STATE_INFO_SIZE just before reading the
record.  However MCA and INIT events are not irq safe, you must _NOT_
call any kernel routines that depend on disabled locks during an MCA or
INIT event.  All kernel memory allocation routines depend on disabled
locks so it is not safe to use those routines during an MCA or INIT
event, which means that you must preallocate memory for these record
types.  Therefore Linux preallocates storage for each record type
during boot.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-04-01 22:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-01 14:11 SAL functions related questions Francois Wellenreiter
2004-04-01 22:48 ` Keith Owens

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox