On 12/8/17 3:55 AM, Peter Maydell wrote:
>> If you give me example on how
>> to trigger this type of request with debug=1 then I can look into the code
>> and see what we can do when memory encryption is enabled. The things like
>> read-clears-bits semantics will be tricky.
> The question was rea
On Fri, Dec 08, 2017 at 09:55:26AM +, Peter Maydell wrote:
> On 7 December 2017 at 21:20, Brijesh Singh wrote:
> > On 12/06/2017 04:03 PM, Peter Maydell wrote:
> >> For instance, if a device gets a debug=1 transaction
> >> should it refuse to do things like read-clears-bits
> >> semantics or o
On 7 December 2017 at 21:20, Brijesh Singh wrote:
> On 12/06/2017 04:03 PM, Peter Maydell wrote:
>> For instance, if a device gets a debug=1 transaction
>> should it refuse to do things like read-clears-bits
>> semantics or other side-effects you wouldn't expect
>> of debugger accesses?
>>
>
> Sor
On 12/06/2017 04:03 PM, Peter Maydell wrote:
On 6 December 2017 at 20:03, Brijesh Singh wrote:
The debug attribute will be set when qemu attempts to access the guest
memory for debug (e.g memory access from gdbstub, memory dump commands
etc).
When guest memory is encrypted, the debug access w
On 6 December 2017 at 20:03, Brijesh Singh wrote:
> The debug attribute will be set when qemu attempts to access the guest
> memory for debug (e.g memory access from gdbstub, memory dump commands
> etc).
>
> When guest memory is encrypted, the debug access will need to go through
> the memory encr
The debug attribute will be set when qemu attempts to access the guest
memory for debug (e.g memory access from gdbstub, memory dump commands
etc).
When guest memory is encrypted, the debug access will need to go through
the memory encryption APIs.
Cc: Alistair Francis
Cc: Peter Maydell
Cc: Edg
