From: Frediano Ziglio <frediano.ziglio@citrix.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Frediano Ziglio <frediano.ziglio@citrix.com>, xen-devel@lists.xen.org
Subject: [PATCH v10 5/5] gcov: Add documentation for coverage
Date: Thu, 21 Feb 2013 16:13:45 +0000 [thread overview]
Message-ID: <1361463225-21750-6-git-send-email-frediano.ziglio@citrix.com> (raw)
In-Reply-To: <1361463225-21750-1-git-send-email-frediano.ziglio@citrix.com>
Signed-off-by: Frediano Ziglio <frediano.ziglio@citrix.com>
---
docs/misc/coverage.markdown | 39 +++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 docs/misc/coverage.markdown
diff --git a/docs/misc/coverage.markdown b/docs/misc/coverage.markdown
new file mode 100644
index 0000000..74af665
--- /dev/null
+++ b/docs/misc/coverage.markdown
@@ -0,0 +1,39 @@
+# Coverage support for Xen
+
+Coverare support allow you to get coverage information from Xen execution.
+You can see how many times a line is executed.
+
+The compiler have specific options that enable the collection of these
+information. Every basic block in the code will be instructed by the compiler
+to compute these statistics. It should not be used in production as it slow
+down your hypervisor.
+
+## Enable coverage
+
+Test coverage support can be turned on compiling Xen with coverage option set
+to y.
+
+Something like:
+ cd xen
+ make coverage=y
+
+(or change your `Config.mk` file).
+
+## Extract coverage data
+
+The way GCC and other tools deal with coverage information is to use some files
+created during build phase (.gcno) and some files produced by executing the
+*program* (.gcda). The program in this case is Xen but Xen cannot write files
+so the way you can use coverage from Xen is extract coverage data from Xen and
+then split these information into files.
+
+To extract data you use a simple utility called `xencov`. Mainly `xencore`
+allow you to do 3 operations:
+
+* `xencov read` extract data
+* `xencov reset` reset all coverage counters
+* `xencov read-reset` extract data and reset counters at the same time.
+
+Another utility (**TODO**) is used to split extracted data file into files
+needed by userspace tools.
+
--
1.7.9.5
next prev parent reply other threads:[~2013-02-21 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 16:13 [PATCH v10 0/5] gcov: Coverage support Frediano Ziglio
2013-02-21 16:13 ` [PATCH v10 1/5] gcov: Call constructors during initialization Frediano Ziglio
2013-02-22 8:50 ` Ian Campbell
2013-02-22 9:40 ` Frediano Ziglio
2013-02-22 9:45 ` Ian Campbell
2013-02-21 16:13 ` [PATCH v10 2/5] gcov: Adding support for coverage information Frediano Ziglio
2013-02-21 16:13 ` [PATCH v10 3/5] gcov: Implement code to read coverage informations Frediano Ziglio
2013-02-21 16:13 ` [PATCH v10 4/5] gcov: Add small utility to deal with test coverage information from Xen Frediano Ziglio
2013-02-21 16:13 ` Frediano Ziglio [this message]
2013-02-22 14:20 ` [PATCH v10 0/5] gcov: Coverage support George Dunlap
2013-02-22 14:35 ` Ian Campbell
2013-02-22 14:35 ` Frediano Ziglio
2013-02-22 14:39 ` Jan Beulich
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=1361463225-21750-6-git-send-email-frediano.ziglio@citrix.com \
--to=frediano.ziglio@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad@kernel.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.