Skip to contentSkip to conversation

Patch: s390 root on scsi disc

PATCH Stefan Völkel 2 participants 4 messages Jun 19, 2004 SCSI

lore
Share & tools
lore
#0 lore raw

Hi,

the attached patch adds the ability to pass an initial zfcp scsi device to the kernel. This enables us to have / on a scsi disc.

This is no "scsi only system" patch as you still need a small minidisk that contains the kernel. Our typical setup looks like this:

        /	/dev/sda1
        /boot	/dev/dasda1

With this patch we are able to preserve our rare DASD space by having most of the data on a cheap scsi disc in our JBOD.

regards
Stefan

Signature · 5 lines
Stefan Völkel                            [email protected]
Millenux GmbH                              mobile: +49.170.79177.17
Lilienthalstraße 2                          phone: +49.711.88770.300
70825 Stuttgart-Korntal                       fax: +49.711.88770.349
     -= linux without limits -=- http://linux.zSeries.org/ =-
zfcp_aux.c renamed from zfcp_aux.c.orig +11 -0
@@ -146,6 +146,17 @@
 module_param(flags_dump, uint, 0);
 #endif
 
+#ifndef MODULE
+/* remember kernel boot time parameter */
+static int __init zfcp_device(char *str)
+{
+	device = str;
+	return 1;
+}
+
+__setup("zfcpdevice=", zfcp_device);
+#endif
+
 /****************************************************************/
 /************** Functions without logging ***********************/
 /****************************************************************/
#1 lore raw
zfcp_aux.c renamed from zfcp_aux.c.orig +10 -0
@@ -146,6 +146,17 @@
 module_param(flags_dump, uint, 0);
 #endif
 
+#ifndef MODULE
+/* remember kernel boot time parameter */
+static int __init zfcp_device(char *str)
+{
+	device = str;
+	return 1;
+}
+
+__setup("zfcpdevice=", zfcp_device);
+#endif
 

please use module_param instead. still wondering why zfcp needs paramters anyway..

#2 lore raw
Quoted 17 lines · Christoph Hellwig
zfcp_aux.c renamed from zfcp_aux.c.orig +10 -0
@@ -146,6 +146,17 @@
 module_param(flags_dump, uint, 0);
 #endif
 
+#ifndef MODULE
+/* remember kernel boot time parameter */
+static int __init zfcp_device(char *str)
+{
+	device = str;
+	return 1;
+}
+
+__setup("zfcpdevice=", zfcp_device);
+#endif
 
Quoted 2 lines

please use module_param instead. still wondering why zfcp needs paramters anyway..

Well, my problem was that passing device=foo at boot time (zfcp compiled into the kernel) resulted in device beeing empty. device is

        module_param(device, charp, 0);
        MODULE_PARM_DESC(device, "specify initial device");

regards
Stefan

Signature · 5 lines
Stefan Völkel                            [email protected]
Millenux GmbH                              mobile: +49.170.79177.17
Lilienthalstraße 2                          phone: +49.711.88770.300
70825 Stuttgart-Korntal                       fax: +49.711.88770.349
     -= linux without limits -=- http://linux.zSeries.org/ =-
#3 lore raw
Quoted 9 lines · Stefan Völkel
Quoted 3 lines

please use module_param instead. still wondering why zfcp needs paramters anyway..

Well, my problem was that passing device=foo at boot time (zfcp compiled into the kernel) resulted in device beeing empty. device is

        module_param(device, charp, 0);
        MODULE_PARM_DESC(device, "specify initial device");

You need to pass zfcp.device=foo
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html