Re: DMESG Output Indicating Potential CPU Errors?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 13/6/20 6:12 am, Samuel Sieb wrote:
On 6/12/20 10:17 AM, Gordon Messmer wrote:
On 6/11/20 10:24 PM, Samuel Sieb wrote:
You can also specify that certain cores are dedicated to certain processes and the kernel won't schedule anything else on them.


It looks like you can do that using a boot-time kernel argument (isolcpus), or by creating new exclusive cpusets.  I wasn't previously aware of those options.  As far as I can tell, though, you won't get that effect from merely pinning the guest to a set of CPUs.

You're right, there are two sides.  There's restricting the process to certain cores and there's dedicating cores to certain processes.
The origonal reason for this thread was the issue with DMESG seeming to indicate a possible hardware issue on what looked to be core 7, or whether is was just that the monitoring process couldn't access the core at the time. Sharing of lpars becomes a moot point if you are running a vm client under windows or linux, setting up lshaped lpars only really becomes relevant when the vm os is using the cpu and all your systems, windows or linux or anything else are all running in vms, where you can configure the sharing/exclusivity of the cpus/cores to be managed by the vm os. Having said this though the cpus potentially still have to be shared between the vm os and the vm images, unless the vm os has the capability of reserving cpus/cores for itself and farming out the rest, in which case the cpu settings in the vm images are only relevant to whether or not the vm images themselves will share cpus with each other.

regards,
Steve

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux