MPSS Users Guide-Windows
MPSS Users Guide-Windows
MPSS Users Guide-Windows
(Intel MPSS)
Introduction
Revision History
Revision
Number
Description
Revision Date
3.3
April 2014
3.3
May 2014
(Intel MPSS)
Contents
1
Introduction .................................................................................................................... 9
2.1
2.2
2.3
2.4
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
Configuration................................................................................................................ 16
4.1
4.2
4.3
4.3.2
4.3.3
Networking ....................................................................................... 17
Document Number: 330077-001US
Introduction
4.4
4.5
Bridging ............................................................................................................. 18
4.5.1
4.5.2
4.5.3
Routing ............................................................................................... 21
5.2
5.3
5.1.2
5.1.3
5.1.4
5.2.2
5.2.3
6.1.2
6.1.3
6.1.4
(Intel MPSS)
6.1.5
6.1.6
6.2
6.3
6.4
7.2
10
11
12
Introduction
14
15
16
(Intel MPSS)
17
Related Documentation............................................................................................ 73
17.1 MYO Documentation ..................................................................................... 73
17.1.1 MYO Tutorials & Other Document Location on Windows*73
17.2 COI Documentation ...................................................................................... 73
17.2.1 COI Documentation for Windows* .......................................... 73
17.3 Intel Xeon Phi Coprocessor Collateral ........................................... 73
List of Figures
Figure 1 Boot process for Intel MPSS ............................................................................... 12
Figure 2 Internal Bridge Network..................................................................................... 18
Figure 3 External Bridge Network .................................................................................... 20
Figure 4 File Sharing screen .............................................................................................. 53
Figure 5 Advanced Sharing screen .................................................................................... 53
Figure 6 Permissions for Winshare window ..................................................................... 54
Introduction
Introduction
The Intel Xeon Phi coprocessors are PCIe based add-in cards that run a version of
Linux* tailored for these coprocessors. The Linux* OS for Intel Xeon Phi coprocessors,
as well as a range of drivers and utilities, are included in the Intel Manycore Platform
Software Stack (Intel MPSS). The responsibilities of these drivers and utilities include:
Placing the Linux* boot image and root file system into coprocessor memory.
Controlling coprocessor booting, shutdown and reset.
Providing an IP (over PCIe) networking connection to each coprocessor.
Directing power management of each coprocessor.
Supporting high speed data transfer to and from the coprocessor.
The PCIe bus is the only communication channel available to the Intel Xeon Phi
coprocessors. Therefore configuration and provisioning of the OS to be executed on
each Intel Xeon Phi coprocessor is performed by the host system in which the
coprocessor is installed.
The Linux* kernel and file system image for the Intel Xeon Phi coprocessors are
installed into the host file system as part of Intel MPSS installation. The coprocessor file
system image can be configured through the use of the micctrl utility described below
and/or directly by the host root.
The micx64.sys driver is the component of Intel MPSS that provides PCIe bus access and
implements the coprocessor boot process. To boot a coprocessor, micx64.sys injects the
Linux* kernel image and a kernel command line into coprocessor memory and signals it
to begin execution. A virtual network driver is installed as micvethx64.sys. Finally,
micx64.sys directs power management of the installed coprocessors and provides a high
speed data transfer over PCIe through its Intel Symmetric Communications Interface
(SCIF) driver.
Micctrl is a utility through which the user can control (boot, shutdown, reset) each of
the installed Intel Xeon Phi coprocessors. Micctrl also offers numerous options to
simplify the process of configuring each coprocessor. Section 5 of this document, The
micctrl Utility, describes the micctrl utility in detail.
(Intel MPSS)
2.1
2.2
2.3
NOTE:
10
The default configuration specifies that each Intel Xeon Phi coprocessor card is
booted when the host driver is loaded. This means that the Intel Xeon Phi
coprocessors will boot when the host system restarts. To start the Intel Xeon Phi
coprocessors, execute the following command as an Administrator:
Admin> micctrl --start
The call to micctrl will exit when it determines the Intel Xeon Phi coprocessor cards
have either booted successfully or failed to boot.
2.4
Used to highlight the elements of a graphical user interface such as buttons and
menu names.
[ items ]
{ item | item }
Indicates to select only one of the items listed between braces. A vertical bar ( | )
separates the items.
... (ellipses)
\ (backslash)
micN
Denotes a name such as mic0, mic1, etc. where N=0,1, 2, For example: the
file name micN.conf denotes file names mic0.conf, mic1.conf, etc.
User>
Admin>
[micN] $
[micN] #
11
(Intel MPSS)
Micctrl utility
instructs MIC
driver to boot
Intel Xeon Phi
coprocessor
Is root device
initial ram disk?
No
Root device is
tmpfs Ram Disk
Execute /sbin/init
in initial ram disk
Request and
download tmpfs
image from mpss
service
Execute /sbin/init
in new root
partition
3.1
3.1.1
3.1.2
13
(Intel MPSS)
3.1.3
3.1.4
3.1.5
3.1.6
14
15
(Intel MPSS)
Configuration
This section focuses on configuring Intel Xeon Phi coprocessor cards, including
configuration files, kernel command line parameters, and authentication.
4.1
Configurable Components
On a typical Linux* system, the installation and configuration process is performed as a
series of questions posed by the system and answered by the installer/operator. Since
the Intel Xeon Phi coprocessor cards do not have a file system of their own, this
process is replaced by editing the configuration files and using the micctrl utility.
The configuration parameters have three categories:
1) Parameters that control loading the Intel Xeon Phi coprocessor Linux* kernel
onto the card and initiating the boot process.
2) Parameters to define the root file system to be used on the card.
3) Parameters to configure the host end of the virtual Ethernet connection.
4.2
Configuration Files
This section briefly discusses configuration file formats and use of the Include
parameter to micctrl.
4.2.1
4.3
16
Configuration
configuration files and builds the kernel command line from relevant parameters. By
default, the boot parameters are placed in the per-card micN.xml files, allowing each
card to be configured independently of the other cards. If a boot parameter is placed in
the global.xml file then it will apply to all cards unless overridden
4.3.1
Power Management
The PowerManagement parameter specifies the Intel Xeon Phi coprocessor Linux*
power management settings. The system owner can specify different power
management settings by editing these values. The changes takes effect upon executing
either micctrl --start or micctrl -b.
4.3.2
Command Line
The CommandLine parameter controls what options are passed to the Intel Xeon Phi
coprocessor when an Intel Xeon Phi coprocessor starts.
4.3.3
Networking
The Networking parameters specify various settings such as IPAddress, HostIPAddress,
Subnet, MACAddress, and HostMACAddress. These settings will not take effect until
the Intel Xeon Phi coprocessor is restarted.
4.4
17
(Intel MPSS)
4.5
Bridging
Windows* provides functionality for creating a software bridge that connects two or
more networks so that they can communicate. Network packets received on any of
these bridged networks are passed unchanged to the bridge.
The bridge is assigned the IP address associated with the system on which it exists.
Network packets arriving on any of the physical interfaces are passed to the bridge. If
the destination for the packet is the IP address assigned to the bridge, it is passed to the
TCP/IP stack on the system. If it is any other destination, the bridge performs the role
of a network switch and passes it to the correct physical interface for retransmit.
Steps to create a network bridge in Windows*:
1) Open Network Connections (Hold <WIN+r> to open Run dialog. Enter ncpa.cpl and
click OK).
2) Hold down CTRL and select each network connection that you want to add to the
bridge.
3) Right-click one of the selected network connections, and then click Bridge
Connections (administrator privileges are required).
4.5.1
Internal Bridging
Internal bridging is a term created to describe a networking topology with Intel Xeon
Phi coprocessors connected through a bridged configuration. The advantage of the
internal bridge over the default static pair network configuration is the ability for the
coprocessors to communicate with each other as well as the host.
Configuration
communicate outside through the 12.12.12 subnet but the coprocessors cannot. The
configuration required to create this topology would be:
mic0.xml
<IPAddress>10.10.10.1</IPAddress>
<HostIPAddress>10.10.10.254</HostIPAddress>
<Subnet>255.255.255.0</Subnet>
mic1.xml
<IPAddress>10.10.10.2</IPAddress>
<HostIPAddress>10.10.10.254</HostIPAddress>
<Subnet>255.255.255.0</Subnet>
4.5.2
External Bridging
External bridging is a term used in the Intel MPSS software to describe a network
topology where the virtual network interfaces are bridged to a physical network
interface. This is the desired configuration in clusters.
The current release of Intel MPSS for Windows* supports creating a static external
bridge configuration. A dhcp-based external bridge configuration is planned for a future
release.
19
(Intel MPSS)
Configuration
<HostIPAddress>10.10.10.5</HostIPAddress>
<Subnet>255.255.255.0</Subnet>
mic1.xml
<IPAddress>10.10.10.7</IPAddress>
<HostIPAddress>10.10.10.5</HostIPAddress>
<Subnet>255.255.255.0</Subnet>
Currently, the micctrl utility does not support setting up the default gateway in the
Intel Xeon Phi coprocessor for external bridge configuration, so it is necessary to
manually change it using the following command.
4.5.3
Routing
Windows* provides functionality to route network traffic between two or more
networks. IP routing is disabled by default in Windows*.
Steps to enable routing in windows:
1) Go to Run; type "cmd" (without quotes).
2) Enter the following commands:
User> sc config RemoteAccess start= auto
User> sc start RemoteAccess
There is no change needed in the configuration files for each coprocessor in order to
support this. Since micctrl utility currently does not support setting up the default
gateway in the Intel Xeon Phi coprocessor, it is necessary to manually change it using
the following command:
User> route add default gw <IP Address of
the Host machine>
21
(Intel MPSS)
The micctrl utility requires a first argument specifying the action to perform, followed
by option-specific arguments. The arguments may be followed by a list of Intel Xeon
Phi coprocessor card names, which is shown in the syntax statements as [mic card
list]. The card list will be a list of the card names. For example: the list may be mic1
mic3, if these are the cards to control.
5.1
NOTE:
5.1.1
5.1.2
22
NOTE:
5.1.3
Performing a reset may result in the loss of file data that has not been flushed to a
remote file.
5.1.4
5.2
5.2.1
5.2.2
23
(Intel MPSS)
5.2.3
5.3
5.3.1
24
Adding Software
Adding Software
Typical installations are not static, and usually require the system administrator to add
additional files or directories to the Intel Xeon Phi root file system that is
downloaded to the card.
6.1
6.1.1
25
(Intel MPSS)
6.1.2
6.1.3
6.1.4
26
Adding Software
6.1.5
6.1.6
6.2
27
(Intel MPSS)
6.3
6.4
6.4.1
28
7.1
Simple Method
The following is the simplest way to execute Micinfo:
User> micinfo
7.2
29
(Intel MPSS)
30
31
(Intel MPSS)
10
10.1
Severity Level
Message Body
Simple Method
Micras is installed as a Windows* service.
The following is the simplest way to start micras service:
Admin> micctrl --start
Admin> net start micras
To stop micras service, execute the following command:
Admin> net stop micras
10.1.1
32
10.2
OPTIONS:
-help : Display command help information.
-maint : Enable maintenance mode for error test and repair.
-loglevel [loggingLevel] : set the level of detail that gets logged with the
micras tool. The accepted levels are from 1 to 15.
It is a 4-bit representation, where bits 0 - 3 denote the following:
The severity level of micras log messages is mostly aligned with the standard RFC 5424
syslog severity level. Currently, there are four severity levels available (see Table 2
Severity Levels).
If micras is executed with no arguments, it runs at the console prompt, connects to
devices, and waits for errors.
Use Ctrl-C to exit micras and return to the console prompt.
Use -maint option to enable maintenance mode for error test and repair.
Use -help to show the help info.
The severity level of micras log messages is mostly aligned with the standard RFC 5424
syslog severity level. Currently, there are four severity levels available (see Table 2
Severity Levels).
User's Guide (Windows)
33
(Intel MPSS)
Severity
Description
General Description
Action
INFO
Informational
messages
No action required.
WARNING
Warning
conditions
No immediate
action required.
ERROR
Error conditions
Inform your
system
administrator.
CRITICAL
Critical
conditions
Immediate action
required for some
error conditions
34
11
NOTE:
35
(Intel MPSS)
12
NOTE:
NFS server is supported on Windows* Server 2008 R2 SP1, Windows* Server 2012, and
Windows* Server 2012 R2 only. It is NOT supported on Windows* 7 or Windows*
8/8.x.
12.1
12.1.1
36
3) Continuing in the wizard, under File Service -> Role Services, select Services for
Network File System.
NOTE:
4) Click Next and then click Install. In the Results pane, confirm that the installation
was successful.
12.1.2
was just added under Roles ->File Services. Click Action -> Edit NFS Configuration
37
(Intel MPSS)
2) Select Use Services for NFS to Share Folders and click Provision a Shared Folder
Wizard.
3) On the Shared Folder Location page of the wizard, enter a Location value for the
NFS share.
38
5) Select the NFS check box and fill in the Share name field.
6) Under Enable unmapped user access, select Allow unmapped user Unix access (by
UID/GID).
12.1.3
2) Now, specify a host and set its permissions to Read-Write. Select Allow root access.
Click OK to return to the previous dialog box.
39
(Intel MPSS)
3) Verify the Host has Read-Write permissions and Root Access is Allowed. Click Next,
then click Create.
4) Close the Provision a Shared Folder Wizard, Services for NFS Configuration Guide
dialog box, and Server Manager.
5) Proceed to Section 12.3, Mount the NFS Share.
12.2
40
method using PowerShell* cmdlets, skip to Section 12.2.4, Use PowerShell* Cmdlets to
Create NFS Share (optional).
12.2.1
2) In the Add Roles and Features Wizard, click Installation type in the left column.
Select Role-based or feature-based installation.
3) Click Server Selection and Select a server from the server pool. Select the server.
41
(Intel MPSS)
4) Click Server Roles. Under Roles, expand File and Storage Services, then expand File
and iSCSI Services. Select Server for NFS.
42
5) A confirmation dialog box will appear. Click the Add Features button.
6) Returning to the Add Roles and Features Wizard, select Confirmation in the left
column. Click the Install button.
43
(Intel MPSS)
12.2.2
44
2) Select the desired server from the list. Click Shares in the left column.
4) In the New Share Wizard, click Select Profile and select NFS Share - Quick.
45
(Intel MPSS)
5) Click Share Location and select the desired server from the list. Specify a path for
the share.
6) Click Share Name and specify a name for the share (click OK if prompted to create
the share location directory).
46
12.2.3
47
(Intel MPSS)
2) Return to the New Share Wizard and click Add. Now, select Host in the Add
Permissions dialog box. Specify a host and set its Share Permissions field to
Read/Write. Select Allow root access. Click Add.
3) Return to the New Share Wizard. Review the Share Permissions settings. Verify the
Host has Read/Write permissions and Root Access is Allowed.
48
4) In the left column, click Permissions then click Confirmation. Confirm your settings
and click Create.
5) Confirm your results and close New Share Wizard and Server Manager.
49
(Intel MPSS)
12.2.4
NOTE:
The backslash \ character, placed at the end of a line, is used to indicate continuation of
a command on the next line. It is not part of the command itself.
1) Add the NFS server:
User> Add-WindowsFeature FS-NFS-Service
2) Provision the directory to be shared:
User> New-Item C:\MY_NFS_TEST -type directory
User> New-NfsShare -Name nfs-tests \
-Path C:\MY_NFS_TEST -EnableUnmappedAccess $True \
-Permission no-access -Authentication sys
3) Grant read/write and root access permissions for Host 192.168.1.100:
User> Grant-NfsSharePermission Name nfs-tests
-Permission readwrite -ClientName 192.168.1.100 \
-ClientType Host -AllowRootAccess $True
4) Confirm share permission settings:
User> Get-NfsSharePermission Name\
nfs-tests
5) Proceed to Section 12.3, Mount the NFS Share.
50
12.3
NOTE:
This section applies to Windows* Server 2008 R2 SP1, Windows* Server 2012, and
Windows* Server 2012 R2.
NOTE:
Refer to Section Error! Reference source not found., External Tools for information
on downloading and installing PuTTY tools.
1) Change to the directory where PuTTY tools are installed:
User> cd C:\Program Files\Intel\MPSS\bin
2) Login to the Intel Xeon Phi coprocessor card as root:
User> putty.exe -ssh -i \
<PATH_TO_PRIVATE_KEY> [email protected]
where <PATH_TO_PRIVATE_KEY> corresponds to the location and name of the
private key file associated with this coprocessor.
NOTE:
If prompted for a password, see Section 14.3 on setting up user SSH keys for the root
user.
3) On the Intel Xeon Phi coprocessor card, add a directory with the same name as
the NFS share:
[root@knightscorner ~]# mkdir /tmp/nfs-tests
where N is the integer ID of that card (for example: mic0, mic1, etc.).
4) Mount the NFS share from the Intel Xeon Phi coprocessor card. The nolock
option is required on this step:
[root@knightscorner ~]# mount -t nfs -o nolock \
192.168.1.99:/nfs-tests /tmp/nfs-tests
5) Navigate to the directory that you created on the Intel Xeon Phi coprocessor
card. Verify that the contents of the NFS share are visible.
[root@knightscorner ~]# cd /tmp/nfs-tests
51
(Intel MPSS)
13
13.1
the configuration file, filelist and fstab with minimum required settings to mount as a
guest user.
NOTE:
52
Navigate to Control Panel > Network and Sharing Center > Change
advanced sharing settings > Public profile > Enable Turn off password
protected sharing and save changes.
Navigate to the properties of the directory you want to share Sharing >
Share. Add Everyone to the share group, assign appropriate
permissions and select Share. (See: Figure 4 File Sharing screen)
Navigate to Advance Sharing from Properties window and select Share this
folder. (See: Figure 5 Advanced Sharing screen)
53
(Intel MPSS)
You have to enable share permissions in both Share and Advanced Sharing. The current
mount utils on coprocessor card do not support nested host share paths.
2. Run micctrl --addcifs
You can use this option to enable mount on required cards by specifying [mic
card list]. If not specified, micctrl --addcifs enables mount on all cards in the
system. Running this command should add a <CIFS> entry in micN.xml file.
Example:
micctrl --addcifs winshare /mnt/wincifsshare mic0 mic2
micctrl --addcifs winshare /mnt/wincifsshare
54
You can manually edit the configuration file micN.xml if you want to modify a mounted
share,it is the same as adding additional mount options. <card mount point> is used as
unique identifier when there are multiple CIFS shares for example.; there should be one
<CIFS> entry per mount point in configuration file. You may want to delete the old
settings from fstab to avoid conflict. You have to restart the card to access the new
mounted share.
You have the option to manually mount and umount password protected shares as the
root user on the card.
When accessing the share files on the card, you could encounter cannot allocate
memory error. This error can be avoided by maximizing the throughout for file sharing
and/or network applications in the registry.
Set the following value to 2 or 3 (for large file transfers)
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\size
Reboot your host or restart the Server service in services.msc after making the changes.
References:
http://support.microsoft.com/kb/232271
http://msdn.microsoft.com/en-us/library/ee377058(v=bts.10).aspx
13.2
micctrl --removecifs option prepares the setup required for umount. It doesnt
do the actual umount but instead cleans up the configuration, filelist and fstab
settings updated in --addcifs step. You have to restart the cards for removing the
mounted share.
User's Guide (Windows)
55
(Intel MPSS)
56
14
14.1
External Tools
Some Intel tools require that PuTTY and PuTTYgen must be installed. Download PuTTY
and PuTTYgen from the link:
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
Install PuTTY and PuTTYgen to the same location as the external tools
(C:\Program Files\Intel\MPSS\bin).
14.2
14.3
57
(Intel MPSS)
2) Click Save public key to save the public key to disk in SSH-2 format. For example:
save the key with the name publicKeys.pub. Click Save private key to save the
private key in a secure location not readable by other users. This key will be used
later to connect to the Intel Xeon Phi coprocessor. For example: save the key
with the name privateKeys.ppk onto your Desktop. Optionally, save it with a
passphrase; otherwise, click Yes to ignore the warning. Close the PuTTYgen tool.
3) Open a command prompt as an Administrator. Run the command:
Admin> micctrl --addssh <username> -f <path-to-key-file>
where <username> is the actual username to link with this SSH key and <pathto-key-file> is the full path to the public key file (saved during key generation).
NOTE:
where <username> is the actual username to link with this SSH key and <publickey> is the key that was copied to the clipboard from the PuTTYgen tool. Paste
<public-key> directly into the command.
4) Restart the Intel Xeon Phi coprocessor using the micctrl utility. Note that a host
reboot is not sufficient to generate a new filesystem. Now use standard SSH tools to
58
interact with the coprocessor once its state changes to online. Note the user
which now has SSH privileges that is the username that you will use to interact
with the coprocessor. The default accounts on the Intel Xeon Phi coprocessor are
root and micuser. The special user account micuser is used exclusively for COI
offload applications. Users are not permitted to login as micuser.
5) Once MPSS has started, start PuTTY.exe. In the Category box, expand Connection ->
SSH and select Auth. In the Private key file for authentication field, browse to the
Desktop and select privateKeys.ppk (saved during key generation).
6) In the Category box, select Session at the top and click Save (you can choose default
or create a new session name). This allows easy reconnection to the coprocessor
without specifying private keys each time.
7) In the Host Name (or IP address) field, enter 192.168.1.100 and then click Open.
8) When the putty session opens to the coprocessor, enter the username specified in
the micctrl --addssh <username> step. At this point, if the keys are correctly
set up it will not ask for a password. You should now have a terminal session set up
to the file system on the coprocessor.
After completing these steps, a program such as WinSCP can be used to transfer files to
and from the coprocessor.
14.3.1
59
(Intel MPSS)
2) In the Advanced Site Settings dialog, select SSH -> Authentication. In the Private
key file field, enter the full path to the private key file generated above (or click
to browse to the file). Click OK to return to the previous dialog.
3) Optionally, click Save As to save the new site to the tree in the left pane. Click
Login to use the tool.
60
14.4
User Groups
The default users for the Intel Xeon Phi coprocessor are root and micuser. The special
user account micuser is used exclusively for COI offload applications. Users are not
permitted to login as micuser. The administrator can add additional users. Any new user
for the coprocessor must have a corresponding local or domain user account.
1) Click the Windows* Start button. Enter Run in the Search Programs and Files search
box and press Enter.
The Run window appears.
2) Enter lusrmgr.msc in the Open drop down box of the Run window and press Enter.
3) Right click Users from the left pane and select New User from the pop up menu to
add a new user.
4) Right click Groups from the left pane, and select New Group. Type MICUSERS in the
box titled Group name. Click Add under the Members box, and type in the name of
the User you created in Step 3. After adding the user, select Create to create the
MICUSERS group.
NOTE:
Only users listed in the MICUSERS group are permitted to log into the coprocessor. After
adding or deleting users in the MICUSERS group, the coprocessor must be stopped and
started again.
61
(Intel MPSS)
14.4.1
NOTE:
14.5
Only users listed in the MICUSERS group are permitted to log into the coprocessor. After
adding or deleting users in the MICUSERS group, the coprocessor must be stopped and
started again.
14.6
62
14.7
14.8
14.9
Troubleshooting
This section describes several methods of troubleshooting and recovery during the
following events:
1) The coprocessor times out during the boot process
2) The coprocessor will not start
The micctrl utility logs information related to events in the Windows* Event Viewer. To
open the event viewer, click the Start button and type Event Viewer. In Event Viewer,
in the left column, expand Applications and Services and double-click MPSSLog.
This will display the following window:
63
(Intel MPSS)
This event log should be checked in case of any observable failure starting or stopping
coprocessors. Failures include timeouts and errors running micctrl --start,
micctrl --stop, micctrl -r, and micctrl -b.
The event log for the coprocessors can be saved to a file from the command line with
the following command (run as administrator):
Admin> wevtutil qe /f:text mpsslog > output.txt
Currently, it is recommended to use DebugView to obtain troubleshooting information
related to the kernel mode drivers. DebugView can be obtained from the following
website:
http://download.sysinternals.com/files/DebugView.zip
Once the zip file has been extracted, run Dbgview.exe as Administrator. From the
Capture menu, make sure to select Capture Global Win32, Capture Kernel, and Enable
Verbose Kernel Output. The result should look like the following image:
64
Certain host kernel mode driver events will print a message to this window. To capture
the output, click File and Save As, and enter the desired filename. DebugView is useful
in cases where the micctrl utility gives commands to boot the coprocessor but the host
driver fails the boot request.
Some errors can be caused by incorrect filelist specifications. See Section 6, Adding
Software, for more details on the filelist syntax. If the filelist is incorrect, the micctrl
utility cannot boot the coprocessors. To verify that the filelist syntax is correct before
attempting to boot the coprocessors, run micctrl -g to see errors listed on the command
line. Once the micctrl utility has attempted to boot the coprocessors, the same error
messages will be listed in the Event Viewer log.
65
(Intel MPSS)
15
15.1
Requirements
1) Intel Composer XE Requirements
There are two options to installing the Intel Composer XE requirements. The first
option is to install the full Intel Composer XE MSI package.
If the full composer installation is not available, then two packages can be used
instead. The required shared object libraries can be installed via the Intel
Composer XE redistributable package, freely distributed on the web at:
http://software.intel.com/en-us/articles/redistributable-libraries-for-intel-c-andvisual-fortran-composer-xe-2013-sp1-for-windows
This download has an MSI package which will set up the environment and install the
required dependencies.
Besides the shared object libraries, the MKL Linpack benchmark is also a
requirement. This is also freely distributed on the web at:
http://software.intel.com/en-us/articles/intel-math-kernel-library-linpackdownload
This download is a zip file that can be unpacked anywhere, but the environment
variable MKLROOT must point to the top level directory of the untarred package.
For instance, if the user extracted the zip file into their home directory they should
set MKLROOT as follows:
User> set MKLROOT=%HOMEPATH%\linpack_11.1.0
If MKLROOT is set in the user's shell environment at run time then micprun will be
able to locate the linpack binaries. Note that the version of linpack linked above
may be newer than 11.1.0, and MKLROOT variable should reflect this.
2) MATPLOTLIB Requirements
The micpplot and micprun applications use the MATPLOTLIB Python module to plot
performance statistics. The micprun application only creates plots when verbosity
is set to two or higher, and only requires MATPLOTLIB for this use case.
MATPLOTLIB must be installed in order to create plots. Download it from:
66
matplotlib.sourceforge.net
3) PuTTY Requirements
The PuTTY command line utilities pscp.exe and plink.exe must be installed to a
location referenced by the user's PATH environment variable. Refer to Section 14.1,
External Tools for information on downloading PuTTY tools.
NOTE:
The user ID and SSH key required to log into the card can be set with the environment
variables INTEL_MPSS_USER and INTEL_MPSS_SSH_KEY respectively.
NOTE:
15.2
Distributed Files
The micperf software is part of the Intel MPSS EXE package and will be installed along
with the rest of MPSS by default. The Intel MPSS EXE installs the micperf files to the
directories:
15.3
NOTE:
C:\Program Files\Intel\MPSS\sdk\tutorials\micperf
C:\Program Files\Intel\MPSS\sdk\micperf\micp
Benchmark binaries:
C:\Program Files\Intel\MPSS\sdk\micperf\libexec
Reference data:
C:\Program Files\Intel\MPSS\sdk\micperf\data
67
(Intel MPSS)
Once the Intel MPSS EXE package has been installed, an additional step is required to
access the micp Python package: either install it to your global Python site packages, or
set up your environment to use the micp package from the installed location.
To install into the Python site packages, open a Windows* command prompt as
administrator and run the following two commands:
Admin> cd C:\Program Files\Intel\MPSS\sdk\micperf\micp
Admin> setup.py install
This method provides access to the micp package and executable scripts by all nonadmin users who use the same Python version as the administrator. If Python is in the
default location and uses a standard configuration, setup.py installs the micp package to
the directories:
C:\PythonXY\Scripts
C:\PythonXY\Lib\site-packages\micp
An intermediate product of running setup.py install is the creation of the directory:
C:\Program Files\Intel\MPSS\sdk\micperf\micp\build
None of the products of running setup.py discussed above will be removed by
uninstalling the Intel MPSS EXE. The installation with setup.py uses Python's distutils
module, and this module does not support uninstall.
68
Important Considerations
16
Important Considerations
16.1
69
(Intel MPSS)
16.2
16.3
70
Important Considerations
rate (default 1 hertz), in order to communicate that the peers are still operating
properly.
When a MYO application is stopped at a breakpoint in a debugger, the MYO
WATCHDOG MONITOR assumes that the host or card side of the MYO application has
suffered a fatal error and will abort, thus preventing debug of the MYO application.
WARNING:
To debug MYO applications for this release, the MYO WATCHDOG MONITOR must be
turned off prior to starting the MYO application on the host. To do so, set the
environment variable: MYO_WATCHDOG_MONITOR to the value -1.
NOTE:
16.4
There is no support for attaching to a MYO application where the MYO WATCHDOG
MONITOR is currently operating. This will be resolved in a future release of the MYO
runtime.
5. Copy the coreutils and libgmp RPMs to the card with a secure copy tool such as
pscp.exe.
User> pscp -scp -i <PATH_TO_PRIVATE_KEY> coreutils*.rpm
[email protected]:/tmp
User> pscp -scp -i <PATH_TO_PRIVATE_KEY> libgmp*.rpm
[email protected]:/tmp
71
(Intel MPSS)
As an alternative mechanism for installing rpm files, once the coreutils are
installed, zypper can be used to install rpm files as follows:
[root@<host_machine>-MicN ~]# zypper --no-gpg-checks \
install /tmp/<rpm_package_name>
72
Related Documentation
17
Related Documentation
This section contains a listing of MYO and COI documentation, as well as links to various
Intel Xeon Phi Coprocessor collateral documents.
17.1
MYO Documentation
17.1.1
17.2
COI Documentation
17.2.1
17.3
-release_notes.txt
(Future release)
-coi_getting_started.pdf
-MIC_COI_API_Reference_Manual_0_65.pdf
(INTEL_MPSS_HOST_SDK)\include\intel-coi\
(INTEL_MPSS_HOST_SDK)\tutorials\coi\
-README_Windows_1.txt
(for how to get card side binaries and general
building and use of tutorials)
73
(Intel MPSS)
https://www-ssl.intel.com/content/www/us/en/processors/xeon/xeon-phicoprocessor-safety-compliance-guide.html
Intel Xeon Phi Coprocessor Datasheet:
https://www-ssl.intel.com/content/www/us/en/processors/xeon/xeon-phicoprocessor-datasheet.html
Intel Xeon Phi Coprocessor Software Users Guide:
https://www-ssl.intel.com/content/www/us/en/processors/xeon/xeon-phicoprocessor-software-users-guide.html
Intel Xeon Phi Coprocessor System Software Developers Guide:
https://www-ssl.intel.com/content/www/us/en/processors/xeon/xeon-phicoprocessor-system-software-developers-guide.html
Intel Xeon Phi Coprocessor Developers Quick Start Guide:
http://software.intel.com/en-us/articles/intel-xeon-phi-coprocessor-developers-quickstart-guide
Intel Xeon Phi Coprocessor System Administration Guide:
http://software.intel.com/en-us/articles/system-administration-for-the-intel-xeon-phicoprocessor
Intel Xeon Phi Coprocessor Instruction Set Architecture Reference Manual:
http://software.intel.com/sites/default/files/forum/278102/327364001en.pdf
74