All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pingfan Liu <kernelfans@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64/fixmap: make notes of fixed_addresses more precisely
Date: Mon, 3 Aug 2020 10:07:16 +0800	[thread overview]
Message-ID: <CAFgQCTvmdVzfqdTwrhmccsvNL_g5pdsqT_5kV9j9Rb7BjLoUsA@mail.gmail.com> (raw)
In-Reply-To: <20200731121334.GC29569@gaia>

On Fri, Jul 31, 2020 at 8:13 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Fri, Jul 31, 2020 at 10:47:13AM +0800, Pingfan Liu wrote:
> > On Thu, Jul 30, 2020 at 7:09 PM Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > On Fri, Jul 10, 2020 at 09:43:22PM +0800, Pingfan Liu wrote:
> > > > These 'compile-time allocated' memory buffers can occupy more than one
> > > > page. So improve the note about it.
> > > >
> > > > Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
> > > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > > Cc: Will Deacon <will@kernel.org>
> > > > To: linux-arm-kernel@lists.infradead.org
> > > > ---
> > > >  arch/arm64/include/asm/fixmap.h | 3 ++-
> > > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/arch/arm64/include/asm/fixmap.h b/arch/arm64/include/asm/fixmap.h
> > > > index f987b8a..318aee1 100644
> > > > --- a/arch/arm64/include/asm/fixmap.h
> > > > +++ b/arch/arm64/include/asm/fixmap.h
> > > > @@ -29,7 +29,8 @@
> > > >   * in the boot process.
> > > >   *
> > > >   * These 'compile-time allocated' memory buffers are
> > > > - * page-sized. Use set_fixmap(idx,phys) to associate
> > > > + * page-sized (or larger if used with an increment
> > > > + * higher than 1). Use set_fixmap(idx,phys) to associate
> > > >   * physical memory with fixmap indices.
> > >
> > > I don't get this. set_fixmap() only maps a page. Also, what's
> > > "increment" in this context?
> >
> > I refer to the notes in the counterpart in x86. And for the time
> > being, it is the case for the ranges (FIX_FDT, FIX_FDT_END), which may
> > cost more than one page size.
>
> OK, so increment refers to the enum increment. But if we update this, we
> also need to state that set_fixmap() only maps page-size buffers,
> otherwise one may think that set_fixmap(FIX_FDT, phys) maps the whole
> FDT. We could say that each enum increment represents a page-sized
> buffer.
What about description like:
diff --git a/arch/arm64/include/asm/fixmap.h b/arch/arm64/include/asm/fixmap.h
index f987b8a..4335800 100644
--- a/arch/arm64/include/asm/fixmap.h
+++ b/arch/arm64/include/asm/fixmap.h
@@ -28,10 +28,9 @@
  * compile time, but to set the physical address only
  * in the boot process.
  *
- * These 'compile-time allocated' memory buffers are
- * page-sized. Use set_fixmap(idx,phys) to associate
- * physical memory with fixmap indices.
- *
+ * Each enum increment in these 'compile-time allocated'
+ * memory buffers is page-sized. Use set_fixmap(idx,phys)
+ * to associate physical memory with a fixmap index.
  */

Thanks,
Pingfan

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-08-03  2:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 13:43 [PATCH] arm64/fixmap: make notes of fixed_addresses more precisely Pingfan Liu
2020-07-30 11:09 ` Catalin Marinas
2020-07-31  2:47   ` Pingfan Liu
2020-07-31 12:13     ` Catalin Marinas
2020-08-03  2:07       ` Pingfan Liu [this message]
2020-08-03 11:53         ` Catalin Marinas

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=CAFgQCTvmdVzfqdTwrhmccsvNL_g5pdsqT_5kV9j9Rb7BjLoUsA@mail.gmail.com \
    --to=kernelfans@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@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.