From: Jeff Dike <jdike@addtoit.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 10/28] UML - Make a common misconfiguration impossible
Date: Mon, 10 Jan 2005 02:35:34 -0500 [thread overview]
Message-ID: <200501100735.j0A7ZYPW005780@ccure.user-mode-linux.org> (raw)
This patch makes UML produce error messages instead of silently exiting
when one of several configuration mistakes are made. FD_CHAN is now
mandatory so that people don't turn it off and complain about no boot
messages.
Some printks were turned into printfs in the tt mode gdb code so that they
appear on the screen.
Signed-off-by: Jeff Dike <jdike@addtoit.com>
Index: 2.6.10/arch/um/Kconfig_char
===================================================================
--- 2.6.10.orig/arch/um/Kconfig_char 2004-12-14 12:14:46.000000000 -0500
+++ 2.6.10/arch/um/Kconfig_char 2004-12-14 16:00:23.000000000 -0500
@@ -23,15 +23,6 @@
Unless you have a specific reason for disabling this, say Y.
-config FD_CHAN
- bool "file descriptor channel support"
- help
- This option enables support for attaching UML consoles and serial
- lines to already set up file descriptors. Generally, the main
- console is attached to file descriptors 0 and 1 (stdin and stdout),
- so it would be wise to leave this enabled unless you intend to
- attach it to some other host device.
-
config NULL_CHAN
bool "null channel support"
help
@@ -80,7 +71,7 @@
config NOCONFIG_CHAN
bool
- default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && FD_CHAN && NULL_CHAN)
+ default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
config CON_ZERO_CHAN
string "Default main console channel initialization"
Index: 2.6.10/arch/um/defconfig
===================================================================
--- 2.6.10.orig/arch/um/defconfig 2004-12-14 15:51:48.000000000 -0500
+++ 2.6.10/arch/um/defconfig 2004-12-14 16:00:23.000000000 -0500
@@ -92,13 +92,12 @@
CONFIG_STDERR_CONSOLE=y
CONFIG_STDIO_CONSOLE=y
CONFIG_SSL=y
-CONFIG_FD_CHAN=y
CONFIG_NULL_CHAN=y
CONFIG_PORT_CHAN=y
CONFIG_PTY_CHAN=y
CONFIG_TTY_CHAN=y
CONFIG_XTERM_CHAN=y
-# CONFIG_NOCONFIG_CHAN is not set
+CONFIG_NOCONFIG_CHAN=y
CONFIG_CON_ZERO_CHAN="fd:0,fd:1"
CONFIG_CON_CHAN="xterm"
CONFIG_SSL_CHAN="pty"
Index: 2.6.10/arch/um/drivers/Makefile
===================================================================
--- 2.6.10.orig/arch/um/drivers/Makefile 2004-12-14 12:14:46.000000000 -0500
+++ 2.6.10/arch/um/drivers/Makefile 2004-12-14 16:00:23.000000000 -0500
@@ -20,7 +20,7 @@
port-objs := port_kern.o port_user.o
harddog-objs := harddog_kern.o harddog_user.o
-obj-y := stdio_console.o $(CHAN_OBJS)
+obj-y := stdio_console.o fd.o $(CHAN_OBJS)
obj-$(CONFIG_SSL) += ssl.o
obj-$(CONFIG_STDERR_CONSOLE) += stderr_console.o
@@ -34,7 +34,6 @@
obj-$(CONFIG_MMAPPER) += mmapper_kern.o
obj-$(CONFIG_BLK_DEV_UBD) += ubd.o
obj-$(CONFIG_HOSTAUDIO) += hostaudio.o
-obj-$(CONFIG_FD_CHAN) += fd.o
obj-$(CONFIG_NULL_CHAN) += null.o
obj-$(CONFIG_PORT_CHAN) += port.o
obj-$(CONFIG_PTY_CHAN) += pty.o
Index: 2.6.10/arch/um/drivers/chan_kern.c
===================================================================
--- 2.6.10.orig/arch/um/drivers/chan_kern.c 2004-12-14 12:14:46.000000000 -0500
+++ 2.6.10/arch/um/drivers/chan_kern.c 2004-12-14 16:00:23.000000000 -0500
@@ -399,11 +399,7 @@
};
struct chan_type chan_table[] = {
-#ifdef CONFIG_FD_CHAN
{ "fd", &fd_ops },
-#else
- { "fd", ¬_configged_ops },
-#endif
#ifdef CONFIG_NULL_CHAN
{ "null", &null_ops },
Index: 2.6.10/arch/um/kernel/tt/gdb.c
===================================================================
--- 2.6.10.orig/arch/um/kernel/tt/gdb.c 2004-12-14 11:42:52.000000000 -0500
+++ 2.6.10/arch/um/kernel/tt/gdb.c 2004-12-14 16:00:23.000000000 -0500
@@ -162,7 +162,7 @@
void signal_usr1(int sig)
{
if(debugger_pid != -1){
- printk(UM_KERN_ERR "The debugger is already running\n");
+ printf("The debugger is already running\n");
return;
}
debugger_pid = start_debugger(linux_prog, 0, 0, &debugger_fd);
@@ -228,19 +228,19 @@
void child_signal(pid_t pid, int status){ }
int init_ptrace_proxy(int idle_pid, int startup, int stop)
{
- printk(UM_KERN_ERR "debug requested when CONFIG_PT_PROXY is off\n");
+ printf("debug requested when CONFIG_PT_PROXY is off\n");
kill_child_dead(idle_pid);
exit(1);
}
void signal_usr1(int sig)
{
- printk(UM_KERN_ERR "debug requested when CONFIG_PT_PROXY is off\n");
+ printf("debug requested when CONFIG_PT_PROXY is off\n");
}
int attach_debugger(int idle_pid, int pid, int stop)
{
- printk(UM_KERN_ERR "attach_debugger called when CONFIG_PT_PROXY "
+ printf("attach_debugger called when CONFIG_PT_PROXY "
"is off\n");
return(-1);
}
reply other threads:[~2005-01-10 5:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200501100735.j0A7ZYPW005780@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome