From: Matt Mackall <mpm@selenic.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/3] netpoll: netconsole
Date: Wed, 10 Sep 2003 03:24:35 -0500 [thread overview]
Message-ID: <20030910082435.GG4489@waste.org> (raw)
In-Reply-To: <p73znhdhxkx.fsf@oldwotan.suse.de>
On Wed, Sep 10, 2003 at 10:11:42AM +0200, Andi Kleen wrote:
> Matt Mackall <mpm@selenic.com> writes:
>
> > This patch uses the netpoll API to transmit kernel printks over UDP
> > for uses similar to serial console.
>
> One common problem I saw with the original netconsole patches
> was that the low level drivers' poll function was grabbing the
> driver spinlock, but the driver would otherwere do printk
> with the spinlock hold (->easy deadlock)
>
> Does your patchkit handle that?
No, haven't encountered it. Which lock are we talking about, specifically?
> P.S.: Also what would be really nice for netconsole
> would be "kernel ifconfig" similar to what the nfsroot code does.
> With that it would be actually possible to use it as a full console
> replacement.
It ups the interface if necessary and has enough info to build a
complete raw packet so if I understand you correctly, it's already
there. I start getting netconsole messages immediately after
driver/net initcalls.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-09-10 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030910074256.GD4489@waste.org.suse.lists.linux.kernel>
2003-09-10 8:11 ` [PATCH 2/3] netpoll: netconsole Andi Kleen
2003-09-10 8:24 ` Matt Mackall [this message]
2003-09-10 8:29 ` Andi Kleen
2003-09-10 9:01 ` Matt Mackall
2003-09-10 16:00 ` Mitchell Blank Jr
2003-09-12 5:33 ` Mitchell Blank Jr
2003-09-12 5:57 ` Matt Mackall
2003-09-12 19:40 ` Andrew Morton
2003-09-10 7:42 Matt Mackall
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=20030910082435.GG4489@waste.org \
--to=mpm@selenic.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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 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.