From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: Question about the ability of credit scheduler to
	handle I/O and CPU intensive VMs
Date: Fri, 8 Oct 2010 11:03:51 +0100
Message-ID: <AANLkTi=_EEw=uixwoxk5eo3+Tp12iemNA0Y7WHu-FpeE@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>
	<AANLkTinG-y8gOW1jVpvKgJU2fBiiDkgj5r=FAOv=0J8q@mail.gmail.com>
	<AANLkTinc+Dar85ZU+_dYb=7AsdWgWpc3N_K_WFSTVbO6@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AANLkTinc+Dar85ZU+_dYb=7AsdWgWpc3N_K_WFSTVbO6@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: Yuehai Xu <yuehaixu@gmail.com>
Cc: xen-devel@lists.xensource.com, yhxu@wayne.edu
List-Id: xen-devel@lists.xenproject.org

On Fri, Oct 8, 2010 at 10:57 AM, George Dunlap
<George.Dunlap@eu.citrix.com> wrote:
> Regarding tracing IO_READs: The code that did IO was refactored some
> time back; I remember trying to figure out how to cleanly do the
> tracing, but finding it difficult. =A0I can't remember now, though, what
> the issue was. =A0Let me take a look again.

Ah, that's right -- IO_READ was replaced with
IO{PORT,MEM}_{READ_WRITE}.  It's traced in
xen/arch/x86/hvm/emulate.c:hvmtrace_io_assist().  xenalyze simply
hasn't been updated to understand those traces yet.

 -George