linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* what happened to /proc/vmallocinfo as of v4.15?
@ 2019-02-15 12:33 Chris Brandt
  2019-02-15 18:02 ` Geert Uytterhoeven
  0 siblings, 1 reply; 3+ messages in thread
From: Chris Brandt @ 2019-02-15 12:33 UTC (permalink / raw)
  To: linux-renesas-soc

Hello everyone,

I just noticed this yesterday and I can't seem to figure it out.

In linux-4.14, vmallocinfo looked like this:

$ cat /proc/vmallocinfo
0xc2800000-0xc2802000    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
0xc2802000-0xc2804000    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
0xc2804000-0xc2806000    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000 ioremap
0xc2806000-0xc2808000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0xc2808000-0xc280a000    8192 unpurged vm_area
0xc280a000-0xc280c000    8192 unpurged vm_area
0xc280c000-0xc280e000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0xc280e000-0xc2810000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0xc2810000-0xc2812000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap


However as of linux-4.15, it now looks like this:

$ cat /proc/vmallocinfo
0x2423e1ec-0x1d348857    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
0x1d348857-0x52c37840    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
0x52c37840-0x402f3b08    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000 ioremap
0x402f3b08-0x06d553ef    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0x06d553ef-0xf6dfcceb    8192 unpurged vm_area
0xf6dfcceb-0xd99b6570    8192 unpurged vm_area
0xd99b6570-0xa32d8fae    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0xa32d8fae-0xffd15855    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
0xffd15855-0x9d2cc6ea    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap


The virtual addresses are all wrong!

I can't seem to find any patches or code changes that would explain this.

Does anyone have an idea why it now looks like this?

Thanks,
Chris


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: what happened to /proc/vmallocinfo as of v4.15?
  2019-02-15 12:33 what happened to /proc/vmallocinfo as of v4.15? Chris Brandt
@ 2019-02-15 18:02 ` Geert Uytterhoeven
  2019-02-15 18:26   ` Chris Brandt
  0 siblings, 1 reply; 3+ messages in thread
From: Geert Uytterhoeven @ 2019-02-15 18:02 UTC (permalink / raw)
  To: Chris Brandt; +Cc: linux-renesas-soc

Hi Chris,

On Fri, Feb 15, 2019 at 5:14 PM Chris Brandt <Chris.Brandt@renesas.com> wrote:
> I just noticed this yesterday and I can't seem to figure it out.
>
> In linux-4.14, vmallocinfo looked like this:
>
> $ cat /proc/vmallocinfo
> 0xc2800000-0xc2802000    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
> 0xc2802000-0xc2804000    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
> 0xc2804000-0xc2806000    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000 ioremap
> 0xc2806000-0xc2808000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0xc2808000-0xc280a000    8192 unpurged vm_area
> 0xc280a000-0xc280c000    8192 unpurged vm_area
> 0xc280c000-0xc280e000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0xc280e000-0xc2810000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0xc2810000-0xc2812000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
>
>
> However as of linux-4.15, it now looks like this:
>
> $ cat /proc/vmallocinfo
> 0x2423e1ec-0x1d348857    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
> 0x1d348857-0x52c37840    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
> 0x52c37840-0x402f3b08    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000 ioremap
> 0x402f3b08-0x06d553ef    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0x06d553ef-0xf6dfcceb    8192 unpurged vm_area
> 0xf6dfcceb-0xd99b6570    8192 unpurged vm_area
> 0xd99b6570-0xa32d8fae    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0xa32d8fae-0xffd15855    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> 0xffd15855-0x9d2cc6ea    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
>
>
> The virtual addresses are all wrong!
>
> I can't seem to find any patches or code changes that would explain this.
>
> Does anyone have an idea why it now looks like this?

Please see commit ad67b74d2469d9b8 ("printk: hash addresses printed with %p").

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 3+ messages in thread
* RE: what happened to /proc/vmallocinfo as of v4.15?
  2019-02-15 18:02 ` Geert Uytterhoeven
@ 2019-02-15 18:26   ` Chris Brandt
  0 siblings, 0 replies; 3+ messages in thread
From: Chris Brandt @ 2019-02-15 18:26 UTC (permalink / raw)
  To: Geert Uytterhoeven; +Cc: linux-renesas-soc

Thank you Geert!!!

I didn't even think about looking at the printk code!

Cheers
Chris


> -----Original Message-----
> From: Geert Uytterhoeven <geert@linux-m68k.org>
> Sent: Friday, February 15, 2019 1:02 PM
> To: Chris Brandt <Chris.Brandt@renesas.com>
> Cc: linux-renesas-soc@vger.kernel.org
> Subject: Re: what happened to /proc/vmallocinfo as of v4.15?
> 
> Hi Chris,
> 
> On Fri, Feb 15, 2019 at 5:14 PM Chris Brandt <Chris.Brandt@renesas.com>
> wrote:
> > I just noticed this yesterday and I can't seem to figure it out.
> >
> > In linux-4.14, vmallocinfo looked like this:
> >
> > $ cat /proc/vmallocinfo
> > 0xc2800000-0xc2802000    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
> > 0xc2802000-0xc2804000    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
> > 0xc2804000-0xc2806000    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000
> ioremap
> > 0xc2806000-0xc2808000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0xc2808000-0xc280a000    8192 unpurged vm_area
> > 0xc280a000-0xc280c000    8192 unpurged vm_area
> > 0xc280c000-0xc280e000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0xc280e000-0xc2810000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0xc2810000-0xc2812000    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> >
> >
> > However as of linux-4.15, it now looks like this:
> >
> > $ cat /proc/vmallocinfo
> > 0x2423e1ec-0x1d348857    8192 of_iomap+0x19/0x22 phys=0xe8201000 ioremap
> > 0x1d348857-0x52c37840    8192 of_iomap+0x19/0x22 phys=0xe8202000 ioremap
> > 0x52c37840-0x402f3b08    8192 l2x0_of_init+0x3f/0x174 phys=0x3ffff000
> ioremap
> > 0x402f3b08-0x06d553ef    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0x06d553ef-0xf6dfcceb    8192 unpurged vm_area
> > 0xf6dfcceb-0xd99b6570    8192 unpurged vm_area
> > 0xd99b6570-0xa32d8fae    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0xa32d8fae-0xffd15855    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> > 0xffd15855-0x9d2cc6ea    8192 of_iomap+0x19/0x22 phys=0xfcfe0000 ioremap
> >
> >
> > The virtual addresses are all wrong!
> >
> > I can't seem to find any patches or code changes that would explain this.
> >
> > Does anyone have an idea why it now looks like this?
> 
> Please see commit ad67b74d2469d9b8 ("printk: hash addresses printed
> with %p").
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-
> m68k.org
> 
> In personal conversations with technical people, I call myself a hacker.
> But
> when I'm talking to journalists I just say "programmer" or something like
> that.
>                                 -- Linus Torvalds

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-02-15 18:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-15 12:33 what happened to /proc/vmallocinfo as of v4.15? Chris Brandt
2019-02-15 18:02 ` Geert Uytterhoeven
2019-02-15 18:26   ` Chris Brandt

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).