On 19 September 2017 at 05:43, Edgar E. Iglesias
wrote:
> On Mon, Sep 18, 2017 at 04:50:23PM +0100, Peter Maydell wrote:
>> 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
On Mon, Sep 18, 2017 at 04:50:23PM +0100, Peter Maydell wrote:
> On 11 July 2017 at 11:38, Edgar E. Iglesias 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
On 11 July 2017 at 11:38, Edgar E. Iglesias 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 implem
On 11 July 2017 at 11:38, Edgar E. Iglesias 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?
Yes, that's probably better. It's how t
On Tue, Jul 11, 2017 at 11:14:04AM +0100, Peter Maydell wrote:
> On 11 July 2017 at 11:03, Edgar E. Iglesias wrote:
> > On Mon, Jul 10, 2017 at 04:11:29PM +0100, Peter Maydell wrote:
> >> So this kind of worries me, because what it's coded as is "determine
> >> whether architecturally we should be
On Tue, Jul 11, 2017 at 11:14:04AM +0100, Peter Maydell wrote:
> On 11 July 2017 at 11:03, Edgar E. Iglesias wrote:
> > On Mon, Jul 10, 2017 at 04:11:29PM +0100, Peter Maydell wrote:
> >> So this kind of worries me, because what it's coded as is "determine
> >> whether architecturally we should be
On 11 July 2017 at 11:03, Edgar E. Iglesias wrote:
> On Mon, Jul 10, 2017 at 04:11:29PM +0100, Peter Maydell wrote:
>> So this kind of worries me, because what it's coded as is "determine
>> whether architecturally we should be returning a 64-bit or 32-bit
>> PAR format", but what the code below i
On Mon, Jul 10, 2017 at 04:11:29PM +0100, Peter Maydell wrote:
> On 30 June 2017 at 14:45, Edgar E. Iglesias wrote:
> > From: "Edgar E. Iglesias"
> >
> > Extend PAR format determination to handle more cases.
> >
> > Signed-off-by: Edgar E. Iglesias
> > ---
> > target/arm/helper.c | 30 +
On 30 June 2017 at 14:45, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias"
>
> Extend PAR format determination to handle more cases.
>
> Signed-off-by: Edgar E. Iglesias
> ---
> target/arm/helper.c | 30 +-
> 1 file changed, 29 insertions(+), 1 deletion(-)
>
> di
From: "Edgar E. Iglesias"
Extend PAR format determination to handle more cases.
Signed-off-by: Edgar E. Iglesias
---
target/arm/helper.c | 30 +-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/target/arm/helper.c b/target/arm/helper.c
index fd1027e..6
10 matches
Mail list logo
