From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russell.h.weight@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Nick Terrell <terrelln@fb.com>,
linux-kernel@vger.kernel.org, Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] firmware_loader: Replace kmap() with kmap_local_page()
Date: Sun, 10 Jul 2022 12:24:41 +0200 [thread overview]
Message-ID: <Ysqo6RjF/njUcOor@kroah.com> (raw)
In-Reply-To: <20220710101156.26139-1-fmdefrancesco@gmail.com>
On Sun, Jul 10, 2022 at 12:11:56PM +0200, Fabio M. De Francesco wrote:
> The use of kmap() is being deprecated in favor of kmap_local_page().
>
> With kmap_local_page() the mappings are per thread, CPU local, can take
> page faults, and can be called from any context (including interrupts).
But that is not the case here for this kmap() instance? If this is a
simple search/replace, why is this not just done once and be done with
it?
> Call kmap_local_page() in firmware_loader wherever kmap() is currently
> used. In firmware_rw() use the copy_{from,to}_page() helpers instead of
> open coding the local mappings plus memcpy().
Isn't that just a different cleanup than the kmap() change? Or is that
tied to the fact that the other buffer is now allocated with
kmap_local_page() instead of kmap()?
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
> drivers/base/firmware_loader/main.c | 4 ++--
> drivers/base/firmware_loader/sysfs.c | 9 ++++-----
> 2 files changed, 6 insertions(+), 7 deletions(-)
Did you run this through the firmware test framework?
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-10 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 10:11 Fabio M. De Francesco
2022-07-10 10:24 ` Greg Kroah-Hartman [this message]
2022-07-10 11:18 ` Fabio M. De Francesco
2022-07-10 11:57 ` Greg Kroah-Hartman
2022-07-10 12:24 ` Fabio M. De Francesco
2022-07-11 18:52 ` Fabio M. De Francesco
2022-07-14 14:50 ` Greg Kroah-Hartman
2022-07-14 20:40 ` Luis Chamberlain
2022-07-14 23:54 ` Fabio M. De Francesco
2022-07-10 11:43 ` kernel test robot
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=Ysqo6RjF/njUcOor@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=terrelln@fb.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
Powered by JetHome