From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <ak@linux.intel.com>
Subject: Re: qemu polling KVM_IRQ_LINE_STATUS when stopped
Date: Fri, 20 Oct 2017 07:09:17 -0700
Message-ID: <20171020140917.GH5109@tassilo.jf.intel.com>
References: <87a80pihlz.fsf@linux.intel.com>
 <1ffc9cf7-a81c-6eeb-4823-c6e0ef53d3af@redhat.com>
 <20171018174946.GU5109@tassilo.jf.intel.com>
 <3d37ef15-932a-1492-3068-9ef0b8cd5794@redhat.com>
 <20171020003449.GG5109@tassilo.jf.intel.com>
 <22d62b58-725b-9065-1f6d-081972ca32c3@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mga09.intel.com ([134.134.136.24]:58406 "EHLO mga09.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752145AbdJTOKX (ORCPT <rfc822;kvm@vger.kernel.org>);
        Fri, 20 Oct 2017 10:10:23 -0400
Content-Disposition: inline
In-Reply-To: <22d62b58-725b-9065-1f6d-081972ca32c3@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> Unfortunately that's not possible in general.  Windows uses the periodic
> timer to track wall time (!), so if you do that your clock is going to
> be late when you resume the guest.

But when the guest cannot execute instructions 
it cannot see whatever the handler does.

So the handler could always catch up after stopping for longer,
without making any difference.

> 
> But yeah, we might have to figure out a way to do that for non-Windows
> guests.  But why is the RTC periodic timer on at all in your setup?

Sorry this one was actually a Windows guest.

I'll check the Linux guests too.

-Andi