From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60316) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehf5V-00088p-QZ for qemu-devel@nongnu.org; Fri, 02 Feb 2018 12:26:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehf4R-0005y9-9w for qemu-devel@nongnu.org; Fri, 02 Feb 2018 12:25:21 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49194) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ehf4Q-0005vS-GJ for qemu-devel@nongnu.org; Fri, 02 Feb 2018 12:24:14 -0500 Date: Fri, 2 Feb 2018 17:23:59 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20180202172359.GA2591@work-vm> References: <20180201125441.2f5b4fdd@redhat.com> <20180201201514.GB660@flask> <20180201202649.GG26425@localhost.localdomain> <20180202141554.GH26425@localhost.localdomain> <20180202141938.GJ15403@redhat.com> <20180202092159.48d9bd4c@redhat.com> <20180202145014.GI26425@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20180202145014.GI26425@localhost.localdomain> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC] kvm: x86: export vCPU halted state to sysfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Luiz Capitulino , Peter Krempa , kvm@vger.kernel.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , libvir-list@redhat.com, Markus Armbruster , qemu-devel@nongnu.org, Viktor Mihajlovski , Christian Borntraeger , John Ferlan , pbonzini@redhat.com * Eduardo Habkost (ehabkost@redhat.com) wrote: > (CCing qemu-devel) >=20 > On Fri, Feb 02, 2018 at 09:21:59AM -0500, Luiz Capitulino wrote: > > On Fri, 2 Feb 2018 14:19:38 +0000 > > Daniel P. Berrang=E9 wrote: > > > On Fri, Feb 02, 2018 at 12:15:54PM -0200, Eduardo Habkost wrote: > [...] > > > > It would be also interesting to update QEMU QMP documentation to > > > > clarify the arch-specific semantics of "halted". =20 > > >=20 > > > Any also especially clarify the awful performance implications of r= unning > > > this particular query command. In general I would not expect query-= xxx > > > monitor commands to interrupt all vcpus, so we should clearly warn = about > > > this ! > >=20 > > Or deprecate it... >=20 > We could deprecate the expensive fields on query-cpus, and move > them to a more expensive query-cpu-state command. I believe most > users of query-cpus are only interested in qom_path, thread_id, > and topology info. Would that data be available without the bql? I ask because if it is then a small advantage to having a separate command is that the command could be marked OOB with Peter's new series and never take the lock. Dave > Markus, Eric: from the QAPI point of view, is it OK to remove > fields between QEMU versions, as long as we follow our > deprecation policy? >=20 > --=20 > Eduardo >=20 -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK