Re: Arch info lost in "info cpus"

["Dr. David Alan Gilbert" <dgilbert@redhat.com>]

* Eduardo Habkost (ehabkost@redhat.com) wrote:
> On Mon, Sep 30, 2019 at 09:45:51AM +0100, Dr. David Alan Gilbert wrote:
> > * Sergio Lopez (slp@redhat.com) wrote:
> > > 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.
> > > 
> > > Is there an alternative way of getting something equivalent to what
> > > "info cpus" provided previously (in 2.10)?
> > 
> > Even the qemp equivalent, query-cpus is deprecated.
> > (Although we do call the underlying query-cpus in 'info numa' as well)
> 
> Why exactly it has to be deprecated?  We have use cases that
> require `query-cpus-fast` to exist, but I don't see why the
> existence of a command that returns extended information is a bad
> thing.
> 
> Having a command that synchronizes CPU state is even a
> requirement if we want to eventually implement "info registers"
> using QMP.

Yes, agreed; it was useful to have the non-syncing version
but I don't see a reason to remove the full-fat version.

Dave
 
> -- 
> Eduardo
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK