From: Pete Zaitcev <zaitcev@redhat.com>
To: schwidefsky@de.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Strange s390 code in 2.4.19-pre8
Date: Fri, 10 May 2002 12:47:27 -0400 [thread overview]
Message-ID: <20020510124727.A10127@devserv.devel.redhat.com> (raw)
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
next reply other threads:[~2002-05-10 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 16:47 Pete Zaitcev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 7:54 Strange s390 code in 2.4.19-pre8 Martin Schwidefsky
2002-05-13 16:10 ` Pete Zaitcev
2002-05-13 16:18 ` Kai Germaschewski
2002-05-13 16:23 ` Pete Zaitcev
2002-05-13 16:30 ` Kai Germaschewski
2002-05-13 16:32 ` Pete Zaitcev
2002-05-13 17:39 ` Kai Germaschewski
2002-05-13 16:16 ` Kai Germaschewski
2002-05-13 16:19 ` Pete Zaitcev
2002-05-13 16:25 ` Kai Germaschewski
2002-05-14 1:22 ` Keith Owens
2002-05-13 22:42 Ulrich Weigand
2002-05-13 22:50 ` Kai Germaschewski
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=20020510124727.A10127@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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