On 2024/02/27 19:29, Alex Bennée wrote:
Akihiko Odaki writes:
On 2024/02/27 19:08, Alex Bennée wrote:
Akihiko Odaki writes:
On 2024/02/27 1:56, Alex Bennée wrote:
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get functi
Akihiko Odaki writes:
> On 2024/02/27 19:08, Alex Bennée wrote:
>> Akihiko Odaki writes:
>>
>>> On 2024/02/27 1:56, Alex Bennée wrote:
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get function on
vCPU initiali
On 2024/02/27 19:08, Alex Bennée wrote:
Akihiko Odaki writes:
On 2024/02/27 1:56, Alex Bennée wrote:
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get function on
vCPU initialisation or during the translation phase.
We don'
Akihiko Odaki writes:
> On 2024/02/27 1:56, Alex Bennée wrote:
>> We can only request a list of registers once the vCPU has been
>> initialised so the user needs to use either call the get function on
>> vCPU initialisation or during the translation phase.
>> We don't expose the reg number to the
On 2024/02/27 1:56, Alex Bennée wrote:
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get function on
vCPU initialisation or during the translation phase.
We don't expose the reg number to the plugin instead hiding it behind
an
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get function on
vCPU initialisation or during the translation phase.
We don't expose the reg number to the plugin instead hiding it behind
an opaque handle. For now this is just the
