Re: [PULL 17/22] plugins: add an API to read registers

2024-01-22 Thread Alex Bennée
Akihiko Odaki writes: > On 2024/01/18 20:38, Alex Bennée wrote: >> Akihiko Odaki writes: >> >>> On 2024/01/16 19:48, 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 initial

Re: [PULL 17/22] plugins: add an API to read registers

2024-01-21 Thread Akihiko Odaki
On 2024/01/18 20:38, Alex Bennée wrote: Akihiko Odaki writes: On 2024/01/16 19:48, 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

Re: [PULL 17/22] plugins: add an API to read registers

2024-01-18 Thread Alex Bennée
Akihiko Odaki writes: > On 2024/01/16 19:48, 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 th

Re: [PULL 17/22] plugins: add an API to read registers

2024-01-17 Thread Akihiko Odaki
On 2024/01/16 19:48, 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 a

[PULL 17/22] plugins: add an API to read registers

2024-01-16 Thread Alex Bennée
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. This allows for a bit of