From: Heiko Carstens <hca@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
frankja@linux.ibm.com, nrb@linux.ibm.com, nsg@linux.ibm.com,
borntraeger@de.ibm.com, gerald.schaefer@linux.ibm.com,
david@redhat.com
Subject: Re: [PATCH v1 0/2] s390/mm: fix improper use of __storage_key_init_range
Date: Tue, 16 Apr 2024 15:24:31 +0200 [thread overview]
Message-ID: <20240416132431.8615-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20240416114220.28489-1-imbrenda@linux.ibm.com>
On Tue, Apr 16, 2024 at 01:42:18PM +0200, Claudio Imbrenda wrote:
> The function __storage_key_init_range() expects the end address to be
> the first byte outside the range to be initialized. I.e. end - start
> should be the size of the area to be initialized.
>
> This small series fixes two cases in which the last address in the
> range was passed as end address. This was still functionally correct,
> since __storage_key_init_range() will still loop over single pages and
> correctly clear the given range, but it will be slower than clearing
> the storage keys for the whole 1M block with a single instruction.
>
> Claudio Imbrenda (2):
> s390/mm: fix storage key clearing for guest huge pages
> s390/mm: fix clearing storage keys for huge pages
>
> arch/s390/mm/gmap.c | 2 +-
> arch/s390/mm/hugetlbpage.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
next prev parent reply other threads:[~2024-04-16 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 11:42 [PATCH v1 0/2] s390/mm: fix improper use of __storage_key_init_range Claudio Imbrenda
2024-04-16 11:42 ` [PATCH v1 1/2] s390/mm: fix storage key clearing for guest huge pages Claudio Imbrenda
2024-04-16 11:42 ` [PATCH v1 2/2] s390/mm: fix clearing storage keys for " Claudio Imbrenda
2024-04-16 13:24 ` Heiko Carstens [this message]
2024-04-16 15:53 ` [PATCH v1 0/2] s390/mm: fix improper use of __storage_key_init_range Alexander Gordeev
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=20240416132431.8615-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@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).