* pin hypervisor to physical cpu
@ 2012-06-14 20:58 Xin Xu
0 siblings, 0 replies; only message in thread
From: Xin Xu @ 2012-06-14 20:58 UTC (permalink / raw)
To: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 859 bytes --]
Hi everyone,
I am trying to identify the current running task is belonging to domu, dom0
or hypervisor. So I figured if I can separate domu, dom0 and hypervisor to
different physical CPUs, then I can just look at cpu and then tell the task
belongs to which. I use xm vcpu-pin to pin domu and dom0, but it does not
work for hypervisor. I am just wondering if there is a way to pin
hypervisor to a specific cpu?
I am just trying to better understand how this "pinning" cpu works. If I
pin domu to cpu 0, does that mean all instructions belongs to domu will run
in cpu 0? Does that mean cpu 0 will be exclusively assigned to domu and
will not run any instructions from dom0 and hypervisor? I pin dom0 to cpu
0, and dom1 to cpu1, but i still see instructions running in cpu 2 and 3.
How can I tell what are those instructions in cpu 2 and 3?
Thank you
Xin Xu
[-- Attachment #1.2: Type: text/html, Size: 989 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-06-14 20:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-14 20:58 pin hypervisor to physical cpu Xin Xu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).