All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Eric Biederman <ebiederm@xmission.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] kexec: Replace kmap() with kmap_local_page()
Date: Fri, 08 Jul 2022 01:50:35 +0200	[thread overview]
Message-ID: <3183776.44csPzL39Z@opensuse> (raw)
In-Reply-To: <20220707231412.1404-1-fmdefrancesco@gmail.com>

On venerdì 8 luglio 2022 01:14:12 CEST Fabio M. De Francesco wrote:
> The use of kmap() and kmap_atomic() are being deprecated in favor of
> kmap_local_page().
> 
> With kmap_local_page(), the mappings are per thread, CPU local and not
> globally visible. Furthermore, the mappings can be acquired from any
> context (including interrupts).
> 
> Therefore, use kmap_local_page() in kexec_core.c because these mappings 
are
> per thread, CPU local, and not globally visible.
> 
> Tested on a QEMU + KVM 32-bits VM booting a kernel with HIGHMEM64GB
> enabled.
> 
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
> 
> v1->v2: A sentence of the commit message contained an error due to a
> mistake in copy-pasting from a previous patch. Replace "aio.c" with
> "kexec_core.c".
> 
>  kernel/kexec_core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
Sorry, another error... Please discard this patch because the version 
number is missing in the subject.

The second version, hopefully final and correct, is at
https://lore.kernel.org/lkml/20220707231550.1484-1-fmdefrancesco@gmail.com/

Thank you,

Fabio




_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Eric Biederman <ebiederm@xmission.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] kexec: Replace kmap() with kmap_local_page()
Date: Fri, 08 Jul 2022 01:50:35 +0200	[thread overview]
Message-ID: <3183776.44csPzL39Z@opensuse> (raw)
In-Reply-To: <20220707231412.1404-1-fmdefrancesco@gmail.com>

On venerdì 8 luglio 2022 01:14:12 CEST Fabio M. De Francesco wrote:
> The use of kmap() and kmap_atomic() are being deprecated in favor of
> kmap_local_page().
> 
> With kmap_local_page(), the mappings are per thread, CPU local and not
> globally visible. Furthermore, the mappings can be acquired from any
> context (including interrupts).
> 
> Therefore, use kmap_local_page() in kexec_core.c because these mappings 
are
> per thread, CPU local, and not globally visible.
> 
> Tested on a QEMU + KVM 32-bits VM booting a kernel with HIGHMEM64GB
> enabled.
> 
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
> 
> v1->v2: A sentence of the commit message contained an error due to a
> mistake in copy-pasting from a previous patch. Replace "aio.c" with
> "kexec_core.c".
> 
>  kernel/kexec_core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
Sorry, another error... Please discard this patch because the version 
number is missing in the subject.

The second version, hopefully final and correct, is at
https://lore.kernel.org/lkml/20220707231550.1484-1-fmdefrancesco@gmail.com/

Thank you,

Fabio




  reply	other threads:[~2022-07-07 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 23:14 [PATCH] kexec: Replace kmap() with kmap_local_page() Fabio M. De Francesco
2022-07-07 23:14 ` Fabio M. De Francesco
2022-07-07 23:50 ` Fabio M. De Francesco [this message]
2022-07-07 23:50   ` Fabio M. De Francesco
  -- strict thread matches above, loose matches on Subject: below --
2022-07-07 18:49 Fabio M. De Francesco
2022-07-07 18:49 ` Fabio M. De Francesco
2022-07-07 23:40 ` Fabio M. De Francesco
2022-07-07 23:40   ` 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=3183776.44csPzL39Z@opensuse \
    --to=fmdefrancesco@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=ira.weiny@intel.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.