From: Alex Smith
CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer) don't (currently) write
through L2. Therefore, to make these writes visible to later accesses
we must invalidate L2 rather than just writing it back, to avoid the
possibility that stale data is read
On 28 March 2017 at 19:11, Bas Nieuwenhuizen wrote:
> On Tue, Mar 28, 2017 at 6:31 PM, Alex Smith
> wrote:
>> On 28 March 2017 at 17:09, Emil Velikov wrote:
>>>
>>> On 22 March 2017 at 10:06, Bas Nieuwenhuizen
On Tue, Mar 28, 2017 at 6:31 PM, Alex Smith wrote:
> On 28 March 2017 at 17:09, Emil Velikov wrote:
>>
>> On 22 March 2017 at 10:06, Bas Nieuwenhuizen
>> wrote:
>> > On Tue, Mar 21, 2017 at 1:02 PM, Alex Smith
>> >
On 28 March 2017 at 17:09, Emil Velikov wrote:
> On 22 March 2017 at 10:06, Bas Nieuwenhuizen
> wrote:
> > On Tue, Mar 21, 2017 at 1:02 PM, Alex Smith
> wrote:
> >> CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer)
On 22 March 2017 at 10:06, Bas Nieuwenhuizen wrote:
> On Tue, Mar 21, 2017 at 1:02 PM, Alex Smith
> wrote:
>> CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer) don't (currently) write
>> through L2. Therefore, to make these writes visible to
On Tue, Mar 21, 2017 at 1:02 PM, Alex Smith wrote:
> CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer) don't (currently) write
> through L2. Therefore, to make these writes visible to later accesses
> we must invalidate L2 rather than just writing it back, to avoid the
CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer) don't (currently) write
through L2. Therefore, to make these writes visible to later accesses
we must invalidate L2 rather than just writing it back, to avoid the
possibility that stale data is read through L2.
Cc: "17.0"