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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC256C433FE for ; Wed, 2 Nov 2022 19:00:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231737AbiKBTAB (ORCPT ); Wed, 2 Nov 2022 15:00:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55160 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231873AbiKBS7f (ORCPT ); Wed, 2 Nov 2022 14:59:35 -0400 Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 524BE140A2 for ; Wed, 2 Nov 2022 11:59:18 -0700 (PDT) Received: by mail-pf1-x429.google.com with SMTP id g62so17219660pfb.10 for ; Wed, 02 Nov 2022 11:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=ozfijFL6oisXA0Rywz9UlgsF3nC4xugKejf2BN/hMCQ=; b=WjSssknYHNDKNXVAC4m9Z+qWXUWoIjb1R2WF95ECyXQqK9TnGf9BQGsa8R9v5iDyCO r1g/IWi7jmIjmD6bG/mUPj9AeS0CYRsAdUVGcSIYibRi+zcuRcKQicApfrpp6qvDRM9M R5DUTmbCEO/GCAZQvPNVi1CzszkRIayc1PMse6Zv0JgaZACrOrQNXkJ8G+4zOjgXV8rG v8qgLotiQyEJpBz5emzw8XXTUrO8iGmIdNQVEQIW+jGYp821AqYfC+q4sk22c9nF6evs TyVDiFoijZCCo9XMliQtfGnUsrJ1vRlABl+C7ziz4tgiflT2Y50XwhC41K/QKF2ToH/a PwCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ozfijFL6oisXA0Rywz9UlgsF3nC4xugKejf2BN/hMCQ=; b=T6Yb6EPQTea6fl9mxGj0ATQ8aUEkiFnRoV8Ox0CSjYMZOQc9Wily9JsHPTdiPGKRUN m8SVKhqwclJZyPo5IKbFKs+wYdk1jsTnnS0vurheKoQrBpI8CHncbsosgi12riQ+PaPC 5mpePW6acGAJPNWcnLrR/UbCPSpgjRDIZjMMydLSVZYO6OWj0jLm5wD61C7OLM00LB+f lkMMMf7ks6/ZXscGbX1DRVi0QW3I21dRy13SLEuRd27e1Fg63uZwaA9P9R+tC1snna1t XimCQ4l1ZMZu7maXpGcoxGOZ611Q4ysTXES2YrnTU6gNNDbrrd7us1Qjrtei2cwCPaqs dIvg== X-Gm-Message-State: ACrzQf2wTH3jiGCJFL6AN3k/dBlUHJenPMNKDJlqq9sZN5ZGHSKncLhp BQBCOd3QM5qOhq8yt03JvdeFJn/6lvn4Ww== X-Google-Smtp-Source: AMsMyM7pZQ31wit4DKIfpjFcUOZdw5alHxSslQKpojZbI31esAaJxU+LL0AH44hmWerSfc/wAQ4JBA== X-Received: by 2002:a63:1041:0:b0:46e:c6eb:22ee with SMTP id 1-20020a631041000000b0046ec6eb22eemr22767269pgq.442.1667415557761; Wed, 02 Nov 2022 11:59:17 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id mg7-20020a17090b370700b0020d3662cc77sm1786677pjb.48.2022.11.02.11.59.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 02 Nov 2022 11:59:17 -0700 (PDT) Date: Wed, 2 Nov 2022 18:59:13 +0000 From: Sean Christopherson To: Paolo Bonzini Cc: isaku.yamahata@intel.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Thomas Gleixner , Marc Zyngier , Will Deacon , isaku.yamahata@gmail.com, Kai Huang , Chao Gao , Atish Patra , Shaokun Zhang , Daniel Lezcano , Huang Ying , Huacai Chen , Dave Hansen , Borislav Petkov Subject: Re: [PATCH v5 00/30] KVM: hardware enable/disable reorganize Message-ID: References: <38d7f8af-3cf0-0d5b-3fda-a2a3326f7b28@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <38d7f8af-3cf0-0d5b-3fda-a2a3326f7b28@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 02, 2022, Paolo Bonzini wrote: > On 10/14/22 06:04, Sean Christopherson wrote: > > Good news (from a certain point of view): > > The reason that the "generic h/w enabling" doesn't help much is because after sorting > > out the myriad issues in KVM initialization, which is even more of a bug-ridden mess > > than I initially thought, kvm_init() no longer has_any_ arch hooks. All the compat > > checks and whatnot are handled in x86, so tweaking those for TDX should be easier, > > or at the very least, we should have more options. > > > > Sorting everything out is proving to be a nightmare, but I think I have the initial > > coding done. Testing will be fun. It'll likely be next week before I can post > > anything. > > Hi Sean, > > is this the same series that you mentioned a couple hours ago in reply to > Isaku? Yep.