From: hs@denx.de (Heiko Schocher)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] kernel, logbuf: add support for external log buffer
Date: Wed, 11 Jul 2012 11:08:58 +0200 [thread overview]
Message-ID: <4FFD42AA.8090301@denx.de> (raw)
In-Reply-To: <1339395188-10166-1-git-send-email-hs@denx.de>
Hello,
On 11.06.2012 08:13, Heiko Schocher wrote:
> This merges support for the previously DENX-only kernel
> feature of specifying an alternative, "external" buffer
> for kernel printk messages and their associated metadata.
> This patch is based on DENX-only kernel commit:
>
> commit 212f61c7fd3b952a81d1459dd32a86a32ddfd4ce
> Author: Igor Lisitsin<igor@emcraft.com>
> Date: Wed Apr 18 14:55:19 2007 +0400
>
> Add support for external log buffer.
>
> Add support for external log buffer, for example passed by U-Boot,
> which may already contain messages (from the boot loader and/or POST).
>
> Signed-off-by: Igor Lisitsin<igor@emcraft.com>
>
> see:
> http://git.denx.de/?p=linux-denx.git;a=commit;h=212f61c7fd3b952a81d1459dd32a86a32ddfd4ce
>
> When this option is enabled, an architecture- or machine-specific log
> buffer is used for all printk messages. This allows entities such as
> boot loaders (e.g. U-Boot) to place printk-compatible messages into
> this buffer and for the kernel to coalesce them with its normal
> messages. This patch support this feature for arch/arm based
> boards.
>
> Signed-off-by: Heiko Schocher<hs@denx.de>
> Cc: Wolfgang Denk<wd@denx.de>
> Cc: Igor Lisitsin<igor@emcraft.com>
> Cc: Grant Erickson<gerickson@nuovations.com>
> Cc: linux-kernel at vger.kernel.org
> Cc: Tim Bird<tim.bird@am.sony.com>
> Cc: CE Linux Developers List<celinux-dev@lists.celinuxforum.org>
> Cc: Kay Sievers<kay@vrfy.org>
>
> ---
> restage prior discussion from lkml:
>
> https://lkml.org/lkml/2009/1/21/250
>
> Discussion stopped, and I want to reanimate it, also there is a
> Project Proposal on the "CE Linux Developers List" for such a feature,
> see here:
>
> http://www.mail-archive.com/celinux-dev at lists.celinuxforum.org/msg00103.html
>
> Maybe it is now the time to discuss this again?
>
> Is it worth to try to get this old code in current kernel, or
> should we investigate Kay Sievers proposal for a structured logging
> system, which will alter the format of the messages as they are
> stored in the log buffer, and discuss for this a "logbuffer support"?
>
> See this discussion here:
>
> http://thread.gmane.org/gmane.linux.kernel/1277619
>
> arch/arm/mm/init.c | 25 ++++++++++
> include/linux/logbuff.h | 51 ++++++++++++++++++++
> init/Kconfig | 12 +++++
> init/main.c | 5 ++
> kernel/printk.c | 117 +++++++++++++++++++++++++++++++++++++++++++++--
> 5 files changed, 206 insertions(+), 4 deletions(-)
> create mode 100644 include/linux/logbuff.h
ping? I got no respond to this RFC ... no chance to get this to
mainline?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Schocher <hs@denx.de>
To: Heiko Schocher <hs@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
Igor Lisitsin <igor@emcraft.com>, Wolfgang Denk <wd@denx.de>,
Grant Erickson <gerickson@nuovations.com>,
linux-kernel@vger.kernel.org, Tim Bird <tim.bird@am.sony.com>,
CE Linux Developers List <celinux-dev@lists.celinuxforum.org>,
Kay Sievers <kay@vrfy.org>
Subject: Re: [RFC] kernel, logbuf: add support for external log buffer
Date: Wed, 11 Jul 2012 11:08:58 +0200 [thread overview]
Message-ID: <4FFD42AA.8090301@denx.de> (raw)
In-Reply-To: <1339395188-10166-1-git-send-email-hs@denx.de>
Hello,
On 11.06.2012 08:13, Heiko Schocher wrote:
> This merges support for the previously DENX-only kernel
> feature of specifying an alternative, "external" buffer
> for kernel printk messages and their associated metadata.
> This patch is based on DENX-only kernel commit:
>
> commit 212f61c7fd3b952a81d1459dd32a86a32ddfd4ce
> Author: Igor Lisitsin<igor@emcraft.com>
> Date: Wed Apr 18 14:55:19 2007 +0400
>
> Add support for external log buffer.
>
> Add support for external log buffer, for example passed by U-Boot,
> which may already contain messages (from the boot loader and/or POST).
>
> Signed-off-by: Igor Lisitsin<igor@emcraft.com>
>
> see:
> http://git.denx.de/?p=linux-denx.git;a=commit;h=212f61c7fd3b952a81d1459dd32a86a32ddfd4ce
>
> When this option is enabled, an architecture- or machine-specific log
> buffer is used for all printk messages. This allows entities such as
> boot loaders (e.g. U-Boot) to place printk-compatible messages into
> this buffer and for the kernel to coalesce them with its normal
> messages. This patch support this feature for arch/arm based
> boards.
>
> Signed-off-by: Heiko Schocher<hs@denx.de>
> Cc: Wolfgang Denk<wd@denx.de>
> Cc: Igor Lisitsin<igor@emcraft.com>
> Cc: Grant Erickson<gerickson@nuovations.com>
> Cc: linux-kernel@vger.kernel.org
> Cc: Tim Bird<tim.bird@am.sony.com>
> Cc: CE Linux Developers List<celinux-dev@lists.celinuxforum.org>
> Cc: Kay Sievers<kay@vrfy.org>
>
> ---
> restage prior discussion from lkml:
>
> https://lkml.org/lkml/2009/1/21/250
>
> Discussion stopped, and I want to reanimate it, also there is a
> Project Proposal on the "CE Linux Developers List" for such a feature,
> see here:
>
> http://www.mail-archive.com/celinux-dev@lists.celinuxforum.org/msg00103.html
>
> Maybe it is now the time to discuss this again?
>
> Is it worth to try to get this old code in current kernel, or
> should we investigate Kay Sievers proposal for a structured logging
> system, which will alter the format of the messages as they are
> stored in the log buffer, and discuss for this a "logbuffer support"?
>
> See this discussion here:
>
> http://thread.gmane.org/gmane.linux.kernel/1277619
>
> arch/arm/mm/init.c | 25 ++++++++++
> include/linux/logbuff.h | 51 ++++++++++++++++++++
> init/Kconfig | 12 +++++
> init/main.c | 5 ++
> kernel/printk.c | 117 +++++++++++++++++++++++++++++++++++++++++++++--
> 5 files changed, 206 insertions(+), 4 deletions(-)
> create mode 100644 include/linux/logbuff.h
ping? I got no respond to this RFC ... no chance to get this to
mainline?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2012-07-11 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 6:13 [RFC] kernel, logbuf: add support for external log buffer Heiko Schocher
2012-06-11 6:13 ` Heiko Schocher
2012-07-11 9:08 ` Heiko Schocher [this message]
2012-07-11 9:08 ` Heiko Schocher
2012-07-24 23:55 ` Andrew Morton
2012-07-24 23:55 ` Andrew Morton
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=4FFD42AA.8090301@denx.de \
--to=hs@denx.de \
--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 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.