[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs


  • To: Yuehai Xu <yuehaixu@xxxxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Fri, 8 Oct 2010 11:03:51 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, yhxu@xxxxxxxxx
  • Delivery-date: Fri, 08 Oct 2010 03:08:14 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=EhzJGLSiZf2fckzPgi0Yoxoe4Uks+yI29nsxyecFAobOr/D/r9LoZ+Ec+kjkTLUPzQ dbu+W6HlMFfhKMYM/kt1SoQ1dg3Mbbba5wq8m6+ANCWicGwF2dB+RlzUT2FH9avkOwrx bq4BUr8u4hRSPmz7aS9GGJEmsYD+Nx2erx4/w=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Fri, Oct 8, 2010 at 10:57 AM, George Dunlap
<George.Dunlap@xxxxxxxxxxxxx> 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.  I can't remember now, though, what
> the issue was.  Let 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.