From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
David Howells <dhowells@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org, linux-input@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux PWM List <linux-pwm@vger.kernel.org>,
linux-rtc@vger.kernel.org, linux-spi <linux-spi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)
Date: Thu, 15 Mar 2018 10:13:42 -0700 [thread overview]
Message-ID: <1521134022.22221.38.camel@perches.com> (raw)
In-Reply-To: <20180315170830.GA17574@bombadil.infradead.org>
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:
> > 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?
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-block@vger.kernel.org,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-doc@vger.kernel.org, netdev <netdev@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PWM List <linux-pwm@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
linux-ide@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-input@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
linux-rtc@vger.kernel.org
Subject: Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)
Date: Thu, 15 Mar 2018 10:13:42 -0700 [thread overview]
Message-ID: <1521134022.22221.38.camel@perches.com> (raw)
In-Reply-To: <20180315170830.GA17574@bombadil.infradead.org>
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:
> > 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
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
David Howells <dhowells@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org, linux-input@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux PWM List <linux-pwm@vger.kernel.org>,
linux-rtc@vger.kernel.org, linux-spi <linux-spi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)
Date: Thu, 15 Mar 2018 10:13:42 -0700 [thread overview]
Message-ID: <1521134022.22221.38.camel@perches.com> (raw)
In-Reply-To: <20180315170830.GA17574@bombadil.infradead.org>
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:
> > 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
David Howells <dhowells@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
linux-ide@vger.kernel.org, linux-input@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux PWM List <linux-pwm@vger.kernel.org>,
linux-rtc@vger.kernel.org, linux-spi <linux-spi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)
Date: Thu, 15 Mar 2018 10:13:42 -0700 [thread overview]
Message-ID: <1521134022.22221.38.camel@perches.com> (raw)
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:
> > 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?
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-block@vger.kernel.org,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-doc@vger.kernel.org, netdev <netdev@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PWM List <linux-pwm@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
linux-ide@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-input@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
linux-rtc@vger.kernel.org
Subject: Re: rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures)
Date: Thu, 15 Mar 2018 17:13:42 +0000 [thread overview]
Message-ID: <1521134022.22221.38.camel@perches.com> (raw)
In-Reply-To: <20180315170830.GA17574@bombadil.infradead.org>
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:
> > 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?
next prev parent reply other threads:[~2018-03-15 17:13 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:34 [PATCH 00/16] remove eight obsolete architectures Arnd Bergmann
2018-03-14 14:34 ` Arnd Bergmann
2018-03-14 14:34 ` Arnd Bergmann
2018-03-14 14:34 ` Arnd Bergmann
2018-03-14 14:36 ` [PATCH 01/16] mn10300: Remove the architecture Arnd Bergmann
2018-03-14 14:36 ` [PATCH 02/16] arch: remove frv port Arnd Bergmann
2018-03-14 14:36 ` [PATCH 03/16] arch: remove m32r port Arnd Bergmann
2018-03-14 14:36 ` [PATCH 04/16] arch: remove score port Arnd Bergmann
2018-03-14 14:36 ` [PATCH 05/16] arch: remove blackfin port Arnd Bergmann
2018-03-14 16:51 ` [PATCH] scripts/checkstack.pl: remove blackfin support Tobias Klauser
2018-03-14 17:04 ` Arnd Bergmann
2018-03-15 22:24 ` [PATCH 05/16] arch: remove blackfin port Bryan Wu
2018-03-14 14:36 ` [PATCH 06/16] arch: remove tile port Arnd Bergmann
2018-03-16 1:23 ` Chris Metcalf
2018-03-16 8:12 ` Arnd Bergmann
2018-03-14 14:36 ` [PATCH 07/16] CRIS: Drop support for the CRIS port Arnd Bergmann
2018-03-14 14:39 ` [PATCH 10/16] mm: remove obsolete alloc_remap() Arnd Bergmann
2018-03-14 14:50 ` Pavel Tatashin
2018-03-14 14:56 ` Arnd Bergmann
2018-03-14 14:59 ` Pavel Tatashin
2018-03-14 14:43 ` [PATCH 11/16] treewide: simplify Kconfig dependencies for removed archs Arnd Bergmann
2018-03-14 14:43 ` Arnd Bergmann
2018-03-14 14:43 ` [11/16] " Arnd Bergmann
2018-03-14 14:43 ` [PATCH 11/16] " Arnd Bergmann
2018-03-14 14:43 ` [PATCH 12/16] asm-generic: siginfo: remove obsolete #ifdefs Arnd Bergmann
2018-03-14 16:38 ` Eric W. Biederman
2018-03-14 20:31 ` Dominik Brodowski
2018-03-14 20:40 ` Arnd Bergmann
2018-03-14 20:45 ` Dominik Brodowski
2018-03-15 10:06 ` Eric W. Biederman
2018-03-15 10:48 ` Arnd Bergmann
2018-03-15 11:37 ` Eric W. Biederman
2018-03-15 12:50 ` Arnd Bergmann
2018-03-15 18:07 ` Eric W. Biederman
2018-03-15 12:54 ` [PATCH 11/16] treewide: simplify Kconfig dependencies for removed archs Kalle Valo
2018-03-15 12:54 ` Kalle Valo
2018-03-15 12:54 ` [11/16] " Kalle Valo
2018-03-15 12:54 ` [PATCH 11/16] " Kalle Valo
2018-03-15 12:54 ` Kalle Valo
2018-03-19 23:06 ` Alexandre Belloni
2018-03-19 23:06 ` Alexandre Belloni
2018-03-19 23:06 ` [11/16] " Alexandre Belloni
2018-03-14 14:51 ` [PATCH 13/16] Documentation: arch-support: remove obsolete architectures Arnd Bergmann
2018-03-14 14:52 ` [PATCH 15/16] recordmcount.pl: drop blackin and tile support Arnd Bergmann
2018-03-15 20:42 ` Steven Rostedt
2018-03-14 14:53 ` [PATCH 16/16] ktest: remove obsolete architectures Arnd Bergmann
2018-03-15 20:46 ` Steven Rostedt
2018-03-14 20:38 ` [PATCH 14/16] asm-generic: clean up asm/unistd.h Arnd Bergmann
2018-03-15 9:42 ` [PATCH 00/16] remove eight obsolete architectures David Howells
2018-03-15 9:42 ` David Howells
2018-03-15 9:42 ` David Howells
2018-03-15 9:42 ` David Howells
2018-03-15 9:48 ` Geert Uytterhoeven
2018-03-15 9:48 ` Geert Uytterhoeven
2018-03-15 9:48 ` Geert Uytterhoeven
2018-03-15 9:48 ` Geert Uytterhoeven
2018-03-15 16:56 ` rfc: remove print_vma_addr ? (was Re: [PATCH 00/16] remove eight obsolete architectures) Joe Perches
2018-03-15 16:56 ` Joe Perches
2018-03-15 16:56 ` Joe Perches
2018-03-15 16:56 ` Joe Perches
2018-03-15 16:56 ` Joe Perches
2018-03-15 16:56 ` Joe Perches
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:08 ` Matthew Wilcox
2018-03-15 17:13 ` Joe Perches [this message]
2018-03-15 17:13 ` Joe Perches
2018-03-15 17:13 ` Joe Perches
2018-03-15 17:13 ` Joe Perches
2018-03-15 17:13 ` Joe Perches
2018-03-15 17:13 ` Joe Perches
2018-03-15 9:56 ` [PATCH 00/16] remove eight obsolete architectures Arnd Bergmann
2018-03-15 9:56 ` Arnd Bergmann
2018-03-15 9:56 ` Arnd Bergmann
2018-03-15 9:56 ` Arnd Bergmann
2018-03-16 4:50 ` afzal mohammed
2018-03-16 4:50 ` afzal mohammed
2018-03-16 4:50 ` afzal mohammed
2018-03-15 9:59 ` Hannes Reinecke
2018-03-15 9:59 ` Hannes Reinecke
2018-03-15 9:59 ` Hannes Reinecke
2018-03-15 9:59 ` Hannes Reinecke
2018-03-15 9:59 ` Hannes Reinecke
2018-03-15 10:42 ` Arnd Bergmann
2018-03-15 10:42 ` Arnd Bergmann
2018-03-15 10:42 ` Arnd Bergmann
2018-03-15 10:42 ` Arnd Bergmann
2018-03-15 14:17 ` Christoph Hellwig
2018-03-15 14:17 ` Christoph Hellwig
2018-03-15 14:17 ` Christoph Hellwig
2018-03-15 14:17 ` Christoph Hellwig
2018-03-20 17:11 ` Palmer Dabbelt
2018-03-20 17:11 ` Palmer Dabbelt
2018-03-20 17:11 ` Palmer Dabbelt
2018-03-20 17:11 ` Palmer Dabbelt
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=1521134022.22221.38.camel@perches.com \
--to=joe@perches.com \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.