Re: [PATCH v5 01/20] hw: encode accessing CPU index in MemTxAttrs

2022-11-21 Thread Peter Maydell
On Fri, 11 Nov 2022 at 18:25, Alex Bennée wrote: > > We currently have hacks across the hw/ to reference current_cpu to > work out what the current accessing CPU is. This breaks in some cases > including using gdbstub to access HW state. As we have MemTxAttrs to > describe details about the access

Re: [PATCH v5 01/20] hw: encode accessing CPU index in MemTxAttrs

2022-11-11 Thread Richard Henderson
On 11/12/22 04:25, Alex Bennée wrote: +/* + * Bus masters which don't specify any attributes will get this which + * indicates none of the attributes can be used. + */ +#define MEMTXATTRS_UNSPECIFIED ((MemTxAttrs) \ +{ .requester_type = MTRT_UNSPECIFIED }) + +/* +

[PATCH v5 01/20] hw: encode accessing CPU index in MemTxAttrs

2022-11-11 Thread Alex Bennée
We currently have hacks across the hw/ to reference current_cpu to work out what the current accessing CPU is. This breaks in some cases including using gdbstub to access HW state. As we have MemTxAttrs to describe details about the access lets extend it so CPU accesses can be explicitly marked. T