From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: sparvu@systemdatarecorder.org, xen-devel@lists.xen.org
Subject: Re: domains being migrated state message improvements
Date: Fri, 2 May 2014 14:40:15 +0100 [thread overview]
Message-ID: <5363A03F.3050109@citrix.com> (raw)
In-Reply-To: <1399037350.6043.9.camel@kazak.uk.xensource.com>
On 02/05/14 14:29, Ian Campbell wrote:
>
>> I would agree that it is a little confusing. '------' means runnable
>> but not running, in this case due to vcpu over subscription.
> Is that not "blocked"?
Blocked is any vcpu/domain pause count. For healthy domains, this is
usually a yielded timeslice, which is why idle domains are almost always
'-b----'.
>
> BTW, the "migration" referred to here is VCPU migration to another PCPU
> rather than domain migration. (It came up because that's another one of
> the VCPU pause flags alongside blocked et al)
I do not think vcpu motion around the system is actually relevant to the
problem described.
~Andrew
>
>> However, the information is stale by the time it is displayed. It is
>> not really appropriate to be consumed by anything other than an eyeball.
> Agreed. And even if someone disagrees I think it is up to those tools to
> accept whatever the output is, even if that includes "nonsensical"
> results.
>
> Ian.
>
next prev parent reply other threads:[~2014-05-02 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:16 domains being migrated state message improvements Stefan Parvu
2014-05-02 13:23 ` Ian Campbell
2014-05-02 13:31 ` Stefan Parvu
2014-05-02 14:15 ` Ian Campbell
2014-05-03 7:41 ` Stefan Parvu
2014-05-02 13:24 ` Andrew Cooper
2014-05-02 13:29 ` Ian Campbell
2014-05-02 13:40 ` Andrew Cooper [this message]
2014-05-02 14:15 ` Ian Campbell
2014-05-02 15:47 ` Stefan Parvu
2014-05-02 15:55 ` Andrew Cooper
2014-05-02 16:46 ` Stefan Parvu
2014-05-02 17:37 ` Andrew Cooper
2014-05-02 17:59 ` Stefan Parvu
2014-05-02 20:22 ` Ian Campbell
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=5363A03F.3050109@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=sparvu@systemdatarecorder.org \
--cc=xen-devel@lists.xen.org \
/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.