Strange s390 code in 2.4.19-pre8

Pete Zaitcev (zaitcev@redhat.com)
Fri, 10 May 2002 12:47:27 -0400


I reviewed the -pre8 briefly, and is seems that the vast
majority of s390/s390x changes are good, but I cannot discern
the intent of some of them. I would like Martin or Ulrich
to comment.

#1 - smp_call_function in a driver, trying to be ultra smart
or IBM's hardware is too broken and asymmetric?

+ iucv_debug(1, "entering");
+ if (smp_processor_id() == 0)
+ iucv_declare_buffer_cpu0(&b2f0_result);
+ else
+ smp_call_function(iucv_declare_buffer_cpu0, &b2f0_result, 0, 1);+ iucv_debug(1, "Address of EIB = %p", iucv_external_int_buffer);
+ if (b2f0_result == 0x0deadbeef)
+ b2f0_result = 0xaa;
+ iucv_debug(1, "exiting");
return b2f0_result;

#2 - strange changes to net Makefile

--- linux.orig/drivers/s390/net/Makefile Thu May 2 22:37:01 2002
+++ linux/drivers/s390/net/Makefile Thu May 2 22:25:05 2002
@@ -9,8 +9,8 @@

ctc-objs := ctcmain.o ctctty.o

-obj-y += iucv.o fsm.o
-obj-$(CONFIG_CTC) += ctc.o
+obj-$(CONFIG_IUCV) += iucv.o fsm.o
+obj-$(CONFIG_CTC) += ctc.o fsm.o
obj-$(CONFIG_IUCV) += netiucv.o

include $(TOPDIR)/Rules.make

I guarantee you that this blows up, unless CTC and IUCV are
built in. And why does it add wo CONFIG_IUCV lines? It is
legal, but unconventional.

#3 - config.in patch inconsistent or deadwood

--- linux.orig/arch/s390/config.in Thu May 2 22:36:59 2002
+++ linux/arch/s390/config.in Thu May 2 22:25:01 2002
@@ -37,6 +37,8 @@
mainmenu_option next_comment
comment 'General setup'
bool 'Fast IRQ handling' CONFIG_FAST_IRQ
+bool 'Process warning machine checks' CONFIG_MACHCHK_WARNING
+bool 'Use chscs for Common I/O' CONFIG_CHSC
bool 'Builtin IPL record support' CONFIG_IPL
if [ "$CONFIG_IPL" = "y" ]; then
choice 'IPL method generated into head.S' \

This is wonderful, but why did you merge it to Marcelo if the
rest of the code is missing?

And, while we are on topic, when are you guys going to merge
changes to the partitioning code?

-- Pete
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/