On Tue, 4 Oct 2022 at 14:33, Alex Bennée <alex.ben...@linaro.org> wrote: > > > Peter Maydell <peter.mayd...@linaro.org> writes: > > The MSC is in the address map like most other stuff, and thus there is > > no restriction on whether it can be accessed by other things than CPUs > > (DMAing to it would be silly but is perfectly possible). > > > > The intent of the code is "pass this transaction through, but force > > it to be Secure/NonSecure regardless of what it was before". That > > should not involve a change of the requester type. > > Should we assert (or warn) when the requester_type is unspecified?
Not in the design of MemTxAttrs that's currently in git, no: in that design it's perfectly fine for something generating memory transactions to use MEMTXATTRS_UNSPECIFIED (which defaults to meaning a bunch of things including "not secure"). thanks -- PMM
