From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] [RESEND] KVM:VMX: Add support for Pause-Loop Exiting
Date: Fri, 25 Sep 2009 22:43:39 +0200
Message-ID: <20090925204339.GA29634@8bytes.org>
References: <4ABA2AD7.6080008@intel.com> <4ABA2C22.7020000@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Zhai, Edwin" <edwin.zhai@intel.com>, Ingo Molnar <mingo@elte.hu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from 8bytes.org ([88.198.83.132]:34580 "EHLO 8bytes.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751974AbZIYUng (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 25 Sep 2009 16:43:36 -0400
Content-Disposition: inline
In-Reply-To: <4ABA2C22.7020000@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Sep 23, 2009 at 05:09:38PM +0300, Avi Kivity wrote:
>
> We haven't sorted out what is the correct thing to do here.  I think we  
> should go for a directed yield, but until we have it, you can use  
> hrtimers to sleep for 100 microseconds and hope the holding vcpu will  
> get scheduled.  Even if it doesn't, we're only wasting a few percent cpu  
> time instead of spinning.

How do you plan to find out to which vcpu thread the current thread
should yield?

	Joerg