Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 16720C433DB for ; Wed, 10 Feb 2021 17:57:15 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8AD2B64E6F for ; Wed, 10 Feb 2021 17:57:14 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8AD2B64E6F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:40936 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l9tjl-0007xV-9k for qemu-devel@archiver.kernel.org; Wed, 10 Feb 2021 12:57:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58610) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l9tZt-0000SY-P4 for qemu-devel@nongnu.org; Wed, 10 Feb 2021 12:47:01 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:41029) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1l9tZp-0001KV-P0 for qemu-devel@nongnu.org; Wed, 10 Feb 2021 12:47:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612979216; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vH2NVhnTFBA65267aM7fkJ4YWs/AH7s2QFpyQalJNwk=; b=XIqBq57OAgeTISSZVg/Clit4qRq/HHznVCF6Jr47cBpXlnuvWpaz9PAy9WqBeL5Ntq/owF +67LDlkxXgM4vqYnmr6yReavfcnSFpK8igE3RzUwNsqkJFB/wM8ovRtGakhW7FqINNIwP7 xWowbdXA34d9Dcr7Oo3tyCW4Em7wyNo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-148-H7PDfYhgP26Uo4lO7jp4vA-1; Wed, 10 Feb 2021 12:46:54 -0500 X-MC-Unique: H7PDfYhgP26Uo4lO7jp4vA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6186B100A8E8 for ; Wed, 10 Feb 2021 17:46:53 +0000 (UTC) Received: from localhost (ovpn-114-196.rdu2.redhat.com [10.10.114.196]) by smtp.corp.redhat.com (Postfix) with ESMTP id 247D010013D7; Wed, 10 Feb 2021 17:46:53 +0000 (UTC) Date: Wed, 10 Feb 2021 12:46:52 -0500 From: Eduardo Habkost To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Subject: Re: [PATCH v4 00/19] i386: KVM: expand Hyper-V features early and provide simple 'hv-default=on' option Message-ID: <20210210174652.GE1420762@habkost.net> References: <20210210164033.607612-1-vkuznets@redhat.com> <20210210165606.GM1240644@redhat.com> MIME-Version: 1.0 In-Reply-To: <20210210165606.GM1240644@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ehabkost@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=63.128.21.124; envelope-from=ehabkost@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -33 X-Spam_score: -3.4 X-Spam_bar: --- X-Spam_report: (-3.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.568, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Paolo Bonzini , Vitaly Kuznetsov , Marcelo Tosatti , qemu-devel@nongnu.org, Igor Mammedov Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, Feb 10, 2021 at 04:56:06PM +0000, Daniel P. Berrangé wrote: > On Wed, Feb 10, 2021 at 05:40:12PM +0100, Vitaly Kuznetsov wrote: > > Changes since v3: > > - Make 'hv-default' override 'hv-*' options which were already set > > (e.g. 'hv-feature=on,hv-default' case) [Igor]. Make 'hv-passthrough' > > behave the same way. > > - Add "i386: be more picky about implicit 'hv-evmcs' enablement" patch to avoid > > enabling 'hv-evmcs' with hv-default/hv-passthrough when guest CPU lacks VMX. > > - Add "i386: support 'hv-passthrough,hv-feature=off' on the command line" patch > > to make 'hv-passthrough' semantics match the newly introduced 'hv-default'. > > - Add "i386: track explicit 'hv-*' features enablement/disablement" patch to > > support the above mentioned changes. > > - Expand qtest to check the above mentioned improvements. > > > > Original description: > > > > Upper layer tools like libvirt want to figure out which Hyper-V features are > > supported by the underlying stack (QEMU/KVM) but currently they are unable to > > do so. We have a nice 'hv_passthrough' CPU flag supported by QEMU but it has > > no effect on e.g. QMP's > > > > query-cpu-model-expansion type=full model={"name":"host","props":{"hv-passthrough":true}} > > > > command as we parse Hyper-V features after creating KVM vCPUs and not at > > feature expansion time. To support the use-case we first need to make > > KVM_GET_SUPPORTED_HV_CPUID ioctl a system-wide ioctl as the existing > > vCPU version can't be used that early. This is what KVM part does. With > > that done, we can make early Hyper-V feature expansion (this series). > > > > In addition, provide a simple 'hv-default' option which enables (and > > requires from KVM) all currently supported Hyper-V enlightenments. > > Unlike 'hv-passthrough' mode, this is going to be migratable. > > How is it going to be migratable if the semantics vary depending on > the host kernel KVM reporting features, because different kernels > will expose different features ? "all currently supported" in this context means "all features supported when the machine type was added", not "all features supported by the host kernel". -- Eduardo