public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: The SMP RHEL 5.1 PAE guest can't boot up issue
Date: Tue, 04 Mar 2008 13:38:16 +0200	[thread overview]
Message-ID: <47CD34A8.6080107@qumranet.com> (raw)
In-Reply-To: <47C3E9B1.7040406@qumranet.com>

Avi Kivity wrote:
> Dong, Eddie wrote:
>>>> I don't know if the patch was still needed now, since it was posted
>>>> long ago(I don't know which issue it solved). I'd like to post a
>>>> revert patch if necessary.
>>>>       
>>> I believe the patch is still necessary, since we still need to
>>> guarantee that a vcpu's tsc is monotonous.  I think there are three
>>> issues to be addressed:
>>>
>>> 1. The majority of intel machines don't need the offset adjustment
>>> since they already have a constant rate tsc that is synchronized on
>>> all cpus. I think this is indicated by X86_FEATURE_CONSTANT_TSC
>>> (though I'm not 100% certain if it means that the rate is the same
>>> for all cpus, Thomas can you clarify?)
>>>     
>>
>> So why not make the TSC_OFFSET adjustment conditional?
>>   
>
> Yes, that's what I meant.  We just need to be sure that this is what 
> X86_FEATURE_CONSTANT_TSC means.

I changed tsc offset adjustment to only allow forward adjustment.  Since 
hosts with synced tsc never require positive adjustment, they should now 
have better quality tsc.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-03-04 11:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  8:57 The SMP RHEL 5.1 PAE guest can't boot up issue Yang, Sheng
2008-02-22 16:16 ` Avi Kivity
2008-02-22 17:17   ` Marcelo Tosatti
2008-02-22 18:45     ` Avi Kivity
2008-02-22 20:12       ` Marcelo Tosatti
2008-02-23 15:24   ` Farkas Levente
2008-02-24  8:51     ` Avi Kivity
2008-02-25  4:09       ` Yang, Sheng
2008-02-25 18:03       ` Farkas Levente
2008-02-25 18:12         ` Avi Kivity
2008-02-25 18:24           ` Farkas Levente
2008-02-25 23:46   ` Dong, Eddie
2008-02-26 10:28     ` Avi Kivity
2008-02-29  4:35       ` Zhao Forrest
2008-03-04 11:38       ` Avi Kivity [this message]
2008-02-29  8:26   ` Zhao Forrest

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=47CD34A8.6080107@qumranet.com \
    --to=avi@qumranet.com \
    --cc=eddie.dong@intel.com \
    --cc=kvm-devel@lists.sourceforge.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