From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44876) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gZfb0-0003hc-Ur for qemu-devel@nongnu.org; Wed, 19 Dec 2018 12:25:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gZfau-0003FB-MH for qemu-devel@nongnu.org; Wed, 19 Dec 2018 12:25:20 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46066) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gZfas-0003AE-MM for qemu-devel@nongnu.org; Wed, 19 Dec 2018 12:25:14 -0500 From: Vitaly Kuznetsov In-Reply-To: <20181204180808.GC18284@habkost.net> References: <20181126135958.20956-1-vkuznets@redhat.com> <878t1chzj8.fsf@vitty.brq.redhat.com> <20181130183608.GQ18284@habkost.net> <871s6yy9st.fsf@vitty.brq.redhat.com> <20181204180808.GC18284@habkost.net> Date: Wed, 19 Dec 2018 18:25:06 +0100 Message-ID: <875zvpl98t.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH] i386/kvm: expose HV_CPUID_ENLIGHTMENT_INFO.EAX and HV_CPUID_NESTED_FEATURES.EAX as feature words List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Eduardo Habkost Cc: qemu-devel@nongnu.org, Richard Henderson , Marcelo Tosatti , Roman Kagan Eduardo Habkost writes: > On Mon, Dec 03, 2018 at 03:17:06PM +0100, Vitaly Kuznetsov wrote: >> Eduardo Habkost writes: > [...] >> > But note that we might still be able to move the existing >> > "hyperv_*" features to feature_word_info[].feat_names. We just >> > need to keep the same semantics (e.g. enable >> > HV_HYPERCALL_AVAILABLE automatically when some features are set). >> > >> > Maybe we can make some of the feature properties read-only. This >> > way we can give them meaningful names for debugging and error >> > messages, even if we don't want to make them configurable >> > directly. >> >> I'd suggest (if there are no objections of course) we do this separately >> from this patch. [...] > > Agreed. > Paolo, Eduardo, in case there are no concerns here, could you please pick this patch up? Thanks! -- Vitaly