search for: kvm_clock_read

Displaying 20 results from an estimated 26 matches for "kvm_clock_read".

2018 Aug 05
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
...d9c/0xfd1 [virtio_net] [ 46.166767] ? receive_buf+0x2e30/0x2e30 [virtio_net] [ 46.166796] ? sched_clock_cpu+0x18/0x2b0 [ 46.166809] ? print_irqtrace_events+0x280/0x280 [ 46.166817] ? print_irqtrace_events+0x280/0x280 [ 46.166830] ? rcu_process_callbacks+0xc5e/0x12d0 [ 46.166838] ? kvm_clock_read+0x1f/0x30 [ 46.166857] ? mark_held_locks+0xd5/0x170 [ 46.166867] ? net_rx_action+0x2aa/0x10e0 [ 46.166882] net_rx_action+0x4bc/0x10e0 [ 46.166906] ? napi_complete_done+0x480/0x480 [ 46.166925] ? print_irqtrace_events+0x280/0x280 [ 46.166935] ? sched_clock+0x5/0x10 [ 46.166952]...
2018 Aug 05
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
...d9c/0xfd1 [virtio_net] [ 46.166767] ? receive_buf+0x2e30/0x2e30 [virtio_net] [ 46.166796] ? sched_clock_cpu+0x18/0x2b0 [ 46.166809] ? print_irqtrace_events+0x280/0x280 [ 46.166817] ? print_irqtrace_events+0x280/0x280 [ 46.166830] ? rcu_process_callbacks+0xc5e/0x12d0 [ 46.166838] ? kvm_clock_read+0x1f/0x30 [ 46.166857] ? mark_held_locks+0xd5/0x170 [ 46.166867] ? net_rx_action+0x2aa/0x10e0 [ 46.166882] net_rx_action+0x4bc/0x10e0 [ 46.166906] ? napi_complete_done+0x480/0x480 [ 46.166925] ? print_irqtrace_events+0x280/0x280 [ 46.166935] ? sched_clock+0x5/0x10 [ 46.166952]...
2018 Aug 05
0
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
...? 46.166767]? ? receive_buf+0x2e30/0x2e30 [virtio_net] > [?? 46.166796]? ? sched_clock_cpu+0x18/0x2b0 > [?? 46.166809]? ? print_irqtrace_events+0x280/0x280 > [?? 46.166817]? ? print_irqtrace_events+0x280/0x280 > [?? 46.166830]? ? rcu_process_callbacks+0xc5e/0x12d0 > [?? 46.166838]? ? kvm_clock_read+0x1f/0x30 > [?? 46.166857]? ? mark_held_locks+0xd5/0x170 > [?? 46.166867]? ? net_rx_action+0x2aa/0x10e0 > [?? 46.166882]? net_rx_action+0x4bc/0x10e0 > [?? 46.166906]? ? napi_complete_done+0x480/0x480 > [?? 46.166925]? ? print_irqtrace_events+0x280/0x280 > [?? 46.166935]? ? sched_c...
2018 Jul 25
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
On Mon, Jul 23, 2018 at 11:36:03PM +0900, Toshiaki Makita wrote: > From: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp> > > Add some ethtool stat items useful for performance analysis. > > Signed-off-by: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp> Series: Acked-by: Michael S. Tsirkin <mst at redhat.com> Patch 1 seems appropriate for stable, even
2018 Jul 25
2
[PATCH net-next 0/6] virtio_net: Add ethtool stat items
On Mon, Jul 23, 2018 at 11:36:03PM +0900, Toshiaki Makita wrote: > From: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp> > > Add some ethtool stat items useful for performance analysis. > > Signed-off-by: Toshiaki Makita <makita.toshiaki at lab.ntt.co.jp> Series: Acked-by: Michael S. Tsirkin <mst at redhat.com> Patch 1 seems appropriate for stable, even
2008 May 08
4
[PATCH 0/4] paravirt clock series.
Respin of the paravirt clock patch series. On the host side the kvm paravirt clock is made compatible with the xen clock. On the guest side some xen code has been factored out into a separate source file shared by both kvm and xen clock implementations. This time it should work ok for kvm smp guests ;) cheers, Gerd
2008 May 08
4
[PATCH 0/4] paravirt clock series.
Respin of the paravirt clock patch series. On the host side the kvm paravirt clock is made compatible with the xen clock. On the guest side some xen code has been factored out into a separate source file shared by both kvm and xen clock implementations. This time it should work ok for kvm smp guests ;) cheers, Gerd
2008 May 16
5
[PATCH 0/4] paravirt clock source patches, #3
paravirt clock source patches, next round, with a bunch of changes in the host code according to Avi's review comments and some minor code tweaks. cheers, Gerd
2008 May 16
5
[PATCH 0/4] paravirt clock source patches, #3
paravirt clock source patches, next round, with a bunch of changes in the host code according to Avi's review comments and some minor code tweaks. cheers, Gerd
2008 Jun 03
6
[PATCH 0/5] paravirt clock source patches, #5
paravirt clock source patches, next round. There is now a pvclock-abi.h file with the structs and some longish comments in it and everybody is switched over to use the stuff in there. Some minor tweaks after super-fast review by Jeremy. The queue is on top of the kvm git tree. The first two patches should have no kvm dependencies and should apply to linus tree just fine. cheers, Gerd
2008 Jun 03
6
[PATCH 0/5] paravirt clock source patches, #5
paravirt clock source patches, next round. There is now a pvclock-abi.h file with the structs and some longish comments in it and everybody is switched over to use the stuff in there. Some minor tweaks after super-fast review by Jeremy. The queue is on top of the kvm git tree. The first two patches should have no kvm dependencies and should apply to linus tree just fine. cheers, Gerd
2008 Jun 03
10
[PATCH 0/5] paravirt clock source patches, #4
paravirt clock source patches, next round. There is now a pvclock-abi.h file with the structs and some longish comments in it and everybody is switched over to use the stuff in there. cheers, Gerd
2008 Jun 03
10
[PATCH 0/5] paravirt clock source patches, #4
paravirt clock source patches, next round. There is now a pvclock-abi.h file with the structs and some longish comments in it and everybody is switched over to use the stuff in there. cheers, Gerd
2015 Jan 07
1
[PATCH v8 34/50] vhost/net: virtio 1.0 byte swap
...fff81451f14>] ? move_addr_to_kernel+0x64/0x70 > <4> [<ffffffff814538b6>] __sys_sendmsg+0x406/0x420 > <4> [<ffffffff8104a98c>] ? __do_page_fault+0x1ec/0x480 > <4> [<ffffffff814523d9>] ? sys_sendto+0x139/0x190 > <4> [<ffffffff8103ea6c>] ? kvm_clock_read+0x1c/0x20 > <4> [<ffffffff81453ad9>] sys_sendmsg+0x49/0x90 > <4> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b > <4>Code: 83 e0 00 00 00 00 10 00 00 48 03 93 d0 00 00 00 66 83 42 04 01 8b 93 cc 00 00 00 48 8b b3 d0 00 00 00 80 4c 16 10 20 44 2b 68 0c &lt...
2015 Jan 07
1
[PATCH v8 34/50] vhost/net: virtio 1.0 byte swap
...fff81451f14>] ? move_addr_to_kernel+0x64/0x70 > <4> [<ffffffff814538b6>] __sys_sendmsg+0x406/0x420 > <4> [<ffffffff8104a98c>] ? __do_page_fault+0x1ec/0x480 > <4> [<ffffffff814523d9>] ? sys_sendto+0x139/0x190 > <4> [<ffffffff8103ea6c>] ? kvm_clock_read+0x1c/0x20 > <4> [<ffffffff81453ad9>] sys_sendmsg+0x49/0x90 > <4> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b > <4>Code: 83 e0 00 00 00 00 10 00 00 48 03 93 d0 00 00 00 66 83 42 04 01 8b 93 cc 00 00 00 48 8b b3 d0 00 00 00 80 4c 16 10 20 44 2b 68 0c &lt...
2014 Dec 01
2
[PATCH v8 34/50] vhost/net: virtio 1.0 byte swap
I had to add an explicit tag to suppress compiler warning: gcc isn't smart enough to notice that len is always initialized since function is called with size > 0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/vhost/net.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff
2014 Dec 01
2
[PATCH v8 34/50] vhost/net: virtio 1.0 byte swap
I had to add an explicit tag to suppress compiler warning: gcc isn't smart enough to notice that len is always initialized since function is called with size > 0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> Reviewed-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- drivers/vhost/net.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff
2008 Apr 30
1
[PATCH] make setup_secondary_clock definition dependent on local apic
...setup_secondary_APIC_clock(); } +#endif /* * After the clock is registered, the host will keep writing to the @@ -177,7 +179,9 @@ void __init kvmclock_init(void) pv_time_ops.get_wallclock = kvm_get_wallclock; pv_time_ops.set_wallclock = kvm_set_wallclock; pv_time_ops.sched_clock = kvm_clock_read; +#ifdef CONFIG_X86_LOCAL_APIC pv_apic_ops.setup_secondary_clock = kvm_setup_secondary_clock; +#endif machine_ops.shutdown = kvm_shutdown; #ifdef CONFIG_KEXEC machine_ops.crash_shutdown = kvm_crash_shutdown; -- 1.5.0.6
2018 Aug 10
0
[PATCH 04/10] x86/paravirt: use a single ops structure
...c b/arch/x86/kernel/kvmclock.c index 3b8e7c13c614..10a6071b209a 100644 --- a/arch/x86/kernel/kvmclock.c +++ b/arch/x86/kernel/kvmclock.c @@ -104,13 +104,13 @@ static u64 kvm_sched_clock_read(void) static inline void kvm_sched_clock_init(bool stable) { if (!stable) { - pv_time_ops.sched_clock = kvm_clock_read; + pv_ops.pv_time_ops.sched_clock = kvm_clock_read; clear_sched_clock_stable(); return; } kvm_sched_clock_offset = kvm_clock_read(); - pv_time_ops.sched_clock = kvm_sched_clock_read; + pv_ops.pv_time_ops.sched_clock = kvm_sched_clock_read; printk(KERN_INFO "kvm-clock: using sc...
2015 Jan 06
0
[PATCH v8 34/50] vhost/net: virtio 1.0 byte swap
...<4> [<ffffffff81451f14>] ? move_addr_to_kernel+0x64/0x70 <4> [<ffffffff814538b6>] __sys_sendmsg+0x406/0x420 <4> [<ffffffff8104a98c>] ? __do_page_fault+0x1ec/0x480 <4> [<ffffffff814523d9>] ? sys_sendto+0x139/0x190 <4> [<ffffffff8103ea6c>] ? kvm_clock_read+0x1c/0x20 <4> [<ffffffff81453ad9>] sys_sendmsg+0x49/0x90 <4> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b <4>Code: 83 e0 00 00 00 00 10 00 00 48 03 93 d0 00 00 00 66 83 42 04 01 8b 93 cc 00 00 00 48 8b b3 d0 00 00 00 80 4c 16 10 20 44 2b 68 0c <4d> 8b 76 1...