From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] mm: Add debug_virt_to_phys()
Date: Sat, 12 Nov 2016 11:29:38 -0800 [thread overview]
Message-ID: <abb97b87-db44-e25a-608e-161b57a0439b@gmail.com> (raw)
In-Reply-To: <20161112054318.GB24127@arm.com>
Le 11/11/2016 ? 21:43, Will Deacon a ?crit :
> On Fri, Nov 11, 2016 at 04:44:43PM -0800, Florian Fainelli wrote:
>> When CONFIG_DEBUG_VM is turned on, virt_to_phys() maps to
>> debug_virt_to_phys() which helps catch vmalloc space addresses being
>> passed. This is helpful in debugging bogus drivers that just assume
>> linear mappings all over the place.
>>
>> For ARM, ARM64, Unicore32 and Microblaze, the architectures define
>> __virt_to_phys() as being the functional implementation of the address
>> translation, so we special case the debug stub to call into
>> __virt_to_phys directly.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> arch/arm/include/asm/memory.h | 4 ++++
>> arch/arm64/include/asm/memory.h | 4 ++++
>> include/asm-generic/memory_model.h | 4 ++++
>> mm/debug.c | 15 +++++++++++++++
>> 4 files changed, 27 insertions(+)
>
> What's the interaction between this and the DEBUG_VIRTUAL patches from Laura?
>
> http://lkml.kernel.org/r/20161102210054.16621-7-labbott at redhat.com
>
> They seem to be tackling the exact same problem afaict.
Indeed thanks for pointing that out, I guess I could piggy back on this
patchset and try to cover ARM.
Thanks!
--
Florian
next prev parent reply other threads:[~2016-11-12 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 0:44 [PATCH RFC] mm: Add debug_virt_to_phys() Florian Fainelli
2016-11-12 1:49 ` Nicolas Pitre
2016-11-12 3:39 ` Florian Fainelli
2016-11-12 16:32 ` Nicolas Pitre
2016-11-12 5:43 ` Will Deacon
2016-11-12 19:29 ` Florian Fainelli [this message]
2016-11-14 18:45 ` Laura Abbott
2016-11-14 19:23 ` Florian Fainelli
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=abb97b87-db44-e25a-608e-161b57a0439b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.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).