o tune them up themselves.
So switch l3-cache off by default, and add a compat clause for the range
of machine types where it was on.
Signed-off-by: Denis Plotnikov <dplotni...@virtuozzo.com>
Reviewed-by: Roman Kagan <rka...@virtuozzo.com>
---
include/hw/i386/pc.h | 7 ++-
targe
of the bug is not revealed.
This patch fixes this problem by making sure it knows the correct
system_time_msr address every time it is needed.
Signed-off-by: Denis Plotnikov <dplotni...@virtuozzo.com>
---
hw/i386/kvm/clock.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/i386/kvm/clo
of the bug is not revealed.
This patch fixes this problem by making sure it knows the correct
system_time_msr address every time it is needed.
Signed-off-by: Denis Plotnikov <dplotni...@virtuozzo.com>
---
hw/i386/kvm/clock.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/i386/kvm/clo
it doesn't enter L1 and
processed it by itself.
Thus, L1 kvm doesn't know about that TPR access happening and doesn't
exit to qemu which in turn doesn't set system_time_msr address.
This patch fixes this by making sure it knows the correct address every
time it is needed.
Signed-off-by: Denis Plotnikov
On 24.05.2017 17:09, Denis V. Lunev wrote:
On 05/24/2017 05:07 PM, Denis Plotnikov wrote:
Do an update of system_time_msr address every time before reading
the value of tsc_timestamp from guest's kvmclock page.
It should be done in a forcible manner because there is a situation
when
501 - 505 of 505 matches
Mail list logo
