Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-18 Thread Roger Pau Monné
On Wed, Sep 25, 2019 at 05:23:11PM +0200, Jan Beulich wrote: > When there's no XPTI-enabled PV domain at all, there's no need to issue > respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and > record the creation of PV domains by bumping opt_xpti_* accordingly. > > As to the sticky op

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-19 Thread Jan Beulich
On 18.05.2020 19:09, Roger Pau Monné wrote: > On Wed, Sep 25, 2019 at 05:23:11PM +0200, Jan Beulich wrote: >> @@ -310,7 +313,16 @@ int pv_domain_initialise(struct domain * >> /* 64-bit PV guest by default. */ >> d->arch.is_32bit_pv = d->arch.has_32bit_shinfo = 0; >> >> -d->arch.pv.x

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-19 Thread Roger Pau Monné
On Tue, May 19, 2020 at 09:55:38AM +0200, Jan Beulich wrote: > On 18.05.2020 19:09, Roger Pau Monné wrote: > > On Wed, Sep 25, 2019 at 05:23:11PM +0200, Jan Beulich wrote: > >> @@ -310,7 +313,16 @@ int pv_domain_initialise(struct domain * > >> /* 64-bit PV guest by default. */ > >> d->arc

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-19 Thread Jan Beulich
On 19.05.2020 11:15, Roger Pau Monné wrote: > On Tue, May 19, 2020 at 09:55:38AM +0200, Jan Beulich wrote: >> On 18.05.2020 19:09, Roger Pau Monné wrote: >>> On Wed, Sep 25, 2019 at 05:23:11PM +0200, Jan Beulich wrote: @@ -310,7 +313,16 @@ int pv_domain_initialise(struct domain * /*

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-22 Thread Andrew Cooper
On 25/09/2019 16:23, Jan Beulich wrote: > When there's no XPTI-enabled PV domain at all, there's no need to issue > respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and > record the creation of PV domains by bumping opt_xpti_* accordingly. > > As to the sticky opt_xpti_domu vs increme

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-22 Thread Roger Pau Monné
On Fri, May 22, 2020 at 12:00:14PM +0100, Andrew Cooper wrote: > On 25/09/2019 16:23, Jan Beulich wrote: > > When there's no XPTI-enabled PV domain at all, there's no need to issue > > respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and > > record the creation of PV domains by bumpin

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-22 Thread Jan Beulich
On 22.05.2020 13:00, Andrew Cooper wrote: > On 25/09/2019 16:23, Jan Beulich wrote: >> When there's no XPTI-enabled PV domain at all, there's no need to issue >> respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and >> record the creation of PV domains by bumping opt_xpti_* accordingly

Re: [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2020-05-22 Thread Andrew Cooper
On 22/05/2020 12:13, Roger Pau Monné wrote: > On Fri, May 22, 2020 at 12:00:14PM +0100, Andrew Cooper wrote: >> On 25/09/2019 16:23, Jan Beulich wrote: >>> When there's no XPTI-enabled PV domain at all, there's no need to issue >>> respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and

[Xen-devel] [PATCH v3 1/5] x86: suppress XPTI-related TLB flushes when possible

2019-09-25 Thread Jan Beulich
When there's no XPTI-enabled PV domain at all, there's no need to issue respective TLB flushes. Hardwire opt_xpti_* to false when !PV, and record the creation of PV domains by bumping opt_xpti_* accordingly. As to the sticky opt_xpti_domu vs increment/decrement of opt_xpti_hwdom, this is done this