Re: [Xen-devel] [PATCH v2 5/6] xen/x86: use flag byte for decision whether xen_cr3 is valid

2018-03-08 Thread Juergen Gross
On 08/03/18 15:24, Jan Beulich wrote: On 02.03.18 at 09:14, wrote: >> This reduces the number of branches in interrupt handling and results >> in better performance (e.g. parallel make of the Xen hypervisor on my >> system was using about 3% less system time). > > 3% seems an awful lot for a

Re: [Xen-devel] [PATCH v2 5/6] xen/x86: use flag byte for decision whether xen_cr3 is valid

2018-03-08 Thread Jan Beulich
>>> On 02.03.18 at 09:14, wrote: > This reduces the number of branches in interrupt handling and results > in better performance (e.g. parallel make of the Xen hypervisor on my > system was using about 3% less system time). 3% seems an awful lot for a single conditional branch on each of the thre

[Xen-devel] [PATCH v2 5/6] xen/x86: use flag byte for decision whether xen_cr3 is valid

2018-03-02 Thread Juergen Gross
Today cpu_info->xen_cr3 is either 0 to indicate %cr3 doesn't need to be switched on entry to Xen, or negative for keeping the value while indicating not to restore %cr3, or positive in case %cr3 is to be restored. Switch to use a flag byte instead of a negative xen_cr3 value in order to allow %cr3