On 20/12/2016 09:55, Jan Beulich wrote: > This is a first (of three, as far as current plans go) steps to do away > with misleading register names (eax instead of rax). > > 01: x86/MSR: introduce MSR access split/fold helpers > 02: x86/guest-walk: use unambiguous register names > 03: x86/shadow: use unambiguous register names > 04: x86/oprofile: use unambiguous register names > 05: x86/HVM: use unambiguous register names > 06: x86/HVMemul: use unambiguous register names > 07: x86/SVM: use unambiguous register names > (VMX counterpart omitted for now, as I'll need to re-base) > 08: x86/vm-event: use unambiguous register names > 09: x86/traps: use unambiguous register names > 10: x86/misc: use unambiguous register names > > Signed-off-by: Jan Beulich <jbeul...@suse.com> >
I haven't looked at these carefully, but they all seem to be sensible mechanical changes, so Acked-by: Andrew Cooper <andrew.coop...@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
