Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-16 Thread Jan Beulich
On 15.05.2025 12:52, Roger Pau Monné wrote: > On Mon, May 12, 2025 at 05:38:07PM +0200, Jan Beulich wrote: >> On 06.05.2025 14:55, Roger Pau Monné wrote: >>> On Tue, May 06, 2025 at 12:16:00PM +0100, Andrew Cooper wrote: On 06/05/2025 9:31 am, Roger Pau Monne wrote: > When a guest is allow

Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-15 Thread Roger Pau Monné
On Mon, May 12, 2025 at 05:38:07PM +0200, Jan Beulich wrote: > On 06.05.2025 14:55, Roger Pau Monné wrote: > > On Tue, May 06, 2025 at 12:16:00PM +0100, Andrew Cooper wrote: > >> On 06/05/2025 9:31 am, Roger Pau Monne wrote: > >>> When a guest is allowed access to cache control operations such trac

Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-12 Thread Jan Beulich
On 06.05.2025 14:55, Roger Pau Monné wrote: > On Tue, May 06, 2025 at 12:16:00PM +0100, Andrew Cooper wrote: >> On 06/05/2025 9:31 am, Roger Pau Monne wrote: >>> When a guest is allowed access to cache control operations such tracking >>> prevents having to issue a system-wide cache flush, and rath

Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-12 Thread Jan Beulich
On 06.05.2025 10:31, Roger Pau Monne wrote: > @@ -2606,6 +2619,36 @@ unsigned int domain_max_paddr_bits(const struct domain > *d) > return bits; > } > > +void vcpu_flush_cache(struct vcpu *curr) > +{ > +ASSERT(curr == current); > +ASSERT(cache_flush_permitted(curr->domain)); > + >

Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-06 Thread Roger Pau Monné
On Tue, May 06, 2025 at 12:16:00PM +0100, Andrew Cooper wrote: > On 06/05/2025 9:31 am, Roger Pau Monne wrote: > > When a guest is allowed access to cache control operations such tracking > > prevents having to issue a system-wide cache flush, and rather just flush > > the pCPUs where the vCPU has

Re: [PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-06 Thread Andrew Cooper
On 06/05/2025 9:31 am, Roger Pau Monne wrote: > When a guest is allowed access to cache control operations such tracking > prevents having to issue a system-wide cache flush, and rather just flush > the pCPUs where the vCPU has been scheduled since the last flush. > > Note that domain-wide flushes

[PATCH 9/9] xen/x86: track dirty pCPU caches for a given vCPU

2025-05-06 Thread Roger Pau Monne
When a guest is allowed access to cache control operations such tracking prevents having to issue a system-wide cache flush, and rather just flush the pCPUs where the vCPU has been scheduled since the last flush. Note that domain-wide flushes accumulate the dirty caches from all the vCPUs, but cle