From: David Hildenbrand <david@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, linux-mm@kvack.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Niklas Schnelle <schnelle@linux.ibm.com>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: Re: [PATCH resend RFC 7/9] s390/mm: no need for pte_alloc_map_lock() if we know the pmd is present
Date: Tue, 14 Sep 2021 19:23:36 +0200 [thread overview]
Message-ID: <5a572489-a6d6-aaf4-098a-a8059f9b12f0@redhat.com> (raw)
In-Reply-To: <20210914185449.42d7d5ca@p-imbrenda>
On 14.09.21 18:54, Claudio Imbrenda wrote:
> On Thu, 9 Sep 2021 18:22:46 +0200
> David Hildenbrand <david@redhat.com> wrote:
>
>> pte_map_lock() is sufficient.
>
> Can you explain the difference and why it is enough?
I didn't repeat the $subject:
"No need for pte_alloc_map_lock() if we know the pmd is present;
pte_map_lock() is sufficient, because there isn't anything to allocate."
>
>>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> ---
>> arch/s390/mm/pgtable.c | 15 +++------------
>> 1 file changed, 3 insertions(+), 12 deletions(-)
>>
>> diff --git a/arch/s390/mm/pgtable.c b/arch/s390/mm/pgtable.c
>> index 5fb409ff7842..4e77b8ebdcc5 100644
>> --- a/arch/s390/mm/pgtable.c
>> +++ b/arch/s390/mm/pgtable.c
>> @@ -814,10 +814,7 @@ int set_guest_storage_key(struct mm_struct *mm, unsigned long addr,
>> }
>> spin_unlock(ptl);
>>
>> - ptep = pte_alloc_map_lock(mm, pmdp, addr, &ptl);
>> - if (unlikely(!ptep))
>> - return -EFAULT;
>> -
>> + ptep = pte_offset_map_lock(mm, pmdp, addr, &ptl);
>> new = old = pgste_get_lock(ptep);
>> pgste_val(new) &= ~(PGSTE_GR_BIT | PGSTE_GC_BIT |
>> PGSTE_ACC_BITS | PGSTE_FP_BIT);
>> @@ -912,10 +909,7 @@ int reset_guest_reference_bit(struct mm_struct *mm, unsigned long addr)
>> }
>> spin_unlock(ptl);
>>
>> - ptep = pte_alloc_map_lock(mm, pmdp, addr, &ptl);
>> - if (unlikely(!ptep))
>> - return -EFAULT;
>> -
>> + ptep = pte_offset_map_lock(mm, pmdp, addr, &ptl);
>> new = old = pgste_get_lock(ptep);
>> /* Reset guest reference bit only */
>> pgste_val(new) &= ~PGSTE_GR_BIT;
>> @@ -977,10 +971,7 @@ int get_guest_storage_key(struct mm_struct *mm, unsigned long addr,
>> }
>> spin_unlock(ptl);
>>
>> - ptep = pte_alloc_map_lock(mm, pmdp, addr, &ptl);
>> - if (unlikely(!ptep))
>> - return -EFAULT;
>> -
>> + ptep = pte_offset_map_lock(mm, pmdp, addr, &ptl);
>> pgste = pgste_get_lock(ptep);
>> *key = (pgste_val(pgste) & (PGSTE_ACC_BITS | PGSTE_FP_BIT)) >> 56;
>> paddr = pte_val(*ptep) & PAGE_MASK;
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-09-14 17:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 16:22 [PATCH resend RFC 0/9] s390: fixes, cleanups and optimizations for page table walkers David Hildenbrand
2021-09-09 16:22 ` [PATCH resend RFC 1/9] s390/gmap: validate VMA in __gmap_zap() David Hildenbrand
2021-09-14 16:53 ` Claudio Imbrenda
2021-09-09 16:22 ` [PATCH resend RFC 2/9] s390/gmap: don't unconditionally call pte_unmap_unlock() " David Hildenbrand
2021-09-14 16:52 ` Claudio Imbrenda
2021-09-09 16:22 ` [PATCH resend RFC 3/9] s390/mm: validate VMA in PGSTE manipulation functions David Hildenbrand
2021-09-14 16:54 ` Claudio Imbrenda
2021-09-09 16:22 ` [PATCH resend RFC 4/9] s390/mm: fix VMA and page table handling code in storage key handling functions David Hildenbrand
2021-09-27 16:37 ` Claudio Imbrenda
2021-09-09 16:22 ` [PATCH resend RFC 5/9] s390/uv: fully validate the VMA before calling follow_page() David Hildenbrand
2021-09-14 16:53 ` Claudio Imbrenda
2021-09-14 22:41 ` Liam Howlett
2021-09-09 16:22 ` [PATCH resend RFC 6/9] s390/pci_mmio: fully validate the VMA before calling follow_pte() David Hildenbrand
2021-09-14 16:54 ` Claudio Imbrenda
2021-09-14 22:41 ` Liam Howlett
2021-09-09 16:22 ` [PATCH resend RFC 7/9] s390/mm: no need for pte_alloc_map_lock() if we know the pmd is present David Hildenbrand
2021-09-14 16:54 ` Claudio Imbrenda
2021-09-14 17:23 ` David Hildenbrand [this message]
2021-09-09 16:22 ` [PATCH resend RFC 8/9] s390/mm: optimize set_guest_storage_key() David Hildenbrand
2021-09-27 17:01 ` Claudio Imbrenda
2021-09-09 16:22 ` [PATCH resend RFC 9/9] s390/mm: optimize reset_guest_reference_bit() David Hildenbrand
2021-09-27 17:02 ` Claudio Imbrenda
2021-09-14 16:50 ` [PATCH resend RFC 0/9] s390: fixes, cleanups and optimizations for page table walkers Claudio Imbrenda
2021-09-14 18:06 ` David Hildenbrand
2021-09-28 10:59 ` Heiko Carstens
2021-09-28 11:06 ` Christian Borntraeger
2021-09-28 14:38 ` Claudio Imbrenda
2021-09-28 16:03 ` Christian Borntraeger
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=5a572489-a6d6-aaf4-098a-a8059f9b12f0@redhat.com \
--to=david@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.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-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=schnelle@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 NNTP newsgroup(s).