>>> On 29.01.18 at 19:12, <andrew.coop...@citrix.com> wrote: > __GET_CURRENT() is very dangerous to use, as is easy to confuse with
I wouldn't say "very", but for the change as a whole - well, yes, why not. > GET_CURRENT(), but strictly depends on the regster parameter already having > the STACK_END value in it. Also, there is no reason to special case accesses > of current_vcpu differently to other cpuinfo fields. > > Expand __GET_CURRENT() in its current users, and remove the macro. > > Take the opportunity to replace the GET_CURRENT() in the cstar path which > doesn't need to recalculate STACK_END. > > No functional change. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> Reviewed-by: Jan Beulich <jbeul...@suse.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
