On Mon, Sep 30, 2019 at 12:22:22PM +0200, Sergio Lopez wrote: > > Alex Bennée <alex.ben...@linaro.org> writes: > > > Sergio Lopez <s...@redhat.com> writes: > > > >> Hi, > >> > >> Commit 137b5cb6ab565cb3781d5337591e155932b4230e (hmp: change > >> hmp_info_cpus to use query-cpus-fast) updated the "info cpus" commit to > >> make it more lightweight, but also removed the ability to get the > >> architecture specific status of each vCPU. > >> > >> This information was really useful to diagnose certain Guest issues, > >> without the need of using GDB, which is more intrusive and requires > >> enabling it in advance. > > > > You can always enable the gdbserver from the HMP when you need it. > > > >> Is there an alternative way of getting something equivalent to what > >> "info cpus" provided previously (in 2.10)? > > > > info registers > > > > should give you a full dump of the CPU state including the PC. > > > > Both methods are less convenient that what we had before. Perhaps it'd > be reasonable adding a flag to "info cpus" to give users the options of > having the same behavior as before?
Is "info registers -a" less convenient because it prints too much information, or because it doesn't print the active CPU indicator and thread_id? -- Eduardo
