From: Daero Lee <skseofh@gmail.com>
To: mark.rutland@arm.com
Cc: linux-mm@kvack.org
Subject: Question about mapping FIX_P*D
Date: Mon, 25 Dec 2023 00:16:12 +0900 [thread overview]
Message-ID: <20231224151612.GA1132393@daerolee-Swift-SF316-51> (raw)
Hello Mark
I have a question about your patch related to FIX_P*D mapping.
(f4710445458c0a1bd1c3c014ada2e7d7dc7b882f)
I understand it maps using bm_p*d to mapping FIX_P*D in
fixmap_remap_fdt().
But in early_fdt_map(), we already maps all fixmap region using bm_p*d.
My question is, 'Do we really need using FIX_P*D to remap the FIX_FDT?'.
My guess is that it uses a previously written function. Functianlly,
nothing has changed.
I think we can just use bm_p*d, then it can save the time mapping
FIX_P*D.
Could I get your opinion about this?
Regards,
Daero Lee
reply other threads:[~2023-12-24 15:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231224151612.GA1132393@daerolee-Swift-SF316-51 \
--to=skseofh@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.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