From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, borntraeger@de.ibm.com,
gor@linux.ibm.com, imbrenda@linux.ibm.com, kvm@vger.kernel.org,
david@redhat.com, hca@linux.ibm.com
Subject: Re: [PATCH v2 1/2] s390x: uv: Add destroy page call
Date: Tue, 8 Sep 2020 08:28:49 +0200 [thread overview]
Message-ID: <20200908082849.7e4a661d.cohuck@redhat.com> (raw)
In-Reply-To: <20200907124700.10374-2-frankja@linux.ibm.com>
On Mon, 7 Sep 2020 08:46:59 -0400
Janosch Frank <frankja@linux.ibm.com> wrote:
> We don't need to export pages if we destroy the VM configuration
> afterwards anyway. Instead we can destroy the page which will zero it
> and then make it accessible to the host.
>
> Destroying is about twice as fast as the export.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> arch/s390/include/asm/uv.h | 7 +++++++
> arch/s390/kernel/uv.c | 20 ++++++++++++++++++++
> arch/s390/mm/gmap.c | 2 +-
> 3 files changed, 28 insertions(+), 1 deletion(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2020-09-08 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 12:46 [PATCH v2 0/2] s390x: pv: Fixes and improvements Janosch Frank
2020-09-07 12:46 ` [PATCH v2 1/2] s390x: uv: Add destroy page call Janosch Frank
2020-09-07 17:59 ` Thomas Huth
2020-09-08 6:28 ` Cornelia Huck [this message]
2020-09-07 12:47 ` [PATCH v2 2/2] s390x: Add 3f program exception handler Janosch Frank
2020-09-08 6:39 ` Cornelia Huck
[not found] ` <202009080542.UHmgfE5u%lkp@intel.com>
2020-09-08 7:53 ` Heiko Carstens
2020-09-08 13:05 ` [PATCH v3] " Janosch Frank
2020-09-08 13:06 ` Heiko Carstens
2020-09-08 13:09 ` Janosch Frank
2020-09-08 13:18 ` Heiko Carstens
2020-09-08 13:10 ` Christian Borntraeger
2020-09-08 7:58 ` [PATCH v2 2/2] " kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200908082849.7e4a661d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox