From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Jeff Moyer" <jmoyer@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>, dhowells@redhat.com
Subject: Re: netconsole and a serial one
Date: Mon, 22 Sep 2008 09:23:59 -0400 [thread overview]
Message-ID: <9e4733910809220623ka3670f7r8937d248fec4c986@mail.gmail.com> (raw)
In-Reply-To: <x498wtkl3lu.fsf@segfault.boston.devel.redhat.com>
On Mon, Sep 22, 2008 at 9:19 AM, Jeff Moyer <jmoyer@redhat.com> wrote:
> "Jon Smirl" <jonsmirl@gmail.com> writes:
>
>> I have both netconsole and a serial console setup on an embedded
>> system. This is what I need for the boot process.
>>
>> After I'm booted I want to turn off printk() output to the serial
>> console but keep it going to netconsole.
>> I've been googling for an hour, how do I do this?
>>
>> I need to turn off the serial output after boot because serial
>> printk() disables interrupts for up to 1ms which is enough to cause me
>> to lose a lot of other interrupts.
>
> There's no way (that I know of) to do this presently. However, I think
> David Howells has been working on a patch that reduces the amount of
> time printk spends with IRQs disabled.
I looked into interrupts and printk several years ago. If I recall
correctly printk() prints with interrupts off to ensure stability in
an OOPS situation. Could serial printk() be changed to disable
interrupts only in the OOPS situation? It's all of the other
non-critical printks that are impacting my system.
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-09-22 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 0:14 Jon Smirl
2008-09-22 13:19 ` Jeff Moyer
2008-09-22 13:23 ` Jon Smirl [this message]
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=9e4733910809220623ka3670f7r8937d248fec4c986@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=dhowells@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®