From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bUDLL-00040B-G6 for qemu-devel@nongnu.org; Mon, 01 Aug 2016 09:33:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bUDLF-0001ha-U0 for qemu-devel@nongnu.org; Mon, 01 Aug 2016 09:33:19 -0400 Received: from mail-vk0-x233.google.com ([2607:f8b0:400c:c05::233]:36783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bUDLF-0001hO-8n for qemu-devel@nongnu.org; Mon, 01 Aug 2016 09:33:13 -0400 Received: by mail-vk0-x233.google.com with SMTP id n129so98813222vke.3 for ; Mon, 01 Aug 2016 06:33:13 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1470058019.3971.13.camel@redhat.com> References: <1469723896-28049-1-git-send-email-wei@redhat.com> <20160729065453.qq44y2hxohizk3yw@hawk.localdomain> <1470053099.3971.11.camel@redhat.com> <20160801130808.2igpsx52opi7ogvk@kamzik.localdomain> <1470058019.3971.13.camel@redhat.com> From: Peter Maydell Date: Mon, 1 Aug 2016 14:32:52 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH RFC 1/1] arm64: add an option to turn on/off vpmu support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrea Bolognani Cc: Andrew Jones , Wei Huang , qemu-arm , QEMU Developers , Shannon Zhao On 1 August 2016 at 14:26, Andrea Bolognani wrote: > On Mon, 2016-08-01 at 15:08 +0200, Andrew Jones wrote: >> > I'm not sure a warning is enough: if I start a guest and >> > explicitly ask for a PMU, I expect it to be there, or for >> > the guest not to start at all. How does x86 behave in this >> > regard? >> >> Peter had a good suggestion for this. We need to wrap the property >> addition in an arm_feature check like the has_el3 property. That will >> remove it from all cpu types that don't support it. > > Wouldn't that mean that you'd be unable to use > > -cpu foo,pmu=off > > if CPU model 'foo' doesn't support a PMU? I'd expect that > to work. The current precedent (has_el3) doesn't work like that: if foo isn't a CPU which can support EL3 then the property doesn't exist, and it's an error to try to set it. thanks -- PMM