Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp3444944pxy; Tue, 4 May 2021 02:18:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxo+vxRcpTkexjUEv5WrgYiDVIRRUoR6jIiaGE3EHkJ/LgwTkepaHka07kOHRBOvGAkYs5L X-Received: by 2002:a63:4607:: with SMTP id t7mr15700461pga.269.1620119890966; Tue, 04 May 2021 02:18:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620119890; cv=none; d=google.com; s=arc-20160816; b=i727v7WvJFZwoGdp7noYFY2PEt2ebUULefEh7Mt1rGFOnJS9m88qaX5guzjypmnh8O MU0Fea17mk4FvoCI9UqRXCEWuqrhML4Qf8/Y6AcsYlXtxuYnm5jJdpLM9YX5VHit+ef3 2lkl+fCTmN1yEVhpdhhODqhSdxTiDytDnlbOsY2dZi+51KqPU2FMHXhcvMGLoP1sjkqa RWRHaV4t1EBfxvmimJO6y1y+0xHYlKM2ICvdE3gNx9BQrJMO+aEB/002+/fpWDWSelAl 4N0s5Jjfr0YZZcEp0ExB2kxrW92v23cgTm0RRKVKJxYCsM4/THSQ6nS5rF893/Odu3UE pCbg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=fnZe71Z03G+GeuFZEGo29g9lHgOD/bxvNQsCK+sXxoI=; b=euDezfEJPzViyLDUTqejwIcyH1zcDiwrYRtqn5Mp6fMqxZoURctfdDVINu8rh9o5BD PyrLxc5Gz3b/62PkutkorU21H1kWAP05wcKTgymmTCiMwuQ1RYFlsQcKD+9HwyyPrVoY 8zu4HXRgEWP6E/janJoluBnLM9R3KAqehKNp5QrodvENAgUKDC/5Mp2ivfUrIzj/oqCV H/U/6nEqT+LphPd9uSAC3k+dIqiKzVYqPF/jd01iFVnSOKl6lnUu/BtEMHCksWxAfTtG U6V83GYEOSbZ5ZFJDd9lOrsIGotjhMJhTukq61oSh6oaon5IVB1A1GtZMu9Fu7xoSjLY 3rDA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gIDXP94z; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z17si2825897plg.432.2021.05.04.02.17.58; Tue, 04 May 2021 02:18:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gIDXP94z; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230048AbhEDIHt (ORCPT + 99 others); Tue, 4 May 2021 04:07:49 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:44445 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230025AbhEDIHt (ORCPT ); Tue, 4 May 2021 04:07:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620115614; 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=fnZe71Z03G+GeuFZEGo29g9lHgOD/bxvNQsCK+sXxoI=; b=gIDXP94z9cT4wFr5kGlb3BA833QAY9lY1QO3EkpZzDYye9MCMnIzXzJV+zWEC7QZQYdzt9 sCygbn51s73i/BIzLzPogcrp2rU97Id3vO/Hhjtt2hQ85oUTnkNMumwdEKTAGVravtJqmL 8JOyxNw+nRVXI20cZ1QeqcnB6JTts2o= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-200-kH86TOr8OAi-EplwS0SJIA-1; Tue, 04 May 2021 04:06:50 -0400 X-MC-Unique: kH86TOr8OAi-EplwS0SJIA-1 Received: by mail-ed1-f71.google.com with SMTP id f8-20020a0564020688b029038840895df2so6023770edy.17 for ; Tue, 04 May 2021 01:06:50 -0700 (PDT) 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=fnZe71Z03G+GeuFZEGo29g9lHgOD/bxvNQsCK+sXxoI=; b=bpbeUvd8IIGKliCvPJ88QJyMgvYroFJdsJuHtekms8uEaSH870StT6qI/9ERYa2+km 7N1ggmZOWkcZ5OrGy7t+DlTGMuBW13MVgJVXBaNmbNt/yZALFxhInGrlwVhp96FvsyGP ivJxFY0bmLO9idrs1dQsINvm+2RC1JrODHDCWvJldO2xCM/DlPsE1auXXF8BAz7cLW1B KVvXOaEh/B4pGPNTQ5qq7XqgThnutuVAkwrAoCVevhKvGdTSGP5bv6o6UnNX59PhwIhZ A2+pr1kCwNS5LC7obwwVdg0fArYj+fiCSxMtOOCnr9kOXBTPqk8ufeuILLITKE7ocrZp YjJw== X-Gm-Message-State: AOAM531RFrYXj7C652mqemc8mNqC8OmAu8BC1LXn5vIC7xm5VOFVFgms FFhQXVoMrSQU2+y0mKeObFV7fgjWMCnGI2fEXz+73/HhgJoeCMc0+41dBd0ZkNZBSlJ/8/4cqlQ 3XxEwM8ReNHBHmG0WL56Z2UxM X-Received: by 2002:a17:907:3e27:: with SMTP id hp39mr20899580ejc.373.1620115609282; Tue, 04 May 2021 01:06:49 -0700 (PDT) X-Received: by 2002:a17:907:3e27:: with SMTP id hp39mr20899564ejc.373.1620115609117; Tue, 04 May 2021 01:06:49 -0700 (PDT) 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 v14sm166212edx.5.2021.05.04.01.06.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 04 May 2021 01:06:48 -0700 (PDT) Subject: Re: [PATCH v3 2/2] KVM: X86: Introduce KVM_HC_PAGE_ENC_STATUS hypercall To: Steve Rutherford Cc: Sean Christopherson , LKML , KVM list , Joerg Roedel , Brijesh Singh , Tom Lendacky , Ashish Kalra , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Borislav Petkov , X86 ML References: <20210429104707.203055-1-pbonzini@redhat.com> <20210429104707.203055-3-pbonzini@redhat.com> From: Paolo Bonzini Message-ID: <7c8f388c-1c0e-1fa8-24a5-46ffd40f8b24@redhat.com> Date: Tue, 4 May 2021 10:06:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/05/21 01:22, Steve Rutherford wrote: > As far as I know, because of MSR filtering, the only "code" that needs > to be in KVM for MSR handling is a #define reserving the PV feature > number and a #define for the MSR number. > > Arguably, you don't even need to add the new PV bits to the supported > cpuid, since MSR filtering is really what determines if kernel support > is present. Not only I don't need to do that, I must not. :) >> At this point I very much prefer the latter, which is basically Ashish's >> earlier patch. > > The minor distinction would be that if you expose the cpuid bit to the > guest you plan on intercepting the MSR with filters, and would not > need any handler code in the kernel. Yep, and it's not a minor distinction after all (especially from the PoV of the guy who actually ends up maintaining the code, i.e. me), so that's what I'm going for. Paolo