Aaron Lindsay OS writes:
> On Sep 06 20:31, Alex Bennée wrote:
>> Aaron Lindsay OS writes:
>>
>> > One thing I would find useful is the ability to access register values
>> > during an execution-time callback. I think the easiest way to do that
>> > generically would be to expose them via the
On Sep 06 20:31, Alex Bennée wrote:
> Aaron Lindsay OS writes:
>
> > One thing I would find useful is the ability to access register values
> > during an execution-time callback. I think the easiest way to do that
> > generically would be to expose them via the gdb functionality (like
> > Pavel's
Aaron Lindsay OS writes:
> One thing I would find useful is the ability to access register values
> during an execution-time callback. I think the easiest way to do that
> generically would be to expose them via the gdb functionality (like
> Pavel's earlier patchset did [1]), though that (curre
One thing I would find useful is the ability to access register values
during an execution-time callback. I think the easiest way to do that
generically would be to expose them via the gdb functionality (like
Pavel's earlier patchset did [1]), though that (currently) limits you to
the general-purpo
On 7/31/19 9:06 AM, Alex Bennée wrote:
> From: "Emilio G. Cota"
>
> Add the API first to ease review.
>
> Signed-off-by: Emilio G. Cota
> Signed-off-by: Alex Bennée
>
> ---
> v3
> - merge in changes to plugin install/reset/uninstall
> - split api file
> v4
> - s/is/it/
> - more docstr
