From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tej <bewith.tej@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xensource.com,
xen-users <xen-users@lists.xensource.com>,
parkash.tej@gmail.com
Subject: Re: [Xen-devel] Xen GCOV Patches for latest Xen Unbstable and linux 2.6.18.8 kernel(32/64bit)
Date: Mon, 10 May 2010 10:53:12 -0400 [thread overview]
Message-ID: <20100510145312.GE29517@phenom.dumpdata.com> (raw)
In-Reply-To: <o2jf1c9d251005071301jfd33f723gc49e4013ae4a3d47@mail.gmail.com>
On Sat, May 08, 2010 at 01:31:01AM +0530, Tej wrote:
> All,
>
> Here are the latest patches to expreiment with gcov profiler for xen
> hypervisor. I have tested current patches on Intel i686.
Nice..
> System Details:
> gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
> gcov (Ubuntu 4.3.3-5ubuntu4) 4.3.3
> Kernel 2.6.28-11-generic
Uhh? 2.6.28 or 2.6.18?
I hate to tell you this but development is happening in the pv-ops
kernel, not anymore in the XenLinux branches :-(
Any chance you can rebase those patches against the pv-ops kernel?
Looking briefly at the Linux patches, you need to remove those #ifdef
LINUX_VERSION_CODE, make the EXPORT_SYMBOL be EXPORT_SYMBOL_GPL, and
also run the patch through scripts/checkpatch.pl
> Distribution: Ubuntu jaunty 9.04
>
> There are some design issue which i would like to highlight here:
> 1. To create gcov proc dir user /proc/xen, we are explicitly exported
> xen_base symbol. I want to know your thoughts.
> 2. XEN_GCOV_PROC config is set as not selected. So someone has to be
> configured manually as M/Y
>
>
> Known Issues:
> File vmac.c throw some fault while using with lcov/gcov. This is due
> to some raw count copy between xen and kernel. I could not able to
> reproduce it many times, may be someone can try on 64 bit m/c.
> "My take on this is that zero length array element in gcov_info
> structure has to be copied separately between xen and kernel. How? I
> dont know."
>
> I am still debugging this issue.
>
> If you get fault and fail to proceed please apply the above patch in
> linux-wa-v1.patch in Linux 2.6.18.8 and recompile. This time vmac.gcda
> file wont appear in /proc/xen/gcov/crypto
>
>
> HOWTO Test using lcov
> 1. install lcov from repo
> # sudo apt-get install lcov
> 2. vi /etc/lcovrc
> Change line: lcov_gcov_dir = /proc/gcov to lcov_gcov_dir = /proc/xen/gcov
> 3. # cd /tmp; lcov -c -o kernel.info
> 4. # genhtml kernel.info
> 5, # firefox index.html
>
> lcov README and screenshot is attached.
22% coverege, eh? Is that just by booting the Dom0 kernel?
>
> HTH
>
> Note:
> For any other detail required please CC me to parkash.tej@gmail.com
> diff -r 86d6c6417cf9 drivers/xen/Kconfig
> --- a/drivers/xen/Kconfig Thu Feb 04 13:08:27 2010 +0000
> +++ b/drivers/xen/Kconfig Sun Feb 07 00:13:40 2010 +0530
> @@ -311,6 +311,13 @@
> help
> Xen hypervisor attributes will show up under /sys/hypervisor/.
>
> +config XEN_GCOV_PROC
> + tristate "Code covarage for hypervisor"
^^^^^ - coverage
next prev parent reply other threads:[~2010-05-10 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 20:01 Xen GCOV Patches for latest Xen Unbstable and linux 2.6.18.8 kernel(32/64bit) Tej
2010-05-10 14:53 ` Konrad Rzeszutek Wilk [this message]
2010-05-10 17:21 ` [Xen-devel] " Tej
2010-05-10 17:26 ` Tej
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=20100510145312.GE29517@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bewith.tej@gmail.com \
--cc=george.dunlap@eu.citrix.com \
--cc=parkash.tej@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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).