All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: RE: [PATCH] Make lock profiling usable again
Date: Mon, 07 Nov 2011 06:52:06 +0100	[thread overview]
Message-ID: <4EB77206.3050706@ts.fujitsu.com> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E281497FD88@shsmsx502.ccr.corp.intel.com>

Xudong,

I found that bug after sending you the patch and included the correction
already in the version sent to xen-devel.


Juergen

On 11/05/2011 05:10 AM, Hao, Xudong wrote:
> Initialize profile to NULL when lock profiling is not enabled.
>
> diff -r 068d3d55ce6e xen/include/xen/spinlock.h
> --- a/xen/include/xen/spinlock.h        Tue Nov 01 19:03:38 2011 +0000
> +++ b/xen/include/xen/spinlock.h        Sat Nov 05 11:57:38 2011 +0800
> @@ -108,7 +108,7 @@ struct lock_profile_qhead { };
>   struct lock_profile_qhead { };
>
>   #define SPIN_LOCK_UNLOCKED                                                    \
> -    { _RAW_SPIN_LOCK_UNLOCKED, 0xfffu, 0, _LOCK_DEBUG, { } }
> +    { _RAW_SPIN_LOCK_UNLOCKED, 0xfffu, 0, _LOCK_DEBUG, NULL }
>   #define DEFINE_SPINLOCK(l) spinlock_t l = SPIN_LOCK_UNLOCKED
>
>   #define spin_lock_init_prof(s, l) spin_lock_init(&((s)->l))
>
>
> Thanks,
> -Xudong
>
>
>> -----Original Message-----
>> From: Juergen Gross [mailto:juergen.gross@ts.fujitsu.com]
>> Sent: Friday, November 04, 2011 8:53 PM
>> To: xen-devel@lists.xensource.com
>> Cc: Hao, Xudong
>> Subject: [PATCH] Make lock profiling usable again
>>
>> Using lock profiling (option lock_profile in xen/Rules.mk) resulted in build errors.
>> Changes:
>> - Include public/sysctl.h in spinlock.h when using lock profiling.
>> - Allocate profile data in an own structure to avoid struct domain becoming
>>    larger then one page
>>
>> Signed-off-by: juergen.gross@ts.fujitsu.com
>>
>>
>> 2 files changed, 44 insertions(+), 24 deletions(-)
>> xen/common/spinlock.c      |   34 +++++++++++++++++++++-------------
>> xen/include/xen/spinlock.h |   34 +++++++++++++++++++++++-----------
>>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>


-- 
Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2011-11-07  5:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 12:52 [PATCH] Make lock profiling usable again Juergen Gross
2011-11-05  4:10 ` Hao, Xudong
2011-11-07  5:52   ` Juergen Gross [this message]
2011-11-07  6:00     ` Hao, Xudong

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=4EB77206.3050706@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xudong.hao@intel.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.