Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp473985pxj; Fri, 14 May 2021 08:00:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzk8k1Vtb0PS08Kzd9d+gVMM86GiOGm/MrQbAJ/zYFE9TsyNDrIxU9nLNTERiWIBOaG1dIM X-Received: by 2002:a17:906:2dcd:: with SMTP id h13mr3575099eji.41.1621004423490; Fri, 14 May 2021 08:00:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621004423; cv=none; d=google.com; s=arc-20160816; b=J+KW5hnKaggGzCZQeqq6sW60+kf0oHlCZbUki0Oa1XMO9uoacgb6sktGymrppXTOej ByLccBFUqhi5BiZk+zQMikxBzpu97uhGu4pFCOnpSMTnAyPCeOKQYDLcm7Au/YR9dPKk YtphPLxk7TRDsXN34itWc9fkAfNU6ZSutAFyuHn+kyJe9sFKMm0FAWy23DwF3SYcoiY7 d44M+hcVjk5nip92vLadB31qRyt5GyoGLuVK2k46ZVDXQTttRw8R8CNqUzQFXj/RcRho WC0h5JpE/a9ChYGRiDkGUPls04RG/KTeMzUeBLnoTLKeHGadCIYpsQKKDaxcSD2pTXF2 0ZhA== 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=FE60io7r9QIWZ+2HbVfZ7x5W1zNu5ip9FIeLOvLYCnU=; b=Ibzsi5oCvkck9aIuVKoJ+xIhEOUbcHEskRiUyo/5K4CzeYjUuOEtcELy0dwyxbSGZ5 dDW2UsWpBo7k1h6K3vQmX3IjrrgFaKYWLL2svneno42UXVMSEeS/BWSc7SupmvxthHvM s6sp7puJen86no+Vxck36WzL2HLL/GazggXjAB5IxRpQYdgQeFqhQeI6Y021T+bj01U8 L+qv0QjSxcihdEO9J7GyAmMHabDB7IarTQDUTZA4SdpGpB7gG1xJ7qD26ifD0z53If5U a/rsMEmB+p98d2ECk42M2Py98GPHG1EfhCduBE5+1ylh7aa3Dl8qkmxuKdBz+rYwS180 IyAw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hKnglwiQ; 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 ay13si1880704edb.577.2021.05.14.07.59.56; Fri, 14 May 2021 08:00:23 -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=hKnglwiQ; 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 S233383AbhENIEg (ORCPT + 99 others); Fri, 14 May 2021 04:04:36 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:27478 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233358AbhENIEf (ORCPT ); Fri, 14 May 2021 04:04:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620979404; 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=FE60io7r9QIWZ+2HbVfZ7x5W1zNu5ip9FIeLOvLYCnU=; b=hKnglwiQ/e1b+A81eWrL0WKkejcnMbR4/NtxDKvNPEeM7S5S8BvV7AjvvomVxc4kSRA9Yy MPbrZ+QelYFxAi9CIOv3Cn21UuX7gWw4wMWqpZsqXbw6Zky+MqYSJywU1OtYXT6Q/9MklW sAhXOjjNKOIwO6eQRv8i7VqqmCxnskc= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-598-Wr6q-rDfO-24Ia1SWszVCw-1; Fri, 14 May 2021 04:03:22 -0400 X-MC-Unique: Wr6q-rDfO-24Ia1SWszVCw-1 Received: by mail-ej1-f69.google.com with SMTP id cs18-20020a170906dc92b02903a8adf202d6so8298667ejc.23 for ; Fri, 14 May 2021 01:03:22 -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=FE60io7r9QIWZ+2HbVfZ7x5W1zNu5ip9FIeLOvLYCnU=; b=U5W+lSzQrHzbWHS5laEg2ibYga1T4Kp9yyaBo9by137pZAAkKpJ+pwcl34rHyCFO4e 4IFPhI9KwTPONA/oL9o8svKVW/pqRkOFbC1sTTlNMUsDTUYMYkQ+o8ejvKiA5ZX8jdNf dswiBxKbV9b2d7ukh/7BFXsmOjdO93DpRTPqh7/u7OnGQ+YYaAD1TurEPRU92lpbV3Xt F/kvImN4cH/NX+/JfQhRs0IpPtkT0QmsXPnSL5TAboMRNTlq71B3Btki0x08invEvwhk KPo80iYjZ0scYrfpOdxMTDr3cAh/DDP5X8IWVB85ZmntNLddBKmCFjZkdJ3iD4m7kwXb 9XHw== X-Gm-Message-State: AOAM531jvWDzMQHPAkbMKkO5Q5Mj9A6ntamFBQnOihnyb65/b41c1jfN UuK/1rqHSOP8Ow2109dHo/DnYLnkFdWOBYFlGYObJlftVcb34j3B+n9aiqbGxl9FHpfab1wtmfV 6goDDo7fuidx85qWgJRjnydA7 X-Received: by 2002:aa7:c510:: with SMTP id o16mr54472585edq.310.1620979401431; Fri, 14 May 2021 01:03:21 -0700 (PDT) X-Received: by 2002:aa7:c510:: with SMTP id o16mr54472550edq.310.1620979401260; Fri, 14 May 2021 01:03:21 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:63a7:c72e:ea0e:6045? ([2001:b07:6468:f312:63a7:c72e:ea0e:6045]) by smtp.gmail.com with ESMTPSA id w19sm4020166edd.52.2021.05.14.01.03.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 14 May 2021 01:03:20 -0700 (PDT) Subject: Re: [PATCH v2 2/4] mm: x86: Invoke hypercall when page encryption status is changed To: Borislav Petkov , Ashish Kalra Cc: seanjc@google.com, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, joro@8bytes.org, thomas.lendacky@amd.com, x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, srutherford@google.com, venu.busireddy@oracle.com, brijesh.singh@amd.com References: <20210513043441.GA28019@ashkalra_ubuntu_server> From: Paolo Bonzini Message-ID: <7ac12a36-5886-cb07-cc77-a96daa76b854@redhat.com> Date: Fri, 14 May 2021 10:03:18 +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 14/05/21 09:33, Borislav Petkov wrote: > Ok, so explain to me how this looks from the user standpoint: she starts > migrating the guest, it fails to lookup an address, there's nothing > saying where it failed but the guest crashed. > > Do you think this is user-friendly? Ok, so explain to me how this looks from the submitter standpoint: he reads your review of his patch, he acknowledges your point with "Yes, it makes sense to signal it with a WARN or so", and still is treated as shit. Do you think this is friendly? Paolo