public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH/RFC] m68k/amiga: Fix specifying multiple debug= parameters
Date: Thu, 17 Oct 2013 21:46:52 +0200	[thread overview]
Message-ID: <1382039212-26062-1-git-send-email-geert@linux-m68k.org> (raw)

Since commit d6713b4091a99fa2af2fabdcd2f3fb97f32ecf2e ("m68k: early
parameter support"), the user can specify multiple debug consoles using the
"debug=" kernel command line parameter.
However, as the struct console object was shared, it would actually register
the same console object multiple times, causing the following warning:

WARNING: CPU: 0 PID: 0 at kernel/printk/printk.c:2233 register_console+0x36/0x2b6()
console 'debug0' already registered

Note that only the console corresponding to the last "debug=" parameter became
active, as the .write() method was overwritten before registration.

Use separate console objects to allow using multiple debug consoles.

Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
Notes:
  1. This patch was only compile-tested.
  2. Do we want to fix it this way? Alternatives are:
       a. Reject a second debug= parameter by checking for a non-NULL .write()
          method
	  => only the first debug console will be used,
       b. Skip console registration in case of a non-NULL .write() method
          => only the last debug console will be used,
  3. Atari has a similar issue, with even more (4) debug consoles.

 arch/m68k/amiga/config.c |   26 ++++++++++++++++----------
 1 file changed, 16 insertions(+), 10 deletions(-)

diff --git a/arch/m68k/amiga/config.c b/arch/m68k/amiga/config.c
index 049ef8605314..b975eefba30f 100644
--- a/arch/m68k/amiga/config.c
+++ b/arch/m68k/amiga/config.c
@@ -107,12 +107,6 @@ static void amiga_mem_console_write(struct console *co, const char *b,
 static void amiga_heartbeat(int on);
 #endif
 
-static struct console amiga_console_driver = {
-	.name	= "debug",
-	.flags	= CON_PRINTBUFFER,
-	.index	= -1,
-};
-
 
     /*
      *  Motherboard Resources present in all Amiga models
@@ -624,6 +618,13 @@ static void amiga_mem_console_write(struct console *co, const char *s,
 	}
 }
 
+static struct console amiga_mem_console = {
+	.name	= "debug",
+	.write	= amiga_mem_console_write,
+	.flags	= CON_PRINTBUFFER,
+	.index	= -1,
+};
+
 static int __init amiga_savekmsg_setup(char *arg)
 {
 	if (!MACH_IS_AMIGA || strcmp(arg, "mem"))
@@ -642,8 +643,7 @@ static int __init amiga_savekmsg_setup(char *arg)
 	savekmsg->magicptr = ZTWO_PADDR(savekmsg);
 	savekmsg->size = 0;
 
-	amiga_console_driver.write = amiga_mem_console_write;
-	register_console(&amiga_console_driver);
+	register_console(&amiga_mem_console);
 	return 0;
 }
 
@@ -723,12 +723,18 @@ void amiga_serial_gets(struct console *co, char *s, int len)
 }
 #endif
 
+static struct console amiga_serial_console = {
+	.name	= "debug",
+	.write	= amiga_serial_console_write,
+	.flags	= CON_PRINTBUFFER,
+	.index	= -1,
+};
+
 static int __init amiga_debug_setup(char *arg)
 {
 	if (MACH_IS_AMIGA && !strcmp(arg, "ser")) {
 		/* no initialization required (?) */
-		amiga_console_driver.write = amiga_serial_console_write;
-		register_console(&amiga_console_driver);
+		register_console(&amiga_serial_console);
 	}
 	return 0;
 }
-- 
1.7.9.5


             reply	other threads:[~2013-10-17 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 19:46 Geert Uytterhoeven [this message]
2013-11-25 16:16 ` [PATCH/RFC] m68k/amiga: Fix specifying multiple debug= parameters Geert Uytterhoeven
2013-11-25 19:03   ` Andreas Schwab
2013-12-01 11:15     ` Geert Uytterhoeven

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=1382039212-26062-1-git-send-email-geert@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@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