| From: |
| Glauber de Oliveira Costa <gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> |
| To: |
| linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org |
| Subject: |
| [PATCH 0/3] Kvm clocksource, new spin |
| Date: |
| Thu, 8 Nov 2007 20:39:20 -0200 |
| Message-ID: |
| <11945615632624-git-send-email-gcosta@redhat.com> |
| Cc: |
| kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
jeremy-TSDbQ3PG+2Y@public.gmane.org, avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org |
| Archive-link: |
| Article,
Thread
|
Hi folks,
Here's a new spin of the clocksource implementation.
In this new version:
* followed avi's suggestion of:
- letting the cpu itself register its memory area.
- using a gfn instead of a phys addr as a parameter, to be sure we can
cover the whole memory area
- write guest time at exits.
Also, I 'm not using an anonymous struct in the kvm_hv_clock union, so the
vcpu struct can grab just what it needs, and not the whole padding the guest needs
This is it.
Have fun
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/