On Fri, 2022-03-11 at 18:38 +0100, Eric Farman wrote: > The SIGP instruction presents a CC0 when an order is accepted, > though the work for the order may be performed asynchronously. > While any such work is outstanding, nearly any other SIGP order > sent to the same CPU will be returned with a CC2. > > Currently, there are two library functions that perform a SIGP, > one which retries a SIGP that gets a CC2, and one which doesn't. > In practice, the users of this functionality want the CC2 to be > handled by the library itself, rather than determine whether it > needs to retry the request or not. > > To avoid confusion, let's convert the smp_sigp() routine to > perform the sigp_retry() logic, and then convert any users of > smp_sigp_retry() to smp_sigp(). This of course means that the > external _retry() interface can be removed for simplicity. > > Signed-off-by: Eric Farman <farman@xxxxxxxxxxxxx> Reviewed-by: Nico Boehr <nrb@xxxxxxxxxxxxx>
