From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: Re: inaccurate dirty_count from XEN_DOMCTL_SHADOW_OP
Date: Wed, 22 Mar 2017 11:46:29 +0100 [thread overview]
Message-ID: <20170322104628.GA21170@aepfle.de> (raw)
In-Reply-To: <20170321095037.GA22242@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 304 bytes --]
On Tue, Mar 21, Olaf Hering wrote:
> I wonder if the usage of xc_shadow_control is correct. The testing was
> done with a xen-4.4 based dom0, I will verify with staging once I find
> the time.
It does work with xen-4.4, but fails with staging.
Did the xc_shadow_control API change at some point?
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-22 10:46 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 [this message]
2017-03-22 10:53 ` Andrew Cooper
2017-03-22 10:59 ` Olaf Hering
2017-03-30 11:40 ` Andrew Cooper
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=20170322104628.GA21170@aepfle.de \
--to=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).