On Mon, Sep 18, 2017 at 04:50:23PM +0100, Peter Maydell wrote: > On 11 July 2017 at 11:38, Edgar E. Iglesias <edgar.igles...@xilinx.com> wrote: > > Another way could also be to have get_phys_addr() fill in generic > > fields in the FaultInfo struct and then have a faultinfo_to_fsr > > mapping function to populate FSR/PAR. Do you see any issues with that? > > Edgar, did you ever have a go at implementing this?
Hi Peter, No, I haven't looked at it yet. I'm a bit behind on everything here so I probably won't get a chance to look at it soonish... > I'm currently running into a similar issue with M profile, > where at the moment we stuff the information about what > kind of fault the MPU generates into a v7PMSA format > FSR value and reinterpret it into M profile exception > types and fault status register bits later. This works > OK, but for v8M we want to start reporting kinds of fault > (like SecureFault) that don't have equivalents in v7PMSA > at all, and maybe it would be better to clean this up rather > than assigning arbitrary bogus fsr values for internal use... I see, yes that sounds like a similar issue. If you'd like to take over this, that'd be great :-) Cheers, Edgar
