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=-4.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 02A26C11F64 for ; Mon, 28 Jun 2021 22:52:30 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CDA4161D00 for ; Mon, 28 Jun 2021 22:52:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234779AbhF1Wyy (ORCPT ); Mon, 28 Jun 2021 18:54:54 -0400 Received: from forward100j.mail.yandex.net ([5.45.198.240]:48682 "EHLO forward100j.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234674AbhF1Wyw (ORCPT ); Mon, 28 Jun 2021 18:54:52 -0400 Received: from iva5-8cd627e71aff.qloud-c.yandex.net (iva5-8cd627e71aff.qloud-c.yandex.net [IPv6:2a02:6b8:c0c:7b87:0:640:8cd6:27e7]) by forward100j.mail.yandex.net (Yandex) with ESMTP id AC42350E077F; Tue, 29 Jun 2021 01:52:22 +0300 (MSK) Received: from iva6-2d18925256a6.qloud-c.yandex.net (iva6-2d18925256a6.qloud-c.yandex.net [2a02:6b8:c0c:7594:0:640:2d18:9252]) by iva5-8cd627e71aff.qloud-c.yandex.net (mxback/Yandex) with ESMTP id vwpJntTCq3-qLIK4PAV; Tue, 29 Jun 2021 01:52:22 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1624920742; bh=T9G7dRz6CqpcTUA26MtrxR6s3izNdLMGGegdrGiyyXw=; h=In-Reply-To:From:Date:References:To:Subject:Message-ID:Cc; b=npMWpAv8OTz7oEH5MujaWYP98mdoqsvlzOQxPjphAE27YNEdmIeZnePmRw+ogWlpR arirb9ylhu2DL/iGtgVXOQbUjJFVsijRsFg8G/h0AYNLIpCZSfnBW2bvTQ0Lgb2Z37 cv6fhOuHQJ2ES2nyNWDmPAJcxLdklFMxrZwHDxzw= Authentication-Results: iva5-8cd627e71aff.qloud-c.yandex.net; dkim=pass header.i=@yandex.ru Received: by iva6-2d18925256a6.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id DCRaTQApGE-qK2qjSOO; Tue, 29 Jun 2021 01:52:21 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) Subject: Re: [PATCH] KVM: X86: Fix exception untrigger on ret to user To: Jim Mattson Cc: Paolo Bonzini , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H. Peter Anvin" , kvm@vger.kernel.org References: <20210627233819.857906-1-stsp2@yandex.ru> From: stsp Message-ID: Date: Tue, 29 Jun 2021 01:52:19 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org 29.06.2021 01:35, Jim Mattson пишет: > How long are you willing to defer the EINTR? What if you're running at > the target of a live migration, and the guest's IDT page needs to be > demand-fetched over the network? It may be quite some time before you > can actually deliver that exception. OK, understood, thank you. I wonder how many other non-atomic things are there in KVM, but probably that doesn't matter much, if run->ready_for_injection covers them all at once...