From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
svens@linux.ibm.com, gerald.schaefer@linux.ibm.com,
borntraeger@de.ibm.com
Subject: [PATCH v3 0/2] s390/pgtable: misc small improvements
Date: Fri, 26 Apr 2024 14:04:45 +0200 [thread overview]
Message-ID: <20240426120447.34318-1-imbrenda@linux.ibm.com> (raw)
This series has two small improvements for the s390 page tables. they
fix some small inconsistencies and missing things.
The first aligns the layout of large puds with that of large pmds;
there is no reason for the large pud read and write softbits to be
swapped compared to large pmds.
The second adds a few bits to _SEGMENT_ENTRY_BITS,
_SEGMENT_ENTRY_HARDWARE_BITS and _SEGMENT_ENTRY_HARDWARE_BITS_LARGE;
those bits are supposed to always be zero, the current code was working
correctly since those bits were being ignored and always left set to
zero. The patch also introduces _REGION3_ENTRY_HARDWARE_BITS and
_REGION3_ENTRY_HARDWARE_BITS_LARGE, for completeness, which are the
bitmasks of the hardware bits for normal puds and large puds.
v3->v2
* update patch description for the second patch
v2->v1
* add the missing pmd bits and _REGION3_ENTRY_HARDWARE_BITS
Claudio Imbrenda (2):
s390/pgtable: switch read and write softbits for puds
s390/pgtable: add missing hardware bits for puds, pmds
arch/s390/include/asm/pgtable.h | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.44.0
next reply other threads:[~2024-04-26 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 12:04 Claudio Imbrenda [this message]
2024-04-26 12:04 ` [PATCH v3 1/2] s390/pgtable: switch read and write softbits for puds Claudio Imbrenda
2024-04-26 12:04 ` [PATCH v3 2/2] s390/pgtable: add missing hardware bits for puds, pmds Claudio Imbrenda
2024-04-29 13:11 ` Heiko Carstens
2024-04-29 14:03 ` Claudio Imbrenda
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=20240426120447.34318-1-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).