Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1683290pxj; Wed, 19 May 2021 11:23:07 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxW/hH2yTSQ74qL2Y0KoxYwfK1jYXuJiDFTkDwoCWK2+psIPKAK9sa5xyP9xdlyLPIuhZD4 X-Received: by 2002:a5d:848a:: with SMTP id t10mr886507iom.68.1621448587177; Wed, 19 May 2021 11:23:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621448587; cv=none; d=google.com; s=arc-20160816; b=06IIcpYdnF7IeU2YuwcKAd3+loSmwSCsu5TzAmNmI32lV3DSb5dqJQ0YKu8XhMcC5x X8QAEgqLZuD+zc15LPgtCgBcvd5x5r2wJkFMtvrtJ/OOYmXVMwvQPojP/KXeFzW2lVCh 1G6d38XhDJUH0zkyTQ3cSS3iTKNvf06nY7z+rMrOBp0MUDyIH5qcjBuHqxGQDdeQYHfl ZsPNFjLRkTfV+0fC5j3ggs5Vw0V1S6i7RVIRaODnmoMP7w4XLaRM5hmbj/iCX6NkhpHo svuntGW5MejY8gvF8hZfij2HF6t1CwgJLLUVHLTVQEP+29N2p1xQGHn7p6S+1IzvxI5W faZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=kvhpwM9B7CK7kJ1xdIZJIHz3ygVOfl53rrG0Yt4bYqA=; b=ihvx7vFcFf7atOBp67eue5TMiNTjqDurf4BW6bZ7wCcTwjFzL012B8NVx+wNsTldtp /kjuekvtj7b0l3zHJTRiX7g+ARubjDp2nt5HkuUVtiZCc/2LtyPqMkd62hIN/q4xaL3I +YqhgiXGrtPLkCU3AVNyFFutVDnPhINM+ppYCD0omrOJImP7qszLyPuFdbko6RCMn8Fe ehIqUxjlisuWHequ/AtMsBGOM+31eeQ0CMtu8z/rDzHK4O+T3nSJOSD8Wi9oDH+gxMA4 9QbeyD40/Z2XmooKfZxYhGt8xz5AVTQpGcFdDTqsIAPsExN3qrCCqZte9Qbj/SEWoSCL 7Law== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=F0YNzu99; 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 w17si273865ilm.86.2021.05.19.11.22.53; Wed, 19 May 2021 11:23:07 -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=F0YNzu99; 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 S1350306AbhERQFm (ORCPT + 99 others); Tue, 18 May 2021 12:05:42 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:48208 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344604AbhERQFm (ORCPT ); Tue, 18 May 2021 12:05:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621353863; 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=kvhpwM9B7CK7kJ1xdIZJIHz3ygVOfl53rrG0Yt4bYqA=; b=F0YNzu99BkiK7ADZJivTo1cW6iEs6oeL5V8gHbPAV2wAkTvP+05HnUclvS2ejfOSIoTFmp phOXMqAKuqXClBa3CLUDLNSw4u59EjfpTDYwe0+GxSEcUV6XQF0S9NOoIh2MeK90U7pXpt +sOOrF2CuE5bsFZKBz4Apuaz8d4al1s= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-488-IwQiSyPUM-SHNa54cz5-nA-1; Tue, 18 May 2021 12:04:20 -0400 X-MC-Unique: IwQiSyPUM-SHNa54cz5-nA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 26CE6800D55; Tue, 18 May 2021 16:04:19 +0000 (UTC) Received: from gondolin.fritz.box (ovpn-113-74.ams2.redhat.com [10.36.113.74]) by smtp.corp.redhat.com (Postfix) with ESMTP id F00385DEAD; Tue, 18 May 2021 16:04:13 +0000 (UTC) Date: Tue, 18 May 2021 18:04:11 +0200 From: Cornelia Huck To: Claudio Imbrenda Cc: kvm@vger.kernel.org, borntraeger@de.ibm.com, frankja@linux.ibm.com, thuth@redhat.com, pasic@linux.ibm.com, david@redhat.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 00/11] KVM: s390: pv: implement lazy destroy Message-ID: <20210518180411.4abf837d.cohuck@redhat.com> In-Reply-To: <20210518173624.13d043e3@ibm-vm> References: <20210517200758.22593-1-imbrenda@linux.ibm.com> <20210518170537.58b32ffe.cohuck@redhat.com> <20210518173624.13d043e3@ibm-vm> Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 18 May 2021 17:36:24 +0200 Claudio Imbrenda wrote: > On Tue, 18 May 2021 17:05:37 +0200 > Cornelia Huck wrote: > > > On Mon, 17 May 2021 22:07:47 +0200 > > Claudio Imbrenda wrote: > > > This means that the same address space can have memory belonging to > > > more than one protected guest, although only one will be running, > > > the others will in fact not even have any CPUs. > > > > Are those set-aside-but-not-yet-cleaned-up pages still possibly > > accessible in any way? I would assume that they only belong to the > > in case of reboot: yes, they are still in the address space of the > guest, and can be swapped if needed > > > 'zombie' guests, and any new or rebooted guest is a new entity that > > needs to get new pages? > > the rebooted guest (normal or secure) will re-use the same pages of the > old guest (before or after cleanup, which is the reason of patches 3 > and 4) Took a look at those patches, makes sense. > > the KVM guest is not affected in case of reboot, so the userspace > address space is not touched. 'guest' is a bit ambiguous here -- do you mean the vm here, and the actual guest above?