 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Question about the ability of credit scheduler to handle
| To: | Yuehai Xu <yuehaixu@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs |
| 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 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=HYOAsGqbkoSNoctfBYCUJlUdtnwyLE05fcsErl5/5/w=; b=SxZdqyRAO8+SMVqaOs3fHOL1frc0poYknsMyikrUVR3Vdd+Ge9lVnU0ncTd3XLE4g/ NVQYNrI+mA1uxZG1XeKnd/A9zQS0u/Z8eR+96Kd+UqzvCKTqQV6s/o62+BJj6xR9S/x/ Op3T6uPKnFrWNki+c+6R2Ks3R+QftCqXBlpew= |
| 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= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <AANLkTinc+Dar85ZU+_dYb=7AsdWgWpc3N_K_WFSTVbO6@xxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <AANLkTi=Ro24zg-yDPk1+=c0XsZSe2kNn8Gk07Bu4x0WN@xxxxxxxxxxxxxx> <AANLkTin9E1m_jFcj4Ak7nB9OxcQynrznpQ_nNPi_U7hN@xxxxxxxxxxxxxx> <AANLkTikBWZdpOviSEQSNi_pf66A+zYW8FyQVjiCX8ojm@xxxxxxxxxxxxxx> <AANLkTi=Oa0_=vXrr63eALBU2sQa3aLV0NiQHt8hPPvcw@xxxxxxxxxxxxxx> <AANLkTimYTbf5meNptCtuiKWfQGd_qSNCkbCNabfREc_0@xxxxxxxxxxxxxx> <AANLkTintdF5h0-YD6FxjX0dapfbQYdAcK2P-=wHXnBiC@xxxxxxxxxxxxxx> <AANLkTinCbnzLLtNpdQe0x387UeDcy3SzrmffZw1oQAJo@xxxxxxxxxxxxxx> <AANLkTi=r2MzCwwNbNDopBkoCWvQSc=jkeWUy8hxKYD3_@xxxxxxxxxxxxxx> <AANLkTik+tZTr8RQrbCwTFYZjbgW6tDq=LTcoBC2xsQhw@xxxxxxxxxxxxxx> <AANLkTinG-y8gOW1jVpvKgJU2fBiiDkgj5r=FAOv=0J8q@xxxxxxxxxxxxxx> <AANLkTinc+Dar85ZU+_dYb=7AsdWgWpc3N_K_WFSTVbO6@xxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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
|
| Previous by Date: | Re: [Xen-devel] MSI badness in xen-unstable, Gianni Tedesco |
|---|---|
| Next by Date: | Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs, George Dunlap |
| Previous by Thread: | Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs, George Dunlap |
| Next by Thread: | Re: [Xen-devel] Question about the ability of credit scheduler to handle I/O and CPU intensive VMs, George Dunlap |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
