WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH-0/2] Hypervisor profiling using GCOV (64bit Hype

To: Gianluca Guida <Gianluca.Guida@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH-0/2] Hypervisor profiling using GCOV (64bit Hypervisor)
From: Tej <bewith.tej@xxxxxxxxx>
Date: Thu, 26 Mar 2009 20:41:47 +0530
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 26 Mar 2009 08:13:29 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=C+98jjwg3q5GvbYfoMaK8kLujPRV4EyiaW/52fx9Aco=; b=icJdWpWnxHxX9DOHvd2c2wR/9Ln69F0A0nN7AxEa4awjftz60HCrKB4uyf4Fjv/Ifn Ifg5OxHglbsJTYJUJyQHO4oTV1Ml1efC8qX4TTd2EomOlnYyTcFh3j1oqGtiwyCQEjBu mGKOB6Qtyb6+VjG/HWYBjZbIej88Uhho2PF/o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LT8nXFOFk2yIwkVclcGnvRQk0fRPeb3nGydIR1R6rRbmebC19QNYgWtOFyo+Q8lqmF s62P5bIln00kI9K1YZE41ayOc6bi7cbJBLT3JSjtCoFpgpQDYaN4MdxHD0akhcOUPUr4 Ssny5GFX/76jI+5e2isyaPyf5vcM4a0BYoZRM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <57B77A97-2D44-4101-8997-33E32CBEC4DA@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f1c9d250902260709s35714c06k990b07a3221afc66@xxxxxxxxxxxxxx> <49A838BE.40801@xxxxxxxxxxxxx> <f1c9d250903020806q609b6bc8se4a1765a5418c6da@xxxxxxxxxxxxxx> <f1c9d250903252359p13f2fe47r84674d183fe8629f@xxxxxxxxxxxxxx> <57B77A97-2D44-4101-8997-33E32CBEC4DA@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Mar 26, 2009 at 4:27 PM, Gianluca Guida
<Gianluca.Guida@xxxxxxxxxxxxx> wrote:
> Hi,
>
> Sorry for the late reply.
>
> On Mar 26, 2009, at 7:59 AM, Tej wrote:
>
>> On Mon, Mar 2, 2009 at 9:36 PM, Tej <bewith.tej@xxxxxxxxx> wrote:
>>>
>>> On Sat, Feb 28, 2009 at 12:32 AM, Gianluca Guida
>>> <gianluca.guida@xxxxxxxxxxxxx> wrote:
>>>>
>>>> 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.
>>>
>>> Attached patches address the four-spaces tabs and make clean issues.
>>> Hope the code is more clean and readable
>>
>> Hi
>>
>> Sorry for interrupting you guys from your busy schedule, as i just
>> want to know the current status for GCOV patches i submitted early
>> this month.
>> any feedback on "testing/coding/design/feature" will be appreciated.
>
> I've been testing it for a while, and it seems an useful and interesting
> feature.

glad to hear this

>
> A few comments, though:
>
> - As I said, while the patch is minimal enough, the feature requires some
> intrusive changes in Xen, like changing the linker script (via the
> definition of CONSTRUCTORS) and in general it changes the compiler behavior,
> so I think it should be mandatory to make this feature explicitely enabled
> at compile time, e.g.  gcov=y.

> - I am talking about Xen code only, but I think a few part of the codes
> should be more clear. I find very confusing the difference between
> xen_gcov_info and gcov_info, and all the instructions that uses them. A
> better naming scheme for the variables and more comments would be
> appreciated.

basically there should not be no difference between xen_gcov_info and
gcov_info, but due to some earlier implementation difficulties we kept
 two different structure. In final implementation those difference
narrow down drastically but we kept the both structures. I will look
back into this.

and All comments will be addressed asap.

thanks
-tej

>
> Thanks!
> Gianluca
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>