> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Kirk Wolf > Sent: Friday, December 07, 2007 8:54 AM > To: [email protected] > Subject: Open z architecture and Linux questions > > > The general discussion on IBM-MAIN of whether the z > architecture is "open" > or not leads me to wonder a bit about Linux on system z. > Perhaps those more experienced with Linux on system z can > help me understand > a couple of things. > > AFAIK: > 1) Linux for system z is still able to run on raw LPARs, without z/VM > 2) IBM contributes kernel patches and tool chain code to support the z > instruction set, under the GPL > > So: > Q1) Are any closed/proprietary instructions and hardware > interfaces used? I > would guess that SIE would not be *executed* by Linux, but > are others? If > so, does contribution of code under the GPL that "links" to > closed/proprietary interfaces imply anything?
There is no proprietary code in the kernel itself. If IBM were to create an instruction and place it in one of their kernel modification without documenting the effect, then I am sure that it would never be accepted into the Linus-approved kernel stream. For whatever that is worth to the users of Linux on z. IBM could not refuse to supply the source due to the GPL. > > Q2) Might we expect that eventually Linux on system z will > require z/VM, so > that "platform enablement" (for the kernel and device > drivers) can be moved > into "closed" DIAG instructions so that IBM can further > protect its IP? > Would that be accepted to the Linux kernel folks? If the functionality is via a "kernel module", then Linus has indicated that binary (no source) kernel modules are acceptable. However they "taint" the kernel. Originally, the 3590 tape I/O driver was binary only. If IBM ever puts in a kernel module to drive their tape robots, I expect that code will be binary only. Similarly if IBM ever puts PAV support into the kernel, I expect it would be binary only. However, updating the filesystem driver to interface to the PAV module could not be binary since it would be updating GPL code. Purists will decry this, but it is acceptable at present. > > Kirk Wolf -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
