From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [Qemu-devel] [RFC] kvm: x86: export vCPU halted state to sysfs Date: Fri, 2 Feb 2018 15:38:46 -0200 Message-ID: <20180202173846.GN26425@localhost.localdomain> 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> <20180202172359.GA2591@work-vm> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 To: "Dr. David Alan Gilbert" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54680 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753231AbeBBRkE (ORCPT ); Fri, 2 Feb 2018 12:40:04 -0500 Content-Disposition: inline In-Reply-To: <20180202172359.GA2591@work-vm> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Feb 02, 2018 at 05:23:59PM +0000, Dr. David Alan Gilbert wrote: > * Eduardo Habkost (ehabkost@redhat.com) wrote: > > (CCing qemu-devel) > > > > 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é 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". > > > > > > > > Any also especially clarify the awful performance implications of running > > > > 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 ! > > > > > > Or deprecate it... > > > > 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. We would need a mechanism to safely walk the CPU list without the BQL, so I wouldn't bother trying to make a OOB-capable version of query-cpus unless really necessary. -- Eduardo