I suspect that most members that will comment on this case cannot
post to tesla-dev. I will be forwarding messages that I think have
not made the alias. Make sure that responses are to the forward
message with the complete To and CC list plus the Subject line as it
appears in the message (it is used by the internal tools to make sure
they are archived against the case).
Here is the first.
---- Randy
---------- Forwarded message ----------
Date: Wed, 18 Feb 2009 11:59:04 -0800
From: Artem Kachitchkine <[email protected]>
To: Randy Fishel <randy.fishel at sun.com>
Cc: PSARC-ext at sun.com, jiang.liu at intel.com, frank.wang at intel.com,
tesla-dev at opensolaris.org
Subject: Re: CPU Idle Notification [PSARC/2009/115 FastTrack timeout 02/25/2009]
> 4.2.5. Register CPU idle notification callback
> int cpu_idle_register_callback(uint_t priority,
> cpu_idle_callback_t *callbackp, void *arg, void **hdlpp);
> This interface registers a callback to be called when CPU idle state
> changes. All registered callbacks will be called in priority order
> from high to low when CPU enters idle state and will be called in
> reverse order when CPU exits idle state.
> Argument priority is used to determine the calling order of
> registered callbacks.
> Argument arg will be passed back to registered callback and how to
> use it is determined by callback.
What are possible return values and their meaning?
On architectures that do not implement this functionality (sparc?), will these
functions exist, i.e. will consumers be #ifdef free, and if so, what's the
behavior: fail callback registration, or succeed but never callback.
-Artem
