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=ham 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 27C96C64E7B for ; Mon, 30 Nov 2020 20:26:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BB08E2073C for ; Mon, 30 Nov 2020 20:26:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="aPrWs/os" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388382AbgK3U0F (ORCPT ); Mon, 30 Nov 2020 15:26:05 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:56348 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727309AbgK3U0F (ORCPT ); Mon, 30 Nov 2020 15:26:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606767879; 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=aMj2PaNetiusUJ1P54tSAn6Nz2qIosd6leD0c3q65l0=; b=aPrWs/osTTbokH6biuq59PQIiRxUOvrB6V18jCp7eaqkKnI6gmS72onv7sPPOcFoWyDzgu UjsJu98cnB+v/amC0cr5vdctUukHzWFEsI9Ct6+4QNNSze2yGhKkxoem6aMRkBaTJbmcOJ mHeguWZZ4MnuZfpYA7eY8xBqNHHCcZE= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-94-LEVTkwzOOEOFAqNkaCzt4A-1; Mon, 30 Nov 2020 15:24:37 -0500 X-MC-Unique: LEVTkwzOOEOFAqNkaCzt4A-1 Received: by mail-ed1-f70.google.com with SMTP id g8so7383252edm.7 for ; Mon, 30 Nov 2020 12:24:36 -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=aMj2PaNetiusUJ1P54tSAn6Nz2qIosd6leD0c3q65l0=; b=LfhI140vjnc3vWN9EcBccL8N6q5Uv7KWhW5M+3NJCIu5eIQOFtkfc1gauRgoe14UUc hPSnT2WMhNs/W38EPNPY+SBuE2/vuZkGlStCeda8dY/qI/s7mUxzl5hVbdLEQe/wwlws QX05MnA2Bp9LA311ql+IltXJJHwK9tnsQmSAHXea4g84ApZAUSiHbUkf16pWuZF84ITO gVi2Z5v8Vkv8tK0EyJO0zv7cQXGkEhimw0UCHe3F5VPXRpO+1T8X1bjAETx8mlJtNIst GaL6CZIR/ClcFNdfP64dMginS9ryGzuQdlmEorKS8ujv2vJ16GBDsDE3BXkm0vE8F9yE CDqw== X-Gm-Message-State: AOAM5338lq2uz55bSsaJYvIZ/JCloXexFeQB3k0kOUrtuaxrc5QWS9JN bUm+aOukIYaNaz1oX6sWOB+huR62xqNeUu6YMLQH8BMHRoGuDHzvkeyQ8TFpvAJpRXCeoGuFgOJ o9KZeOcS5LmoA X-Received: by 2002:a05:6402:1508:: with SMTP id f8mr24584459edw.350.1606767875966; Mon, 30 Nov 2020 12:24:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJwcaweS7N9Z2p838MkPfnWxC0zGsgoIar9qD5b2KHOmOuPY1gh8wXFsvvvU96QcQwwD96dezQ== X-Received: by 2002:a05:6402:1508:: with SMTP id f8mr24584431edw.350.1606767875803; Mon, 30 Nov 2020 12:24:35 -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 q19sm8970227ejz.90.2020.11.30.12.24.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Nov 2020 12:24:34 -0800 (PST) Subject: Re: [RFC PATCH 00/35] SEV-ES hypervisor support To: Sean Christopherson Cc: Tom Lendacky , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, Jim Mattson , Joerg Roedel , Vitaly Kuznetsov , Wanpeng Li , Borislav Petkov , Ingo Molnar , Thomas Gleixner , Brijesh Singh , Xiaoyao Li , Isaku Yamahata References: <20200914225951.GM7192@sjchrist-ice> <20200916001925.GL8420@sjchrist-ice> <60cbddaf-50f3-72ca-f673-ff0b421db3ad@redhat.com> <8759948d-aa0b-3929-bda6-488b6788489a@redhat.com> From: Paolo Bonzini Message-ID: Date: Mon, 30 Nov 2020 21:24:33 +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: 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 20:35, Sean Christopherson wrote: >> Delayed interrupts are fine, since they are injected according to RVI and >> the posted interrupt descriptor. I'm thinking more of events (exceptions >> and interrupts) that caused an EPT violation exit and were recorded in the >> IDT-vectored info field. > Ah. As is, I don't believe KVM has access to this information. TDX-Module > handles the actual EPT violation, as well as event reinjection. The EPT > violation reported by SEAMRET is synthesized, and IIRC the IDT-vectoring field > is not readable. > > Regardless, is there an actual a problem with having a "pending" exception that > isn't reported to userspace? Obviously the info needs to be migrated, but that > will be taken care of by virtue of migrating the VMCS. No problem, I suppose we would just have to get used to not being able to look into the state of migrated VMs. Paolo