[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zo/3RzpS2WNssMIi@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>
Date: Thu, 11 Jul 2024 17:16:23 +0200
From: Alexander Gordeev <agordeev@...ux.ibm.com>
To: Claudio Imbrenda <imbrenda@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-s390@...r.kernel.org, hca@...ux.ibm.com, svens@...ux.ibm.com,
gor@...ux.ibm.com, nrb@...ux.ibm.com, nsg@...ux.ibm.com,
seiden@...ux.ibm.com, frankja@...ux.ibm.com, borntraeger@...ibm.com,
gerald.schaefer@...ux.ibm.com, david@...hat.com
Subject: Re: [PATCH v1 2/2] s390/kvm: Move bitfields for dat tables
On Wed, Jul 03, 2024 at 05:59:00PM +0200, Claudio Imbrenda wrote:
Hi Claudio,
> Once in a separate header, the structs become available everywhere. One
> possible usecase is to merge them in the s390
> definitions, which is left as an exercise for the reader.
Is my understanding correct that you potentially see page_table_entry::val /
region?_table_entry.*::val / segment_table_entry.* merged with pte_t::pte /
p?d_t::p?d?
Thanks!
Powered by blists - more mailing lists