All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emilio Cota <cota@braap.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 3/4] util/qht: use striped locks under TSAN
Date: Mon, 9 Jan 2023 17:10:08 -0500	[thread overview]
Message-ID: <Y7yQwHMNArx2tlvV@cota-l14> (raw)
In-Reply-To: <4f9cf406-1a46-8f7c-6a52-fb13d8c27317@linaro.org>

On Sun, Jan 08, 2023 at 11:51:44 -0800, Richard Henderson wrote:
> On 1/8/23 08:39, Emilio Cota wrote:
> > +static inline void qht_bucket_lock_init(const struct qht_map *map,
> > +                                        struct qht_bucket *b)
> > +{
> > +    qht_do_if_first_in_stripe(map, b, qemu_spin_init);
> > +}
> > +
> > +static inline void qht_bucket_lock_destroy(const struct qht_map *map,
> > +                                           struct qht_bucket *b)
> > +{
> > +    qht_do_if_first_in_stripe(map, b, (void (*)(QemuSpin *))qemu_spin_destroy);
> > +}
> 
> I think it's clear the declaration of qemu_spin_destroy is wrong vs const.

Done, added a separate patch for this.

> Why do you create two wrappers for qht_do_if_first_in_stripe, but...
> 
> > +static inline void qht_head_init(struct qht_map *map, struct qht_bucket *b)
> >   {
> >       memset(b, 0, sizeof(*b));
> > -    qemu_spin_init(&b->lock);
> > +    qht_bucket_lock_init(map, b);
> >       seqlock_init(&b->sequence);
> >   }
> > @@ -250,7 +328,7 @@ static void qht_map_lock_buckets(struct qht_map *map)
> >       for (i = 0; i < map->n_buckets; i++) {
> >           struct qht_bucket *b = &map->buckets[i];
> > -        qemu_spin_lock(&b->lock);
> > +        qht_do_if_first_in_stripe(map, b, qemu_spin_lock);
> >       }
> 
> ... not others?

Thought the remaining two cases were obvious enough.

I've now removed the wrappers.

> The actual logic of the stripe seems ok.

Thanks!

		Emilio


  reply	other threads:[~2023-01-09 22:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-08 16:39 [PATCH 0/4] tsan fixes Emilio Cota
2023-01-08 16:39 ` [PATCH 1/4] cpu: free cpu->tb_jmp_cache with RCU Emilio Cota
2023-01-08 19:19   ` Richard Henderson
2023-01-09 21:52     ` Emilio Cota
2023-01-08 16:39 ` [PATCH 2/4] util/qht: add missing atomic_set(hashes[i]) Emilio Cota
2023-01-08 19:20   ` Richard Henderson
2023-01-08 19:54   ` Philippe Mathieu-Daudé
2023-01-08 16:39 ` [PATCH 3/4] util/qht: use striped locks under TSAN Emilio Cota
2023-01-08 19:51   ` Richard Henderson
2023-01-09 22:10     ` Emilio Cota [this message]
2023-01-08 16:39 ` [PATCH 4/4] plugins: make qemu_plugin_user_exit's locking order consistent with fork_start's Emilio Cota
2023-01-08 19:31   ` Richard Henderson

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=Y7yQwHMNArx2tlvV@cota-l14 \
    --to=cota@braap.org \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.