From: David Hildenbrand <david@redhat.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Matthew Wilcox <willy@infradead.org>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH v3 00/10] s390: PG_arch_1+folio cleanups for uv+hugetlb
Date: Thu, 9 May 2024 19:26:15 +0200 [thread overview]
Message-ID: <393b666b-3f28-439e-92e0-727c7bd529f3@redhat.com> (raw)
In-Reply-To: <20240509150459.12056-A-hca@linux.ibm.com>
On 09.05.24 17:04, Heiko Carstens wrote:
> On Wed, May 08, 2024 at 08:29:45PM +0200, David Hildenbrand wrote:
>> Rebased on 390x/features. Cleanups around PG_arch_1 and folio handling
>> in UV and hugetlb code.
>>
>> One "easy" fix upfront. Another issue I spotted is documented in [1].
>>
>> Once this hits upstream, we can remove HAVE_ARCH_MAKE_PAGE_ACCESSIBLE
>> from core-mm and s390x, so only the folio variant will remain.
>>
>> Compile tested, but not runtime tested with UV, I'll appreciate some
>> testing help from people with UV access and experience.
>>
>> [1] https://lkml.kernel.org/r/20240404163642.1125529-1-david@redhat.com
>>
>> v2 -> v3:
>> * "s390/uv: split large folios in gmap_make_secure()"
>> -> Spelling fix
>> * "s390/hugetlb: convert PG_arch_1 code to work on folio->flags"
>> -> Extended patch description
>
> Added Claudio's Reviewed-by from v2 to the third patch, and fixed a
> typo in the commit message of patch 9.
Ah, I missed on RB, thanks!
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-05-09 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 18:29 [PATCH v3 00/10] s390: PG_arch_1+folio cleanups for uv+hugetlb David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 01/10] s390/uv: don't call folio_wait_writeback() without a folio reference David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 02/10] s390/uv: gmap_make_secure() cleanups for further changes David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 03/10] s390/uv: split large folios in gmap_make_secure() David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 04/10] s390/uv: convert PG_arch_1 users to only work on small folios David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 05/10] s390/uv: update PG_arch_1 comment David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 06/10] s390/uv: make uv_convert_from_secure() a static function David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 07/10] s390/uv: convert uv_destroy_owned_page() to uv_destroy_(folio|pte)() David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 08/10] s390/uv: convert uv_convert_owned_from_secure() to uv_convert_from_secure_(folio|pte)() David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 09/10] s390/uv: implement HAVE_ARCH_MAKE_FOLIO_ACCESSIBLE David Hildenbrand
2024-05-08 18:29 ` [PATCH v3 10/10] s390/hugetlb: convert PG_arch_1 code to work on folio->flags David Hildenbrand
2024-05-09 15:04 ` [PATCH v3 00/10] s390: PG_arch_1+folio cleanups for uv+hugetlb Heiko Carstens
2024-05-09 17:26 ` David Hildenbrand [this message]
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=393b666b-3f28-439e-92e0-727c7bd529f3@redhat.com \
--to=david@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.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-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=willy@infradead.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).