Re: [PATCH v2 3/5] x86/HVM: correct read/write split at page boundaries

2025-01-23 Thread Roger Pau Monné
On Thu, Jan 23, 2025 at 10:49:36AM +0100, Jan Beulich wrote: > On 22.01.2025 18:45, Roger Pau Monné wrote: > > On Tue, Oct 01, 2024 at 10:49:40AM +0200, Jan Beulich wrote: > >> The MMIO cache is intended to have one entry used per independent memory > >> access that an insn does. This, in particula

Re: [PATCH v2 3/5] x86/HVM: correct read/write split at page boundaries

2025-01-23 Thread Jan Beulich
On 22.01.2025 18:45, Roger Pau Monné wrote: > On Tue, Oct 01, 2024 at 10:49:40AM +0200, Jan Beulich wrote: >> The MMIO cache is intended to have one entry used per independent memory >> access that an insn does. This, in particular, is supposed to be >> ignoring any page boundary crossing. Therefor

Re: [PATCH v2 3/5] x86/HVM: correct read/write split at page boundaries

2025-01-22 Thread Roger Pau Monné
On Tue, Oct 01, 2024 at 10:49:40AM +0200, Jan Beulich wrote: > The MMIO cache is intended to have one entry used per independent memory > access that an insn does. This, in particular, is supposed to be > ignoring any page boundary crossing. Therefore when looking up a cache > entry, the access'es

[PATCH v2 3/5] x86/HVM: correct read/write split at page boundaries

2024-10-01 Thread Jan Beulich
The MMIO cache is intended to have one entry used per independent memory access that an insn does. This, in particular, is supposed to be ignoring any page boundary crossing. Therefore when looking up a cache entry, the access'es starting (linear) address is relevant, not the one possibly advanced