From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yuehai Xu <yuehaixu@gmail.com>
Subject: Re: Question about the ability of credit scheduler to
	handle I/O and CPU intensive VMs
Date: Thu, 7 Oct 2010 20:25:12 -0400
Message-ID: <AANLkTinG-y8gOW1jVpvKgJU2fBiiDkgj5r=FAOv=0J8q@mail.gmail.com>
References: <AANLkTi=Ro24zg-yDPk1+=c0XsZSe2kNn8Gk07Bu4x0WN@mail.gmail.com>
	<AANLkTin9E1m_jFcj4Ak7nB9OxcQynrznpQ_nNPi_U7hN@mail.gmail.com>
	<AANLkTikBWZdpOviSEQSNi_pf66A+zYW8FyQVjiCX8ojm@mail.gmail.com>
	<AANLkTi=Oa0_=vXrr63eALBU2sQa3aLV0NiQHt8hPPvcw@mail.gmail.com>
	<AANLkTimYTbf5meNptCtuiKWfQGd_qSNCkbCNabfREc_0@mail.gmail.com>
	<AANLkTintdF5h0-YD6FxjX0dapfbQYdAcK2P-=wHXnBiC@mail.gmail.com>
	<AANLkTinCbnzLLtNpdQe0x387UeDcy3SzrmffZw1oQAJo@mail.gmail.com>
	<AANLkTi=r2MzCwwNbNDopBkoCWvQSc=jkeWUy8hxKYD3_@mail.gmail.com>
	<AANLkTik+tZTr8RQrbCwTFYZjbgW6tDq=LTcoBC2xsQhw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AANLkTik+tZTr8RQrbCwTFYZjbgW6tDq=LTcoBC2xsQhw@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, yhxu@wayne.edu
List-Id: xen-devel@lists.xenproject.org

> I originally considered that when a Dom has an I/O event, its VCPU
> would be waken up, in another word, csched_vcpu_wake(struct vcpu *vc)
> should be invoked. However, I find I am definitely wrong. As long as
> there is a CPU intensive program running in a Dom, this Dom should
> never be in a state of "sleep"? In another word, it should never be
> waken up?
>

The trace result from xenalyze confirms that when a VM has a running
CPU intensive program, it never needs to be waken up. So, my question
is, how can I schedule a VM that has I/O event immediately even this
VM is CPU intensive? I think it is impossible to implement it in the
function csched_vcpu_wake.

Also, is it possible to trace the I/O procedure by xenalyze? I notice
even the macro TRC_HVM_IO_READ is defined, I don't find it is used in
anywhere.

Thanks,
Yuehai