All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Yuehai Xu <yuehaixu@gmail.com>
Cc: xen-devel@lists.xensource.com, yhxu@wayne.edu
Subject: Re: Question about the ability of credit scheduler to handle I/O and CPU intensive VMs
Date: Fri, 8 Oct 2010 11:11:42 +0100	[thread overview]
Message-ID: <AANLkTimC=pPNWv=1n6CtuSYRPmN9jcE51ebafDCjMO+c@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=_EEw=uixwoxk5eo3+Tp12iemNA0Y7WHu-FpeE@mail.gmail.com>

OK, scratch that... the #defines were renamed, but the actual values
remained the same; so the binaries are compatible.

The results show up in the xenalyze output as "mmio_assist" (for MMIO)
and "io [read|write]" (for PIO).

 -George

On Fri, Oct 8, 2010 at 11:03 AM, George Dunlap
<George.Dunlap@eu.citrix.com> wrote:
> 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.  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
>

  reply	other threads:[~2010-10-08 10:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 21:37 Question about the ability of credit scheduler to handle I/O and CPU intensive VMs Yuehai Xu
2010-09-13 23:29 ` Jeremy Fitzhardinge
2010-09-14  1:38   ` Yuehai Xu
     [not found] ` <AANLkTin9E1m_jFcj4Ak7nB9OxcQynrznpQ_nNPi_U7hN@mail.gmail.com>
2010-09-14 14:58   ` Yuehai Xu
2010-09-30 12:28   ` Yuehai Xu
2010-09-30 13:27     ` George Dunlap
2010-10-05  2:52       ` Yuehai Xu
2010-10-05 14:16         ` George Dunlap
2010-10-05 14:56           ` Yuehai Xu
2010-10-05 15:02             ` George Dunlap
2010-10-07 22:18               ` Yuehai Xu
2010-10-08  0:25                 ` Yuehai Xu
2010-10-08  9:57                   ` George Dunlap
2010-10-08 10:03                     ` George Dunlap
2010-10-08 10:11                       ` George Dunlap [this message]
2010-10-10  4:08                     ` Yuehai Xu
2010-10-10  8:30                       ` cendhu
2010-10-11 11:05                       ` George Dunlap
2010-10-12 12:42                         ` Yuehai Xu
2010-10-18 10:25                           ` George Dunlap
2010-10-05  4:30       ` question about lineat pagetable and mfn_x strongerwill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTimC=pPNWv=1n6CtuSYRPmN9jcE51ebafDCjMO+c@mail.gmail.com' \
    --to=george.dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yhxu@wayne.edu \
    --cc=yuehaixu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.