From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Ira Weiny <ira.weiny@intel.com>, Mike Rapoport <rppt@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Mike Rapoport <rppt@linux.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] mm/highmem: Add notes about conversions from kmap{,_atomic}()
Date: Wed, 7 Dec 2022 09:00:29 +0100 [thread overview]
Message-ID: <Y5BIHdnP4yeJ8svL@linutronix.de> (raw)
In-Reply-To: <2093077.OBFZWjSADL@suse>
On 2022-12-06 20:12:13 [+0100], Fabio M. De Francesco wrote:
> > Furthermore, code between the kmap_atomic() and kunmap_atomic()
> > functions may implicitly depended
>
> I suppose it should be "depend"? Shouldn't it?
Ehm, yes, correct.
> > on the side effects of kmap_atomic()
> > namely disabling pagefaults or preemption or both.
>
> I agree with you for rephrasing, mainly because it is
> written in poor English.
>
> However, I still have doubts about why you deleted "migration".
> AFAIK, __kmap_local_pfn_prot() always takes care of disabling migration for
> HIGHMEM enabled kernels.
That is correct. Historically kmap_atomic() never had a
migrate_disable() statement - only preempt_disable(). With disabled
preemption the task migration is implicitly disabled.
> How about !HIGHMEM, where kmap_local_page() is an indirect call to
> page_address()? Did you mean that, if the code between kmap_atomic() and
> kunmap_atomic() depended on migrate_disable() (in PREEMPT_RT) we should always
> just stay safe and call preempt_disable() together with conversion to
> kmap_local_page()?
Even in the !HIGHMEM case it always uses preempt_disable(). With
PREEMPT_RT it is different as it never disabled preemption and always
did a migrate_disable() instead. If you talk about what needs to be
considered while migrating away from kmap_atomic() then I wouldn't add
the PREEMPT_RT bits to it since it was never in the picture while the
code (using kmap_atomic()) was originally written.
> If so, I understand and I again agree with you. If not, I'm missing something;
> so please let me understand properly.
>
> Aside from the above, I'm not sure whether you deleted the last phrase before
> your suggestion. What about making it to become "For the above-mentioned
> cases, conversions should also explicitly disable page-faults and/or
> preemption"?
They need to disable preemption or page-faults or both if it is needed
(not unconditionally) and where it is needed. This means not
unconditionally over the whole kmap-ed section.
> Thanks again for noticing my mistakes.
>
> Fabio
Sebastian
next prev parent reply other threads:[~2022-12-07 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 7:00 Fabio M. De Francesco
2022-12-06 8:00 ` Sebastian Andrzej Siewior
2022-12-06 19:12 ` Fabio M. De Francesco
2022-12-07 8:00 ` Sebastian Andrzej Siewior [this message]
2022-12-07 13:01 ` Fabio M. De Francesco
2022-12-07 13:51 ` Sebastian Andrzej Siewior
2022-12-07 23:03 ` Fabio M. De Francesco
2022-12-06 19:14 ` Fabio M. De Francesco
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=Y5BIHdnP4yeJ8svL@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
/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