From: jaedon.shin@gmail.com (Jaedon Shin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] irqchip: Use %px to print pointer value
Date: Sat, 10 Feb 2018 11:16:22 +0900 [thread overview]
Message-ID: <CAD3828B-6D72-42C6-8D54-78EC35BAF65B@gmail.com> (raw)
In-Reply-To: <6bf05e81-2334-f3ac-08a7-e53ee59bb4c0@arm.com>
> On 10 Feb 2018, at 1:04 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>
> On 09/02/18 15:54, Florian Fainelli wrote:
>> On February 9, 2018 12:51:33 AM PST, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>> On 09/02/18 02:10, Jaedon Shin wrote:
>>>> Since commit ad67b74d2469 ("printk: hash addresses printed with %p")
>>>> pointers printed with %p are hashed. Use %px instead of %p to print
>>>> pointer value.
>>>>
>>>> Signed-off-by: Jaedon Shin <jaedon.shin@gmail.com>
>>>> ---
>>>> drivers/irqchip/irq-bcm7038-l1.c | 2 +-
>>>> drivers/irqchip/irq-bcm7120-l2.c | 2 +-
>>>> drivers/irqchip/irq-brcmstb-l2.c | 2 +-
>>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/drivers/irqchip/irq-bcm7038-l1.c
>>> b/drivers/irqchip/irq-bcm7038-l1.c
>>>> index 55cfb986225b..f604c1d89b3b 100644
>>>> --- a/drivers/irqchip/irq-bcm7038-l1.c
>>>> +++ b/drivers/irqchip/irq-bcm7038-l1.c
>>>> @@ -339,7 +339,7 @@ int __init bcm7038_l1_of_init(struct device_node
>>> *dn,
>>>> goto out_unmap;
>>>> }
>>>>
>>>> - pr_info("registered BCM7038 L1 intc (mem: 0x%p, IRQs: %d)\n",
>>>> + pr_info("registered BCM7038 L1 intc (mem: 0x%px, IRQs: %d)\n",
>>>> intc->cpus[0]->map_base, IRQS_PER_WORD * intc->n_words);
>>>>
>>>> return 0;
>>>> diff --git a/drivers/irqchip/irq-bcm7120-l2.c
>>> b/drivers/irqchip/irq-bcm7120-l2.c
>>>> index 983640eba418..1cc4dd1d584a 100644
>>>> --- a/drivers/irqchip/irq-bcm7120-l2.c
>>>> +++ b/drivers/irqchip/irq-bcm7120-l2.c
>>>> @@ -318,7 +318,7 @@ static int __init bcm7120_l2_intc_probe(struct
>>> device_node *dn,
>>>> }
>>>> }
>>>>
>>>> - pr_info("registered %s intc (mem: 0x%p, parent IRQ(s): %d)\n",
>>>> + pr_info("registered %s intc (mem: 0x%px, parent IRQ(s): %d)\n",
>>>> intc_name, data->map_base[0], data->num_parent_irqs);
>>>>
>>>> return 0;
>>>> diff --git a/drivers/irqchip/irq-brcmstb-l2.c
>>> b/drivers/irqchip/irq-brcmstb-l2.c
>>>> index 691d20eb0bec..6760edeeb666 100644
>>>> --- a/drivers/irqchip/irq-brcmstb-l2.c
>>>> +++ b/drivers/irqchip/irq-brcmstb-l2.c
>>>> @@ -262,7 +262,7 @@ static int __init brcmstb_l2_intc_of_init(struct
>>> device_node *np,
>>>> ct->chip.irq_set_wake = irq_gc_set_wake;
>>>> }
>>>>
>>>> - pr_info("registered L2 intc (mem: 0x%p, parent irq: %d)\n",
>>>> + pr_info("registered L2 intc (mem: 0x%px, parent irq: %d)\n",
>>>> base, parent_irq);
>>>>
>>>> return 0;
>>>>
>>>
>>> Why is that something useful to do? This just tells you where the
>>> device
>>> is mapped in the VA space, and I doubt that's a useful information,
>>> hashed pointers or not. Am I missing something obvious?
>>
>> No you are right there is not much value in printing the register
>> virtual address (sometimes there is e.g: on MIPS) either we fix the
>> prints to show the physical address of the base register or we could
>> possibly drop the prints entirely.
>
> Displaying the PA can be useful if you have several identical blocks in
> your system and you want to be able to identify them. Given that there
> is probably only one of these controllers per system, the address is
> pretty pointless.
>
> If you send me a patch removing the prints, I'll queue it.
>
> Thanks,
>
> M.
> --
> Jazz is not dead. It just smells funny...
I'll submit a new one to drop the entire print.
Thanks,
Jaedon
next prev parent reply other threads:[~2018-02-10 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 2:10 [PATCH] irqchip: Use %px to print pointer value Jaedon Shin
2018-02-09 8:48 ` Geert Uytterhoeven
2018-02-09 8:51 ` Marc Zyngier
2018-02-09 15:54 ` Florian Fainelli
2018-02-09 16:04 ` Marc Zyngier
2018-02-10 2:16 ` Jaedon Shin [this message]
2018-02-12 22:17 ` Jonas Gorski
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=CAD3828B-6D72-42C6-8D54-78EC35BAF65B@gmail.com \
--to=jaedon.shin@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).