This is the
talk page for discussing improvements to the
Logical partition article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
|
References can be found here [1] —Preceding unsigned comment added by 91.152.200.56 ( talk) 12:10, 2 November 2007 (UTC)
IBM introduced the terms LPAR and PR/SM on the 3090, long after the cited date of 1972. The LPAR support differed from the early CP-67, Virtual Machine Facility/370 and Virtual Machine Facility/System Product in that it was bundled with the processor and didn't offer the user controls of the full VM packages.
As part of any article cleanup, the text copied from references should be properly attributed. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 22:22, 30 June 2010 (UTC)
This article deals with topics that are present also in other vendors (e.g. HP vPAR) but it seems that it only talks about IBM. — Preceding unsigned comment added by 151.99.187.181 ( talk) 11:44, 12 March 2013 (UTC)
Hello fellow Wikipedians,
I have just modified 6 external links on Logical partition. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
{{
dead link}}
tag to
https://www-01.ibm.com/servers/resourcelink/lib03030.nsf/web+search/0E6125F89F8B8EF6852572E6007E884D/$file/sa76-0098.pdfWhen you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 5 June 2024).
Cheers.— InternetArchiveBot ( Report bug) 06:37, 5 January 2018 (UTC)
What happened to https://i.stack.imgur.com/R0K32.png ? — Preceding unsigned comment added by 84.147.35.23 ( talk) 07:51, 26 May 2018 (UTC)
@
Guy Harris: The edit
Special:Permalink/1152075614 has the comment An IBM Systems Journal article on PR/SM suggests it's implemented with low-level hardware and microcode at a level very different from the level at which CP runs.
I'm not aware of any hardware, microcode or millicode support for VM/XA beyond SIE. Is that article available online? My suspicion is that the "hardware and microcode" it is referring to is just SIE. --
Shmuel (Seymour J.) Metz Username:Chatul (
talk)
01:54, 28 April 2023 (UTC)
PR/SM is an optional feature on the IBM 3090 Model E and ES/3090(TM) Model S processor families that allows a single processor complex to support the concurrent execution of multiple operating systems. It consists of special hardware and microcode that can be invoked and controlled in either of two ways: directly through the machine console (hardware logical partitioning) or indirectly under software control by the VM/XA SP control program.
Logical partitioning is a new mode (LPAR) for the IBM 3090E and ES/3090S processor families that is selected at power-on reset (POR) of the processor complex. With the PR/SM feature installed, 3090E and ES/3090S processors have three basic modes--System/370, 370-XA or ESA/370, and a new LPAR mode.
In LPAR mode, main storage and expanded storage are subdivided into contiguous areas with 1-megabyte granularity and allocated to each of the partitions such that each partition appears to have a 0-origin for its storage. All storage addresses used in the instructions or channel program addresses of a partition are relocated by the processors and channels and checked to ensure that they are in the range of physical storage allocated to the partition...
Hardware does most of the virtualization (SIE architecture); the hardware assist is in the SIE implementation. -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 13:10, 28 April 2023 (UTC)
{{
cite journal}}
: CS1 maint: date format (
link)System z host firmware consists of two levels. The first is the lower-level millicode layer. This layer is written in assembly language and runs directly on the z9* processor hardware. It is used to implement performance-critical functions or functions that require direct control of the underlying hardware structures. The millicode layer has to be adjusted for each new System z hardware generation. The second firmware level, which runs on top of the millicode layer and can use functionality provided by the millicode, is the higher-level internal 390 (i390) code. It is written primarily in PL8 or C and implements functions that are less performance-critical or too complex to code in assembly language. An advantage of the i390 code layer is that most parts of it do not have to be adjusted for each new System z processor generation because the underlying millicode layer deals with most of the hardware-specific handling. (See [1] for a discussion of the firmware stack running on a System z.)
But a citation would still be good. Guy Harris ( talk) 19:33, 28 April 2023 (UTC)
Notes
This is the
talk page for discussing improvements to the
Logical partition article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
|
References can be found here [1] —Preceding unsigned comment added by 91.152.200.56 ( talk) 12:10, 2 November 2007 (UTC)
IBM introduced the terms LPAR and PR/SM on the 3090, long after the cited date of 1972. The LPAR support differed from the early CP-67, Virtual Machine Facility/370 and Virtual Machine Facility/System Product in that it was bundled with the processor and didn't offer the user controls of the full VM packages.
As part of any article cleanup, the text copied from references should be properly attributed. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 22:22, 30 June 2010 (UTC)
This article deals with topics that are present also in other vendors (e.g. HP vPAR) but it seems that it only talks about IBM. — Preceding unsigned comment added by 151.99.187.181 ( talk) 11:44, 12 March 2013 (UTC)
Hello fellow Wikipedians,
I have just modified 6 external links on Logical partition. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
{{
dead link}}
tag to
https://www-01.ibm.com/servers/resourcelink/lib03030.nsf/web+search/0E6125F89F8B8EF6852572E6007E884D/$file/sa76-0098.pdfWhen you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 5 June 2024).
Cheers.— InternetArchiveBot ( Report bug) 06:37, 5 January 2018 (UTC)
What happened to https://i.stack.imgur.com/R0K32.png ? — Preceding unsigned comment added by 84.147.35.23 ( talk) 07:51, 26 May 2018 (UTC)
@
Guy Harris: The edit
Special:Permalink/1152075614 has the comment An IBM Systems Journal article on PR/SM suggests it's implemented with low-level hardware and microcode at a level very different from the level at which CP runs.
I'm not aware of any hardware, microcode or millicode support for VM/XA beyond SIE. Is that article available online? My suspicion is that the "hardware and microcode" it is referring to is just SIE. --
Shmuel (Seymour J.) Metz Username:Chatul (
talk)
01:54, 28 April 2023 (UTC)
PR/SM is an optional feature on the IBM 3090 Model E and ES/3090(TM) Model S processor families that allows a single processor complex to support the concurrent execution of multiple operating systems. It consists of special hardware and microcode that can be invoked and controlled in either of two ways: directly through the machine console (hardware logical partitioning) or indirectly under software control by the VM/XA SP control program.
Logical partitioning is a new mode (LPAR) for the IBM 3090E and ES/3090S processor families that is selected at power-on reset (POR) of the processor complex. With the PR/SM feature installed, 3090E and ES/3090S processors have three basic modes--System/370, 370-XA or ESA/370, and a new LPAR mode.
In LPAR mode, main storage and expanded storage are subdivided into contiguous areas with 1-megabyte granularity and allocated to each of the partitions such that each partition appears to have a 0-origin for its storage. All storage addresses used in the instructions or channel program addresses of a partition are relocated by the processors and channels and checked to ensure that they are in the range of physical storage allocated to the partition...
Hardware does most of the virtualization (SIE architecture); the hardware assist is in the SIE implementation. -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 13:10, 28 April 2023 (UTC)
{{
cite journal}}
: CS1 maint: date format (
link)System z host firmware consists of two levels. The first is the lower-level millicode layer. This layer is written in assembly language and runs directly on the z9* processor hardware. It is used to implement performance-critical functions or functions that require direct control of the underlying hardware structures. The millicode layer has to be adjusted for each new System z hardware generation. The second firmware level, which runs on top of the millicode layer and can use functionality provided by the millicode, is the higher-level internal 390 (i390) code. It is written primarily in PL8 or C and implements functions that are less performance-critical or too complex to code in assembly language. An advantage of the i390 code layer is that most parts of it do not have to be adjusted for each new System z processor generation because the underlying millicode layer deals with most of the hardware-specific handling. (See [1] for a discussion of the firmware stack running on a System z.)
But a citation would still be good. Guy Harris ( talk) 19:33, 28 April 2023 (UTC)
Notes