From mboxrd@z Thu Jan 1 00:00:00 1970 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=-8.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 1772CC64E7B for ; Mon, 30 Nov 2020 11:05:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AED182084C for ; Mon, 30 Nov 2020 11:05:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Q2zjh7M4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729026AbgK3LFD (ORCPT ); Mon, 30 Nov 2020 06:05:03 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:37585 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727571AbgK3LFC (ORCPT ); Mon, 30 Nov 2020 06:05:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606734216; 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=ZM8hGmh0HYKlxLF1MQnAl60sUuzhNOm03zoIM5nbspw=; b=Q2zjh7M4DM2jC2XKQ92cbJVqUI1SjUgT5w9CATvyyjQwEkEVjYvwa7KjkhV1K66O7h8QX4 M0PUrdw5OYj+c5I+cWmKwskecVPZPwQqbkdJmbNBjF2/23baJhKvm5EkSqfd7QscHopqKa EJWx9TTEJiPDgrFCZAIP/VvnBiovtbg= Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-504-wnMmQHcBOZu-sMeWhYVtIw-1; Mon, 30 Nov 2020 06:03:34 -0500 X-MC-Unique: wnMmQHcBOZu-sMeWhYVtIw-1 Received: by mail-ej1-f70.google.com with SMTP id a8so5586806ejc.19 for ; Mon, 30 Nov 2020 03:03:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ZM8hGmh0HYKlxLF1MQnAl60sUuzhNOm03zoIM5nbspw=; b=eLrPrSCSsW2o+g83myLerZG84n9KdrLqUm7zpnRdwB7uAC7LqAipUj2pW2zQrAdPsb aitfdKUWGrsb7oK+kodGLe9fx0Vy5ilgPSen2zOoESzT/aGUIJ/9VG60Ezf1HwdvKGI1 s720RZq8s6zQTR7l5gbForq//+Yz7/DGgW7WqEyDAmvXRuZxhJnnUzeW/CHBB2WC4vNS sOlW7J1GOG0uuBPilotrNx/iAalTHVnWXJYRCE2UZtDsauQDa8xCHfB/mF7NBoDNV3pV 65E59zJsYmLAVjleUh3tQ9zje0TKjI5TyuihN0gZDt0nEeMU4BamWcGC6oEU39FixnIn 3FOw== X-Gm-Message-State: AOAM5337SARmFNA7hI5zsgbRPCLZGehcqqluYj++MgunNoCGEDQs+Q1y 1lyfRn+K3ZbuzKJXhiw84uWCZ0daJrUUJE0k6mx7EXuTkHlZXgO/NjrJomW4MCzdLSd1/heRNFH HxqmVMoWSryFT X-Received: by 2002:a17:906:4049:: with SMTP id y9mr9370142ejj.442.1606734212961; Mon, 30 Nov 2020 03:03:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJwk9wPoUjFt1o1YFgMXhH50p+0HXcZVHi6I26KKsHXbrcGubZdrjbVI/wFYANXa1rmhlF9rSQ== X-Received: by 2002:a17:906:4049:: with SMTP id y9mr9370101ejj.442.1606734212647; Mon, 30 Nov 2020 03:03:32 -0800 (PST) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id da9sm270504edb.13.2020.11.30.03.03.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Nov 2020 03:03:31 -0800 (PST) Subject: Re: [PATCH RFC 01/39] KVM: x86: fix Xen hypercall page msr handling To: David Woodhouse , Sean Christopherson , Joao Martins Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Ankur Arora , Boris Ostrovsky , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org References: <20190220201609.28290-1-joao.m.martins@oracle.com> <20190220201609.28290-2-joao.m.martins@oracle.com> <20190222013008.GG7224@linux.intel.com> <44b102eb-ea74-7f19-3f4a-41dfc298d372@redhat.com> <188a300f8314dd30a3a71857f63f144a3ce69950.camel@infradead.org> From: Paolo Bonzini Message-ID: <51b7771a-0b76-37e3-a80b-e372a7467aca@redhat.com> Date: Mon, 30 Nov 2020 12:03:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <188a300f8314dd30a3a71857f63f144a3ce69950.camel@infradead.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 30/11/20 11:39, David Woodhouse wrote: > ... except that's a bit icky because that trick of falling through to > the default case only works for *one* case statement. And more to the > point, the closest thing I can find to a 'kvm_hyperv_enabled()' flag is > what we do for setting the HV_X64_MSR_HYPERCALL_ENABLE flag... which is > based on whether the hv_guest_os_id is set, which in turn is done by > writing one of these MSRs You can use CPUID too (search for Hv#1 in leaf 0x40000000)? Paolo > I suppose we could disable them just by letting Xen take precedence, if > kvm->arch.xen_hvm_config.msr == HV_X64_MSR_GUEST_OS_ID. But that's > basically what Joao's patch already does. It doesn't disable the > *other* Hyper-V MSRs except for the one Xen 'conflicts' with, but I > don't think that matters.