From: Frediano Ziglio Subject: [RFC PATCH] Coverage support Date: Fri, 1 Feb 2013 14:48:19 +0000 Message-ID: <1359730103-9474-1-git-send-email-frediano.ziglio@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: frediano.ziglio@citrix.com, Konrad Rzeszutek Wilk , "Keir (Xen.org)" , Ian Campbell Cc: George Dunlap , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Updated set of patches for coverage. Changes: - implemented way of getting information - use only 2 parameter in hypercall (still not sure it's better to use sysctl) - use "coverage" for configuration option as suggested by Ian Campbell - split header in include/public/gcov.h and include/xen/gcov.h to allow tools to include public header - use weak to avoid defining compat_coverage_op I manage to write 2 tools, one that call the new hypercall and dump the blob in a file, one that split this file into required .gcda files. Both very hack ones and dirty but works and prove the hypervisor code is fine. Should I just send them anyway? The forth patch allow to consume just 0 bytes if coverage is disabled.