qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 00/29] first version of mcdstub


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH v2 00/29] first version of mcdstub
Date: Fri, 6 Oct 2023 11:50:55 +0200
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.1

On 6/10/23 11:05, Nicolas Eder wrote:
SUMMARY
=======

This patch-set introduces the first version of the mcdstub.
The mcdstub is a debug interface, which enables debugging QEMU
using the MCD (Multi-Core Debug) API.

[...]

neder (29):
   mcdstub initial commit, mcdstub file structure added
   TCP chardev added, handshake with TRACE32 working
   TCP packet handling added
   queries for resets and triggers added
   queries for memory spaces and register groups added
   query for registers added
   query data preparation improved
   shared header file added, used for TCP packet data
   memory and register query data now stored per core
   handler for resets added
   query for the VM state added
   handler for reading registers added
   handler for reading memory added
   handler for single step added
   adapting to the qemu coding style
   deleting the mcdd startup option
   handler for breakpoints and watchpoints added
   making step and go handlers core-specific
   adding trigger ID handling for TRACE32
   cp register read/write added
   switching between secure and non-secure memory added
   transitioning to unsinged integers in TCP packets and removing
     MCD-API-specific terms
   moved all ARM code to the ARM mcdstub and added now commom header file
   step and go handlers now propperly perform global operations
   Doxygen documentation added
   moved all mcd related header files into include/mcdstub
   MCD stub entry added to maintainers file
   added description to out-commented gdb function
   introducing the DebugClass. It is used to abstract the gdb/mcd
     set_stop_cpu function.

v2 is now reviewable, thank you!



reply via email to

[Prev in Thread] Current Thread [Next in Thread]