On Fri, 26 Apr 2024 10:57:14 +0200 Heiko Carstens <hca@xxxxxxxxxxxxx> wrote: > On Thu, Apr 25, 2024 at 03:05:55PM +0200, Claudio Imbrenda wrote: > > For completeness, introduce _REGION3_ENTRY_HARDWARE_BITS_LARGE, > > containing the hardware bits used for large puds. > > > > Signed-off-by: Claudio Imbrenda <imbrenda@xxxxxxxxxxxxx> > > --- > > arch/s390/include/asm/pgtable.h | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h > > index 3da2995fd196..5c0f840eee2a 100644 > > --- a/arch/s390/include/asm/pgtable.h > > +++ b/arch/s390/include/asm/pgtable.h > > @@ -262,6 +262,7 @@ static inline int is_module_addr(void *addr) > > #define _REGION3_ENTRY (_REGION_ENTRY_TYPE_R3 | _REGION_ENTRY_LENGTH) > > #define _REGION3_ENTRY_EMPTY (_REGION_ENTRY_TYPE_R3 | _REGION_ENTRY_INVALID) > > > > +#define _REGION3_ENTRY_HARDWARE_BITS_LARGE 0xffffffff8000073cUL > > _REGION_ENTRY_HARDWARE_BITS is missing too. :) right, I will fix it > > And this definition also raises the question if the definition of > _SEGMENT_ENTRY_HARDWARE_BITS_LARGE should be changed so it also includes > the table type bits, which it probably should. tbh I agree > > These masks are really a bit randomly defined and assume that the > ACCF-Validity control bit is never set, and therefore the ACC bitfield can > be assumed to be software bits (and they are used as such for format 1 > segment table entries). > > But the ACCF bit is also a hardware bit in any case... oh well. probably the ACCF bit should also be marked as hardware bit (I had actually thought about it, but we don't do it for segments and I wanted it to be consistent) I'll send a v2 with: segment table type bits ACCF bit (both for segments and region3 _REGION3_ENTRY_HARDWARE_BITS
