From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Ira Weiny <ira.weiny@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Will Deacon <will@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, outreachy@lists.linux.dev,
"Acked-by : Mike Rapoport" <rppt@linux.ibm.com>
Subject: Re: [PATCH v2 1/4] mm/highmem: Fix kernel-doc warnings in highmem*.h
Date: Wed, 27 Apr 2022 07:28:13 +0200 [thread overview]
Message-ID: <2383038.jE0xQCEvom@leap> (raw)
In-Reply-To: <YmfRynAhuSWz9H+e@linutronix.de>
On martedì 26 aprile 2022 13:04:42 CEST Sebastian Andrzej Siewior wrote:
> On 2022-04-26 11:43:03 [+0200], Fabio M. De Francesco wrote:
>
> Either way, according to the code kmap_atomic() does not always disable
> preemption
Hi Sebastian,
In my last email (for patch 4/4) I wrote that I would add a deprecation
notice to kunmap_local() and would talk about thread locality in
kmap_local_page(). I want to confirm that I'll do these changes in v3.
Then I closed that email asking if I was still overlooking something.
Consider that I'm relatively new to kernel development and that it's just
something I do in my spare time. So I was pretty sure I was still missing
something :)
After reading again the code of kmap_atomic() (as you suggested - thanks!)
I noted that you correctly say that kmap_atomic() does not always disables
preemption (i.e., preemption is disabled only for !PREEMPT_RT kernel's
configurations).
Therefore I'll also change the first sentence of kunmap_local() to the
following:
"[It] Unmaps an address previously mapped by kmap_atomic() and re-enables
pagefaults and preemption (the latter disabled only for !PREEMP_RT
configurations).".
I will also be making this change in v3.
Can you please say if I'm still missing something?
Thanks,
Fabio
next prev parent reply other threads:[~2022-04-27 5:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 16:23 [PATCH v2 0/4] Extend and reorganize Highmem's documentation Fabio M. De Francesco
2022-04-25 16:23 ` [PATCH v2 1/4] mm/highmem: Fix kernel-doc warnings in highmem*.h Fabio M. De Francesco
2022-04-26 7:01 ` Sebastian Andrzej Siewior
2022-04-26 9:43 ` Fabio M. De Francesco
2022-04-26 11:04 ` Sebastian Andrzej Siewior
2022-04-27 5:28 ` Fabio M. De Francesco [this message]
2022-04-29 15:59 ` Ira Weiny
2022-05-25 9:34 ` Sebastian Andrzej Siewior
2022-05-25 16:03 ` Ira Weiny
2022-04-25 16:23 ` [PATCH v2 2/4] Documentation/vm: Include kdocs into highmem.rst Fabio M. De Francesco
2022-04-25 16:23 ` [PATCH v2 3/4] Documentation/vm: Move section from highmem.rst to highmem.h Fabio M. De Francesco
2022-04-25 16:24 ` [PATCH v2 4/4] Documentation/vm: Rework "Temporary Virtual Mappings" section Fabio M. De Francesco
2022-04-26 7:17 ` Sebastian Andrzej Siewior
2022-04-26 10:45 ` Fabio M. De Francesco
2022-04-26 11:47 ` Sebastian Andrzej Siewior
2022-04-26 18:31 ` 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=2383038.jE0xQCEvom@leap \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=ira.weiny@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
--cc=pcc@google.com \
--cc=rppt@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).