For linux it looks in /proc/cpuinfo and tries using uname. For Windows it looks like it uses the registry. To get the first processor name using this module: import cpuinfo cpuinfo.cpu.info0'model name' 'Intel(R) Pentium(R) 4 CPU 3.60GHz' If its got more than one processor, then the elements of cpuinfo.cpu.info will have their names. I am new to the world of Linux and Ubuntu. I want say get maximum information about CPU. Of threads per core, instruction set, size of caches, instruction set, virtuali. $./cpuinfo.bash cpuinfocurfreq: 260 2667000 cpuinfomaxfreq: 260 2667000 cpuinfominfreq: 110 1199000.

Because CRIU allows to live migrate containers (see live migration for details), it might happen that CPU a container has been ran on differs from the target CPU. For most software this is usually not a problem, but if a program is compiled with optimizations involving a particular CPU feature (say, AVX instruction), the lack of the feature on a destination machine will lead to execution exception in a best case scenario.

Therefore there should be a way to test if destination machine is capable of running container to be migrated. This is the purpose of cpuinfo command.

Saving CPU capabilities into an image file[edit]

CRIU does not write CPU capabilities into an image by default (for the sake of speed). Instead, one have to run CRIU as:

The command creates a cpuinfo image file, containing information about the current CPU and some bits representing the supported capabilities.

Testing CPU capabilities[edit]

To check if the capabilities saved in cpuinfo image file are matching those of the current CPU, one should run:

Checkpoint/Restore with CPU capabilities[edit]

While by default CRIU does not save CPU capabilities in image file, one can pass --cpu-cap option to force CRIU to save and check CPU capabilities on dump and restore accordingly.

By Mark Russinovich

Published: February 22, 2021

Download Coreinfo(370 KB)

Introduction

Coreinfo is a command-line utility that shows you the mapping between logical processors and the physical processor, NUMA node, and socket on which they reside, as well as the cache’s assigned to each logical processor. It uses the Windows’ GetLogicalProcessorInformation function to obtain this information and prints it to the screen, representing a mapping to a logical processor with an asterisk e.g. ‘*’. Coreinfo is useful for gaining insight into the processor and cache topology of your system.

Installation

You run Coreinfo by typing 'coreinfo”.

Using CoreInfo

For each resource it shows a map of the OS-visible processorsthat correspond to the specified resources, with '*' representing theapplicable processors. For example, on a 4-core system, a line in thecache output with a map of shared by cores 3 and 4.

Usage: coreinfo [-c][-f][-g][-l][-n][-s][-m][-v]

All options except -v are selected by default.

Cpuinfo Ubuntu

Coreinfo Output:

Cpuinfo Python

Download Coreinfo(370 KB)