From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
borntraeger@de.ibm.com, schlameuss@linux.ibm.com,
willy@infradead.org, hca@linux.ibm.com, svens@linux.ibm.com,
agordeev@linux.ibm.com, gor@linux.ibm.com, nrb@linux.ibm.com,
nsg@linux.ibm.com
Subject: Re: [PATCH v1 13/13] KVM: s390: remove the last user of page->index
Date: Mon, 20 Jan 2025 11:28:48 +0100 [thread overview]
Message-ID: <20250120112848.1547a439@p-imbrenda> (raw)
In-Reply-To: <e548aa1e-d954-4fab-8b74-302c140c04f7@redhat.com>
On Mon, 20 Jan 2025 10:43:15 +0100
David Hildenbrand <david@redhat.com> wrote:
> >> +static inline unsigned long gmap_pgste_get_index(unsigned long *pgt)
> >> +{
> >> + unsigned long *pgstes, res;
> >> +
> >> + pgstes = pgt + _PAGE_ENTRIES;
> >> +
> >> + res = (pgstes[0] & PGSTE_ST2_MASK) << 16;
> >> + res |= pgstes[1] & PGSTE_ST2_MASK;
> >> + res |= (pgstes[2] & PGSTE_ST2_MASK) >> 16;
> >> + res |= (pgstes[3] & PGSTE_ST2_MASK) >> 32;
> >> +
> >> + return res;
> >> +}
> >
> > I have to think about that change for a bit before I post an opinion.
>
> I'm wondering if we should just do what Willy suggested and use ptdesc
> -> pt_index instead?
we will need to store more stuff in the future; putting things in the
PGSTEs gives us 512 bytes per table (although I admit it looks... weird)
>
> It's not like we must "force" this removal here. If we'll simply
> allocate a ptdesc memdesc in the future for these page tables (just like
> for any other page table), we have that extra space easily available.
>
> The important part is getting rid of page->index now, but not
> necessarily ptdesc->pt_index.
>
next prev parent reply other threads:[~2025-01-20 10:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 18:14 [PATCH v1 00/13] KVM: s390: Stop using page->index and other things Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 01/13] KVM: s390: wrapper for KVM_BUG Claudio Imbrenda
2025-01-10 9:09 ` Christian Borntraeger
2025-01-10 13:13 ` Christoph Schlameuss
2025-01-08 18:14 ` [PATCH v1 02/13] KVM: s390: fake memslots for ucontrol VMs Claudio Imbrenda
2025-01-10 9:31 ` Christian Borntraeger
2025-01-10 11:47 ` Claudio Imbrenda
2025-01-10 16:22 ` Sean Christopherson
2025-01-10 17:02 ` Claudio Imbrenda
2025-01-10 17:34 ` Sean Christopherson
2025-01-10 17:43 ` Claudio Imbrenda
2025-01-10 15:40 ` Christoph Schlameuss
2025-01-10 16:18 ` Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 03/13] KVM: s390: use __kvm_faultin_pfn() Claudio Imbrenda
2025-01-14 17:34 ` Christoph Schlameuss
2025-01-14 17:56 ` Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 04/13] KVM: s390: move pv gmap functions into kvm Claudio Imbrenda
2025-01-09 17:42 ` kernel test robot
2025-01-15 12:48 ` Janosch Frank
2025-01-15 12:59 ` Claudio Imbrenda
2025-01-15 13:23 ` Janosch Frank
2025-01-08 18:14 ` [PATCH v1 05/13] KVM: s390: get rid of gmap_fault() Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 06/13] KVM: s390: get rid of gmap_translate() Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 07/13] KVM: s390: move some gmap shadowing functions away from mm/gmap.c Claudio Imbrenda
2025-01-15 8:56 ` Janosch Frank
2025-01-15 10:20 ` Claudio Imbrenda
2025-01-15 11:48 ` Janosch Frank
2025-01-08 18:14 ` [PATCH v1 08/13] KVM: s390: stop using page->index for non-shadow gmaps Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 09/13] KVM: s390: stop using lists to keep track of used dat tables Claudio Imbrenda
2025-01-15 9:01 ` Janosch Frank
2025-01-08 18:14 ` [PATCH v1 10/13] KVM: s390: move gmap_shadow_pgt_lookup() into kvm Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 11/13] KVM: s390: remove useless page->index usage Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 12/13] KVM: s390: move PGSTE softbits Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 13/13] KVM: s390: remove the last user of page->index Claudio Imbrenda
2025-01-15 12:17 ` Janosch Frank
2025-01-15 12:23 ` Claudio Imbrenda
2025-01-20 9:43 ` David Hildenbrand
2025-01-20 10:28 ` Claudio Imbrenda [this message]
2025-01-20 10:34 ` 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=20250120112848.1547a439@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=schlameuss@linux.ibm.com \
--cc=svens@linux.ibm.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