From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>, Sven Schnelle <svens@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Andrea Arcangeli <aarcange@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v3 2/2] s390/mm: re-enable the shared zeropage for !PV and !skeys KVM guests
Date: Mon, 15 Apr 2024 13:49:15 +0200 [thread overview]
Message-ID: <2a4ce6bc-49cc-45b8-ba15-82eb330f409f@linux.ibm.com> (raw)
In-Reply-To: <bd4d940e-5710-446f-9dc5-928e67920ec6@redhat.com>
Am 11.04.24 um 23:09 schrieb David Hildenbrand:
> On 11.04.24 18:37, Alexander Gordeev wrote:
>> On Thu, Apr 11, 2024 at 06:14:41PM +0200, David Hildenbrand wrote:
>>
>> David, Christian,
>>
>>> Tested-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>>
>> Please, correct me if I am wrong, but (to my understanding) the
>> Tested-by for v2 does not apply for this version of the patch?
>
> I thought I'd removed it -- you're absolutely, this should be dropped. Hopefully Christian has time to retest.
So I can confirm that this patch does continue fix the qemu memory consumption for a guest doing managedsave/start.
A quick check of other aspects seems to be ok. We will have more coverage on the base functionality as soon as it hits next(via Andrew) as our daily CI will pick this up for lots of KVM tests.
next prev parent reply other threads:[~2024-04-15 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:14 [PATCH v3 0/2] s390/mm: shared zeropage + KVM fixes David Hildenbrand
2024-04-11 16:14 ` [PATCH v3 1/2] mm/userfaultfd: don't place zeropages when zeropages are disallowed David Hildenbrand
2024-04-11 16:14 ` [PATCH v3 2/2] s390/mm: re-enable the shared zeropage for !PV and !skeys KVM guests David Hildenbrand
2024-04-11 16:37 ` Alexander Gordeev
2024-04-11 21:09 ` David Hildenbrand
2024-04-15 11:49 ` Christian Borntraeger [this message]
2024-04-15 13:14 ` Alexander Gordeev
2024-04-15 18:24 ` Alexander Gordeev
2024-04-15 19:14 ` David Hildenbrand
2024-04-16 6:37 ` Alexander Gordeev
2024-04-16 7:05 ` David Hildenbrand
2024-04-16 12:02 ` Christian Borntraeger
2024-04-16 13:41 ` David Hildenbrand
2024-04-18 13:09 ` Christian Borntraeger
2024-04-11 21:28 ` [PATCH v3 0/2] s390/mm: shared zeropage + KVM fixes Andrew Morton
2024-04-11 21:56 ` David Hildenbrand
2024-04-12 13:25 ` Alexander Gordeev
2024-04-17 12:46 ` Alexander Gordeev
2024-04-17 12:47 ` David Hildenbrand
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=2a4ce6bc-49cc-45b8-ba15-82eb330f409f@linux.ibm.com \
--to=borntraeger@linux.ibm.com \
--cc=aarcange@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gerald.schaefer@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-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=svens@linux.ibm.com \
/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