From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Subject: Re: inaccurate dirty_count from XEN_DOMCTL_SHADOW_OP
Date: Thu, 30 Mar 2017 12:40:34 +0100 [thread overview]
Message-ID: <2b4fb138-2d53-1b35-978d-86e9884d38c9@citrix.com> (raw)
In-Reply-To: <20170322105909.GA24055@aepfle.de>
On 22/03/17 10:59, Olaf Hering wrote:
> On Wed, Mar 22, Olaf Hering wrote:
>
>> Did the xc_shadow_control API change at some point?
> ... staging-4.5 works, while staging-4.6 does not.
Can you describe in a little more detail what you are testing?
I have tried reproducing your scenario, and I don't observe any dropoff
with 4.7 or staging.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-30 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:50 inaccurate dirty_count from XEN_DOMCTL_SHADOW_OP Olaf Hering
2017-03-22 10:46 ` Olaf Hering
2017-03-22 10:53 ` Andrew Cooper
2017-03-22 10:59 ` Olaf Hering
2017-03-30 11:40 ` Andrew Cooper [this message]
2017-03-30 11:50 ` Olaf Hering
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=2b4fb138-2d53-1b35-978d-86e9884d38c9@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=olaf@aepfle.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).