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

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

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@xxxxxxxxxxxxx> wrote:
> 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