From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: javi.merino@cloud.com, Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH v3 07/13] xen/spinlock: make struct lock_profile rspinlock_t aware
Date: Fri, 24 Nov 2023 20:09:21 +0000 [thread overview]
Message-ID: <cb7ea607-b73d-4cc2-b680-fb953f8d445b@cloud.com> (raw)
In-Reply-To: <20231120113842.5897-8-jgross@suse.com>
On 20/11/2023 11:38, Juergen Gross wrote:
> Struct lock_profile contains a pointer to the spinlock it is associated
> with. Prepare support of differing spinlock_t and rspinlock_t types by
> adding a type indicator of the pointer. Use the highest bit of the
> block_cnt member for this indicator in order to not grow the struct
> while hurting only the slow path with slightly less performant code.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> V2:
> - new patch
> ---
> xen/common/spinlock.c | 26 +++++++++++++++++++-------
> xen/include/xen/spinlock.h | 10 ++++++++--
> 2 files changed, 27 insertions(+), 9 deletions(-)
>
> diff --git a/xen/common/spinlock.c b/xen/common/spinlock.c
> index 17716fc4eb..65f180203a 100644
> --- a/xen/common/spinlock.c
> +++ b/xen/common/spinlock.c
> @@ -538,19 +538,31 @@ static void spinlock_profile_iterate(lock_profile_subfunc *sub, void *par)
> static void cf_check spinlock_profile_print_elem(struct lock_profile *data,
> int32_t type, int32_t idx, void *par)
> {
> - struct spinlock *lock = data->lock;
> + unsigned int cpu;
> + uint32_t lockval;
> +
> + if ( data->is_rlock )
> + {
> + cpu = data->rlock->debug.cpu;
> + lockval = data->rlock->tickets.head_tail;
> + }
> + else
> + {
> + cpu = data->lock->debug.cpu;
> + lockval = data->lock->tickets.head_tail;
> + }
>
> printk("%s ", lock_profile_ancs[type].name);
> if ( type != LOCKPROF_TYPE_GLOBAL )
> printk("%d ", idx);
> - printk("%s: addr=%p, lockval=%08x, ", data->name, lock,
> - lock->tickets.head_tail);
> - if ( lock->debug.cpu == SPINLOCK_NO_CPU )
> + printk("%s: addr=%p, lockval=%08x, ", data->name, data->lock, lockval); > + if ( cpu == SPINLOCK_NO_CPU )
> printk("not locked\n");
> else
> - printk("cpu=%d\n", lock->debug.cpu);
> - printk(" lock:%" PRId64 "(%" PRI_stime "), block:%" PRId64 "(%" PRI_stime ")\n",
> - data->lock_cnt, data->time_hold, data->block_cnt, data->time_block);
> + printk("cpu=%u\n", cpu);
> + printk(" lock:%" PRIu64 "(%" PRI_stime "), block:%" PRIu64 "(%" PRI_stime ")\n",
> + data->lock_cnt, data->time_hold, (uint64_t)data->block_cnt,
> + data->time_block);
> }
>
> void cf_check spinlock_profile_printall(unsigned char key)
> diff --git a/xen/include/xen/spinlock.h b/xen/include/xen/spinlock.h
> index 53f0f72ac4..5ada9dce3d 100644
> --- a/xen/include/xen/spinlock.h
> +++ b/xen/include/xen/spinlock.h
> @@ -76,13 +76,19 @@ union lock_debug { };
> */
>
> struct spinlock;
> +/* Temporary hack until a dedicated struct rspinlock is existing. */
> +#define rspinlock spinlock
>
> struct lock_profile {
> struct lock_profile *next; /* forward link */
> const char *name; /* lock name */
> - struct spinlock *lock; /* the lock itself */
> + union {
> + struct spinlock *lock; /* the lock itself */
> + struct rspinlock *rlock; /* the recursive lock itself * > + };
> uint64_t lock_cnt; /* # of complete locking ops */
> - uint64_t block_cnt; /* # of complete wait for lock */
> + uint64_t block_cnt:63; /* # of complete wait for lock */
> + uint64_t is_rlock:1; /* use rlock pointer */
> s_time_t time_hold; /* cumulated lock time */
> s_time_t time_block; /* cumulated wait time */
> s_time_t time_locked; /* system time of last locking */
LGTM.
Acked-by: Alejandro Vallejo <alejandro.vallejo@cloud.com>
Cheers,
Alejandro
next prev parent reply other threads:[~2023-11-24 20:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 11:38 [PATCH v3 00/13] xen/spinlock: make recursive spinlocks a dedicated type Juergen Gross
2023-11-20 11:38 ` [PATCH v3 01/13] xen/spinlock: fix coding style issues Juergen Gross
2023-11-20 11:38 ` [PATCH v3 02/13] xen/spinlock: reduce lock profile ifdefs Juergen Gross
2023-11-24 17:59 ` Alejandro Vallejo
2023-11-24 18:12 ` Alejandro Vallejo
2023-11-28 13:07 ` Juergen Gross
2023-11-20 11:38 ` [PATCH v3 03/13] xen/spinlock: make spinlock initializers more readable Juergen Gross
2023-11-20 11:38 ` [PATCH v3 04/13] xen/spinlock: introduce new type for recursive spinlocks Juergen Gross
2023-11-24 18:59 ` Alejandro Vallejo
2023-11-28 13:16 ` Juergen Gross
2023-11-28 13:36 ` Jan Beulich
2023-11-20 11:38 ` [PATCH v3 05/13] xen/spinlock: rename recursive lock functions Juergen Gross
2023-11-20 11:38 ` [PATCH v3 06/13] xen/spinlock: add rspin_[un]lock_irq[save|restore]() Juergen Gross
2023-11-24 19:23 ` Alejandro Vallejo
2023-11-28 13:24 ` Juergen Gross
2023-11-20 11:38 ` [PATCH v3 07/13] xen/spinlock: make struct lock_profile rspinlock_t aware Juergen Gross
2023-11-24 20:09 ` Alejandro Vallejo [this message]
2023-11-20 11:38 ` [PATCH v3 08/13] xen/spinlock: add explicit non-recursive locking functions Juergen Gross
2023-11-20 11:38 ` [PATCH v3 09/13] xen/spinlock: add another function level Juergen Gross
2023-11-20 11:38 ` [PATCH v3 10/13] xen/spinlock: add missing rspin_is_locked() and rspin_barrier() Juergen Gross
2023-11-20 11:38 ` [PATCH v3 11/13] xen/spinlock: split recursive spinlocks from normal ones Juergen Gross
2023-11-20 11:38 ` [PATCH v3 12/13] xen/spinlock: remove indirection through macros for spin_*() functions Juergen Gross
2023-11-20 11:38 ` [PATCH v3 13/13] xen/spinlock: support higher number of cpus Juergen Gross
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=cb7ea607-b73d-4cc2-b680-fb953f8d445b@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=javi.merino@cloud.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.