From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: Tej <bewith.tej@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH-0/2] Hypervisor profiling using GCOV (64bit Hypervisor)
Date: Fri, 27 Feb 2009 19:02:22 +0000 [thread overview]
Message-ID: <49A838BE.40801@eu.citrix.com> (raw)
In-Reply-To: <f1c9d250902260709s35714c06k990b07a3221afc66@mail.gmail.com>
Hi,
Tej wrote:
> Sending Patches for the 64 bit Hypervisor, We have tested patches on
> AMD-64 (Athlon(tm) 64 X2 Dual Core Processor 4600+) machine with
> gcc-4.2 & gcc-3.4. Please refer the previous GCOV RFC in same mail for
> more info on Hypervisor profiling.
> We have added support to 32bit and 64bit Kernel.
>
> In addition to patches for hypervisor profiling, we did a little work
> on *lcov* to work with hypervisor.
> README could be useful, for naive lcov user. locv-diff.patch show our
> change in lcov scripts.
>
> any comments, feedback and suggestion are more than welcome
While I still need to test the patch (building 3.3 right now) and to
understand gcov internals, I think that a few comments can be done,
mostly aestethicals.
- xen coding style: Using four-spaces tabs is generally the tradition.
Also I do prefer to have brackets that start code blocks on a new line
aligned to the previous line, but that's not followed everywhere in the
code.
- Makefiles: while the num=$*.c is still a mystery to me, my question
is: do you really need to make links with different names to files
compiled multiple times? If so, it would be useful to remove them on
'make clean'.
Also, it would be useful to make this feature enabled with a
compile-time option.
More comments to follow as I test it.
Thanks,
Gianluca
next prev parent reply other threads:[~2009-02-27 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 15:09 [PATCH-0/2] Hypervisor profiling using GCOV (64bit Hypervisor) Tej
2009-02-27 19:02 ` Gianluca Guida [this message]
2009-02-28 7:23 ` Tej
2009-03-02 16:06 ` Tej
[not found] ` <f1c9d250903252359p13f2fe47r84674d183fe8629f@mail.gmail.com>
2009-03-26 10:57 ` Gianluca Guida
2009-03-26 15:11 ` Tej
2009-04-06 15:04 ` Tej
2009-04-29 14:56 ` 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=49A838BE.40801@eu.citrix.com \
--to=gianluca.guida@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=bewith.tej@gmail.com \
--cc=xen-devel@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 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.