kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, mtosatti@redhat.com, pl@dlh.net
Subject: Re: [RFC PATCH 1/2] Hyper-H reference counter
Date: Mon, 20 May 2013 20:25:11 +1000	[thread overview]
Message-ID: <1369045511.31632.22.camel@localhost> (raw)
In-Reply-To: <20130520092519.GA11606@redhat.com>

On Mon, 2013-05-20 at 12:25 +0300, Gleb Natapov wrote:
> On Mon, May 20, 2013 at 10:56:22AM +0200, Paolo Bonzini wrote:
> > In any case, this patch needs more comments and a better commit message.
> >  Microsoft docs are decent, but there are several non-obvious points in
> > how the patches were done, and they need to be documented.
> I wish you were right about Microsoft docs :) So in Hyper-V spec they
> say:
> 
>   Special value of 0xFFFFFFFF is used to indicate that this facility is no
>   longer a reliable source of reference time and the virtual machine must
>   fall back to a different source (for example, the virtual PM timer).
> 
> May be they really mean "virtual PM timer" here and reference counter is
> not considered as a fall back source, but this is not what we want.

As far as I know, you cannot fall back from iTSC to PMTimer or HPET,
but you can fallback to reference counters.

> 
> On the other hand in API specification [1] they have:
> 
> #define HV_REFERENCE_TSC_SEQUENCE_INVALID   (0x00000000)
> 
> which is not even documented in hyper-v spec. Actually 0 is specified as
> valid value there. Go figure.
> 
> [1] http://msdn.microsoft.com/en-us/library/windows/hardware/ff540244%28v=vs.85%29.aspx
> 
> --
> 			Gleb.



  parent reply	other threads:[~2013-05-20 10:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 11:45 [RFC PATCH 0/2] Hyper-V timers Vadim Rozenfeld
2013-05-13 11:45 ` [RFC PATCH 1/2] Hyper-H reference counter Vadim Rozenfeld
2013-05-13 23:30   ` Eric Northup
2013-05-14  9:46     ` Vadim Rozenfeld
2013-05-16  8:18       ` Gleb Natapov
2013-05-16  8:53         ` Vadim Rozenfeld
2013-05-14 14:14   ` Peter Lieven
2013-05-15 10:24     ` Vadim Rozenfeld
2013-05-16  8:10     ` Gleb Natapov
2013-05-16  8:34   ` Gleb Natapov
2013-05-16  9:13     ` Vadim Rozenfeld
2013-05-16  9:21       ` Gleb Natapov
2013-05-16  9:28         ` Vadim Rozenfeld
2013-05-16 13:37           ` Paolo Bonzini
2013-05-16 14:22             ` Vadim Rozenfeld
2013-05-16 14:48               ` Paolo Bonzini
2013-05-16 13:44           ` Paolo Bonzini
2013-05-16 14:26             ` Vadim Rozenfeld
2013-05-16 14:45               ` Paolo Bonzini
2013-05-19  6:37                 ` Vadim Rozenfeld
2013-05-20  8:05                   ` Paolo Bonzini
2013-05-20  8:36                     ` Gleb Natapov
2013-05-20  8:42                       ` Paolo Bonzini
2013-05-20  8:49                         ` Gleb Natapov
2013-05-20  8:56                           ` Paolo Bonzini
2013-05-20  9:13                             ` Gleb Natapov
2013-05-20  9:25                             ` Gleb Natapov
2013-05-20  9:32                               ` Paolo Bonzini
2013-05-20  9:41                                 ` Gleb Natapov
2013-05-20 10:06                                   ` Peter Lieven
2013-05-20 10:25                               ` Vadim Rozenfeld [this message]
2013-05-20 10:27                                 ` Gleb Natapov
2013-05-20 10:44                                   ` Vadim Rozenfeld
2013-05-20 10:21                             ` Vadim Rozenfeld
2013-05-20  9:12                     ` Vadim Rozenfeld
2013-05-16 14:40   ` Paolo Bonzini
2013-05-13 11:45 ` [RFC PATCH 2/2] Hyper-V iTSC handler Vadim Rozenfeld
2013-05-16  8:33   ` Gleb Natapov
2013-05-16  8:58     ` Vadim Rozenfeld
2013-05-16  8:02 ` [RFC PATCH 0/2] Hyper-V timers Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1369045511.31632.22.camel@localhost \
    --to=vrozenfe@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@dlh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).