Re: [Qemu-devel] [RFC 0/5] Memory transaction attributes API

2015-03-18 Thread Peter Maydell
On 18 March 2015 at 08:38, Edgar E. Iglesias wrote: > 2. The series introduces the read and write _with_attrs. Another > approach could be to add a (for example) single .access callback. > The callback could take a structure pointer as input, e.g: > > struct MemTx { > bool rw; > hwaddr add

Re: [Qemu-devel] [RFC 0/5] Memory transaction attributes API

2015-03-18 Thread Edgar E. Iglesias
On Mon, Mar 16, 2015 at 05:20:17PM +, Peter Maydell wrote: > This is an RFC patchset aimed at getting comment on > some memory API changes to support "transaction attributes", > ie sideband information that goes along with a memory read > or write access to define things like ARM secure/nonsecu

[Qemu-devel] [RFC 0/5] Memory transaction attributes API

2015-03-16 Thread Peter Maydell
This is an RFC patchset aimed at getting comment on some memory API changes to support "transaction attributes", ie sideband information that goes along with a memory read or write access to define things like ARM secure/nonsecure, CPU/transaction master ID, privileged/nonprivileged. (See also pre