From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Norrgard Subject: [PATCH 0/3] Sync TSC for guest when vcpu has been migrated to another cpu Date: Fri, 02 Mar 2007 18:41:04 +0200 Message-ID: <45E853A0.3080207@refactor.fi> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org When a vcpu is migrated to another cpu, an unexpected difference in current and previous cpu TSC values can cause a guest to wait indefinitely. A known workaround has been to run kvm with taskset, locking it to a single cpu. This patch series modifies the guest TSC offset as needed to guarantee that the guest sees a monotonically increasing TSC, adds a statistic for vcpu_migrated and updates kvm_stat so the first column isn't truncated. [1/3] Sync guest viewable TSC when vcpu migrated [2/3] Add a vcpu_migrated statistic [3/3] Widen key column in kvm_stat -- Leonard ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV