On 16/02/2023 01:10, john.c.harri...@intel.com wrote:
From: John Harrison
Instruction from hardware arch is that stolen memory and BAR mappings
are unsafe for use as ring buffers. There can be issues with cache
aliasing due to the CPU access going to memory via the BAR. So, don't
do it.
v2:
On Fri, 2023-02-17 at 09:18 -0800, John Harrison wrote:
> On 2/17/2023 00:39, Hogander, Jouni wrote:
> > On Wed, 2023-02-15 at 17:10 -0800, john.c.harri...@intel.com wrote:
> > > From: John Harrison
> > >
> > > Instruction from hardware arch is that stolen memory and BAR
> > > mappings
> > > are
On 2/17/2023 00:39, Hogander, Jouni wrote:
On Wed, 2023-02-15 at 17:10 -0800, john.c.harri...@intel.com wrote:
From: John Harrison
Instruction from hardware arch is that stolen memory and BAR mappings
are unsafe for use as ring buffers. There can be issues with cache
aliasing due to the CPU ac
On Wed, 2023-02-15 at 17:10 -0800, john.c.harri...@intel.com wrote:
> From: John Harrison
>
> Instruction from hardware arch is that stolen memory and BAR mappings
> are unsafe for use as ring buffers. There can be issues with cache
> aliasing due to the CPU access going to memory via the BAR. So
From: John Harrison
Instruction from hardware arch is that stolen memory and BAR mappings
are unsafe for use as ring buffers. There can be issues with cache
aliasing due to the CPU access going to memory via the BAR. So, don't
do it.
v2: Dont use BAR mappings either.
Make conditional on LLC so a
