Displaying 4 results from an estimated 4 matches for "init_sched_switch_trac".
Did you mean:
init_sched_switch_trace
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2008 Jul 07
10
[PATCH RFC 0/4] Paravirtual spinlocks
At the most recent Xen Summit, Thomas Friebel presented a paper
("Preventing Guests from Spinning Around",
http://xen.org/files/xensummitboston08/LHP.pdf) investigating the
interactions between spinlocks and virtual machines. Specifically, he
looked at what happens when a lock-holding VCPU gets involuntarily
preempted.
The obvious first order effect is that while the VCPU is not
2010 Nov 16
0
Bug#603727: xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver)
...0xd returned 0 after 14 usecs
[ 37.921572] calling init_tracepoints+0x0/0xa @ 1
[ 37.926338] initcall init_tracepoints+0x0/0xa returned 0 after 0 usecs
[ 37.932923] calling init_events+0x0/0x53 @ 1
[ 37.937344] initcall init_events+0x0/0x53 returned 0 after 1 usecs
[ 37.943583] calling init_sched_switch_trace+0x0/0xa @ 1
[ 37.948957] initcall init_sched_switch_trace+0x0/0xa returned 0 after 1 usecs
[ 37.956148] calling init_blk_tracer+0x0/0x47 @ 1
[ 37.960917] initcall init_blk_tracer+0x0/0x47 returned 0 after 0 usecs
[ 37.967502] calling perf_event_sysfs_init+0x0/0xf @ 1
[ 37.972704] initc...