Lines Matching +full:partition +full:- +full:file +full:- +full:system
10 .. NOTE:Eight space tabs are the optimum editor setting for reading this file.
22 2. System Requirements
24 3.1 Built-in:
38 space applications access to the system consoles of logically partitioned
40 ppc64 system. Physical hardware consoles per partition are not practical
41 on this hardware so system consoles are accessed by this driver using
44 2. System Requirements:
54 Sysfs must be mounted on the system so that the user can determine which
55 major and minor numbers are associated with each vty-server. Directions
68 built into the kernel. If not, the default can be over-ridden by inserting
71 3.1 Built-in:
72 -------------
77 Device Drivers --->
78 Character devices --->
84 -----------
89 Device Drivers --->
90 Character devices --->
95 - hvcs.ko
96 - hvcserver.ko
116 source file before building.
126 build a current modules.dep file in /lib/modules/`uname -r` and then
131 The modules.dep file indicates that hvcserver.ko needs to be inserted
132 before hvcs.ko and modprobe uses this file to smartly insert the modules in
138 modprobe -r hvcs
148 |-- *other sysfs base dirs*
150 |-- class
151 | |-- *other classes of devices*
153 | `-- tty
154 | |-- *other tty devices*
156 | |-- hvcs0
157 | | `-- dev
158 | |-- hvcs1
159 | | `-- dev
160 | |-- hvcs2
161 | | `-- dev
162 | |-- hvcs3
163 | | `-- dev
165 | |-- *other tty devices*
167 |-- *other sysfs base dirs*
206 is a vty-server device configured for that node.
212 interact with the device node entries using any standard tty-interactive
214 to provide real time console interaction with a Linux partition's console,
215 which requires the use of applications that provide bi-directional,
249 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node
250 is used to connect to each vty-server adapter. In order to determine which
251 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
252 attribute has been added to each vty-server sysfs entry. This entry is
255 index attribute of vty-server adapter 30000004 shows the following::
260 This index of '2' means that in order to connect to vty-server adapter
263 It should be noted that due to the system hotplug I/O capabilities of a
264 system the /dev/hvcs* entry that interacts with a particular vty-server
265 adapter is not guaranteed to remain the same across system reboots. Look
272 unintended target the Power5 system firmware disables the fetching of data
273 and discards that data when a connection between a vty-server and a vty has
274 been severed. As an example, when a vty-server is immediately disconnected
286 manually terminated vty-server connections on tty close this would close
287 the vty-server and vty connection before the target vty has had a chance to
290 Additionally, disconnecting a vty-server and vty only on module removal or
291 adapter removal is impractical because other vty-servers in other
294 Due to this behavioral restriction disconnection of vty-servers from the
296 outlined below, on the other hand the initial vty-server connection to a
297 vty is established automatically by this driver. Manual vty-server
300 In order to terminate the connection between a vty-server and vty the
301 "vterm_state" sysfs attribute within each vty-server's sysfs entry is used.
303 vty-server adapter. A zero means that the vty-server is not connected to a
307 connection between the vty-server and target vty ONLY if the vterm_state
311 the vty-server connection status and disconnecting a vty-server connection::
321 All vty-server connections are automatically terminated when the device is
327 Each vty-server has a sysfs entry in the /sys/devices/vio directory, which
334 By design, firmware notifies the hvcs driver of vty-server lifetimes and
338 firmware and update the partner info for all the vty-servers that this
348 Vty-server entries in this directory are a 32 bit partition unique unit
349 address that is created by firmware. An example vty-server sysfs entry
361 vty-server
368 /vdevice/vty-server@30000004
370 Each vty-server sysfs dir is provided with two read-only attributes that
382 U5112.428.103048A-V3-C0
383 U5112.428.103048A-V3-C2
384 U5112.428.103048A-V3-C3
385 U5112.428.103048A-V4-C0
386 U5112.428.103048A-V5-C0
389 numbering is only per-partition-unique so entries will frequently repeat.
392 composed of a system serial number followed by "-V*", where the '*' is the
393 target partition number, and "-C*", where the '*' is the slot of the
397 A vty-server can only be connected to a single vty at a time. The entry,
405 8A-V4-C0 > current_vty
407 Changing the current_vty when a vty-server is already connected to a vty
424 access to system consoles.
427 suggested that the user connect to the console hosting partition
431 the next vty-server connection (which may be from another
432 partition) will experience the previously logged in session.
434 ---------------------------------------------------------------------------
446 ---------------------------------------------------------------------------
462 ---------------------------------------------------------------------------
469 HMC by right clicking on the partition and then selecting "close terminal".
473 Power5 systems to determine the many ways a system console can be held.
479 vty-server connection established. They need to free this using the method
495 A: There is not a corresponding vty-server device that maps to an existing
498 ---------------------------------------------------------------------------
506 ---------------------------------------------------------------------------
508 Q: If I already have one Linux partition installed can I use hvcs on said
509 partition to provide the console for the install of a second Linux
510 partition?
515 ---------------------------------------------------------------------------
517 Q: Can I connect to more than one partition's console at a time using this
520 A: Yes. Of course this means that there must be more than one vty-server
521 configured for this partition and each must point to a disconnected vty.
523 ---------------------------------------------------------------------------
527 A: Yes, if you have dlpar and hotplug enabled for your system and it has
531 ---------------------------------------------------------------------------
533 Q: For some reason /dev/hvcs* doesn't map to the same vty-server adapter
536 A: Assignment of vty-server adapters to /dev/hvcs* entries is always done
538 this driver assignment of hotplug added vty-servers may be in a different
541 and vty-server coupling changing if a vty-server adapter was added in a
542 slot between two other vty-server adapters. Refer to the section above
543 on how to determine which vty-server goes with which /dev/hvcs* node.
544 Hint; look at the sysfs "index" attribute for the vty-server.
546 ---------------------------------------------------------------------------
548 Q: Can I use /dev/hvcs* as a conduit to another partition and use a tty
549 device on that partition as the other end of the pipe?
555 partition with the HMC gui which will show up as /dev/hvc* when the target
556 partition is rebooted.
559 current partition and points this at the target partition's newly created
563 Now a program on the target system can be configured to read or write to
564 /dev/hvc* and another program on the current partition can be configured to
568 ---------------------------------------------------------------------------
577 linuxppc-dev@lists.ozlabs.org