Hi Marc, Thank you for having a look at the patch! On 10/6/20 4:32 PM, Marc Zyngier wrote: > Hi Alex, > > On Tue, 06 Oct 2020 16:05:20 +0100, > Alexandru Elisei <alexandru.elisei@xxxxxxx> wrote: >> From ARM DDI 0487F.b, page D9-2807: >> >> "Although the Statistical Profiling Extension acts as another observer in >> the system, for determining the Shareability domain of the DSB >> instructions, the writes of sample records are treated as coming from the >> PE that is being profiled." >> >> Similarly, on page D9-2801: >> >> "The memory type and attributes that are used for a write by the >> Statistical Profiling Extension to the Profiling Buffer is taken from the >> translation table entries for the virtual address being written to. That >> is: >> - The writes are treated as coming from an observer that is coherent with >> all observers in the Shareability domain that is defined by the >> translation tables." >> >> All the PEs are in the Inner Shareable domain, use a DSB ISH to make sure >> writes to the profiling buffer have completed. > I'm a bit sceptical of this change. The SPE writes are per-CPU, and > all we are trying to ensure is that the CPU we are running on has > drained its own queue of accesses. > > The accesses being made within the IS domain doesn't invalidate the > fact that they are still per-CPU, because "the writes of sample > records are treated as coming from the PE that is being profiled.". > > So why should we have an IS-wide synchronisation for accesses that are > purely local? I think I might have misunderstood how perf spe works. Below is my original train of thought. In the buffer management event interrupt we drain the buffer, and if the buffer is full, we call arm_spe_perf_aux_output_end() -> perf_aux_output_end(). The comment for perf_aux_output_end() says "Commit the data written by hardware into the ring buffer by adjusting aux_head and posting a PERF_RECORD_AUX into the perf buffer. It is the pmu driver's responsibility to observe ordering rules of the hardware, so that all the data is externally visible before this is called." My conclusion was that after we drain the buffer, the data must be visible to all CPUs. >From the definition of non-shareable memory (ARM DDI0487F.b, page B2-155): "For Normal memory locations, the Non-shareable attribute identifies Normal memory that is likely to be accessed only by a single PE. A location in Normal memory with the Non-shareable attribute does not require the hardware to make data accesses by different observers coherent, unless the memory is Non-cacheable." Linux configures all memory to be Inner Shareable (SH[1:0] = 0b11), *not* Non-shareable (SH[1:0] = 0b00). I think that the DSB NSH doesn't really do anything, because the PE will not do any accesses to Non-shareable memory, and we end up breaking the assumption of perf_aux_output_end(). Did I make a mistake in my reasoning? Thanks, Alex _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
