On Thu, Jan 18, 2024 at 03:55:00PM -0800, Dan Williams wrote: > Alison Schofield wrote: > [..] > > > > "dpa":1073741824, > > > > "dpa_length":64, > > > > > > The dpa_length is also the hpa_length, right? So maybe just call the > > > field "length". > > > > > > > No, the length only refers to the device address space. I don't think > > the hpa is guaranteed to be contiguous, so only the starting hpa addr > > is offered. > > > > hmm..should we call it 'size' because that seems to imply less > > contiguous-ness than length? > > The only way the length could be discontiguous in HPA space is if the > error length is greater than the interleave granularity. Given poison is > tracked in cachelines and the smallest granularity is 4 cachelines it is > unlikely to hit the mutiple HPA case.
Hi Dan, Circling back to this issue, as I'm posting an udpated rev. I'm not getting how *only* an error length greater that IG can lead to discontigous HPA. If the poison starts on the last 64 bytes of an IG and has a length greater than 64 bytes, we go beyond the endpoints mapping, even if that length is less than IG. In the layout below, if the device underlying endpoint2 reports ^poison^ as shown, it is discontinguous in HPA space. HPA 0..........................................................N ep1 .......... .......... .......... ep2 .......... .......... .......... bad ^poison^ good ^po ison^ 'bad' is what happens today if length is applied to HPA 'good' is what is right Am I missing something wrt cachelines you mention? > > However, I think the kernel side should aim to preclude that from > happening. Given that this is relying on the kernel's translation I > would make it so that the kernel never leaves the impacted HPAs as > ambiguous. For example, if the interleave_granularity of the region is > 256 and the DPA length is 512, it would be helpful if the *kernel* split > that into multiple trace events to communicate the multiple impacted > HPAs rather than leave it as an exercise to userspace. > That's a familiar plan that we rejected in the driver implementation, As defined, a cxl_poison event reports a starting dpa, a dpa_length, and the starting hpa if the address is mapped. That left userspace to do the HPA translation work. We can move that work to the driver independent of this ndctl work. > > Might be useful to capture Erwin's analysis of how to use that field in > the man page, if it's not there already. The man page now has the definitions of the source field and a spec reference. I don't see the cxl list man page as the place to offer media-error trouble-shooting tips.
