Thread (14 messages) 14 messages, 10 authors, 2018-03-20

Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)

From: Joe Perches <joe@perches.com>
Date: 2018-03-15 17:13:42
Also in: dri-devel, linux-arch, linux-block, linux-doc, linux-fbdev, linux-fsdevel, linux-ide, linux-input, linux-mm, linux-pwm, linux-rtc, linux-spi, linux-usb, linux-watchdog, linux-wireless, lkml

On Thu, 2018-03-15 at 10:08 -0700, Matthew Wilcox wrote:
On Thu, Mar 15, 2018 at 09:56:46AM -0700, Joe Perches wrote:
quoted
I have a patchset that creates a vsprintf extension for
print_vma_addr and removes all the uses similar to the
print_symbol() removal.

This now avoids any possible printk interleaving.

Unfortunately, without some #ifdef in vsprintf, which
I would like to avoid, it increases the nommu kernel
size by ~500 bytes.

Anyone think this is acceptable?
[]
This doesn't feel like a huge win since it's only called ~once per
architecture.  I'd be more excited if it made the printing of the whole
thing standardised; eg we have a print_fault() function in mm/memory.c
which takes a suitable set of arguments.
Sure but perhaps that's not feasible as the surrounding output
is per-arch specific.

What could be a standardized fault message here?

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help