On Mon, 13 Apr 2026 at 14:08, Philippe Mathieu-Daudé <[email protected]> wrote: > > With SMP configurations, using the 'current vCPU' under the > monitor isn't recommended, as it changes during runtime. Better > to specify which vCPU we want to monitor by its index. Deprecate > the default of 'info lapic', mentioning an argument is expected, > so we can remove this unpredictable behavior one day.
Is this really "unpredictable" ? This isn't the "current CPU" in the sense of "whatever is currently running", it's the "current CPU" in the sense of "whatever the user has set via the 'cpu' HMP command". You can certainly argue that a UI where you set the CPU via one command and then that's an implicit argument to various other commands is not ideal, but it's not unpredictable. The only time the CPU will change without user interaction is if they have set the monitor's current-CPU to one that is hot-unplugged (in which case it will reset to the first CPU), but the user is also likely to be in control of hot-unplug events anyway. -- PMM
