All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Juergen Gross <jgross@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>,
	"Bertrand Marquis" <bertrand.marquis@arm.com>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"George Dunlap" <george.dunlap@citrix.com>,
	"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>,
	"Tamas K Lengyel" <tamas@tklengyel.com>,
	"Lukasz Hawrylko" <lukasz@hawrylko.pl>,
	"Daniel P. Smith" <dpsmith@apertussolutions.com>,
	"Mateusz Mówka" <mateusz.mowka@intel.com>,
	"Paul Durrant" <paul@xen.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [RFC PATCH 1/3] xen/spinlock: add explicit non-recursive locking functions
Date: Wed, 14 Dec 2022 11:21:19 +0100	[thread overview]
Message-ID: <5a3c8cd5-7f78-aaaa-0338-d063bb04e357@suse.com> (raw)
In-Reply-To: <20220910154959.15971-2-jgross@suse.com>

On 10.09.2022 17:49, Juergen Gross wrote:
> In order to prepare a type-safe recursive spinlock structure, add
> explicitly non-recursive locking functions to be used for non-recursive
> locking of spinlocks, which are use recursively, too.

While I can see that something needs doing, a function name like
spin_unlock_nonrecursive_irqrestore() is really unwieldy, imo.

Just one minor further remark:

> @@ -64,7 +64,7 @@ void pcidevs_unlock(void)
>  
>  bool_t pcidevs_locked(void)
>  {
> -    return !!spin_is_locked(&_pcidevs_lock);
> +    return !!spin_recursive_is_locked(&_pcidevs_lock);
>  }

While touching this line, could you please also get rid of the !! ?

Jan


  reply	other threads:[~2022-12-14 10:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 15:49 [RFC PATCH 0/3] xen/spinlock: make recursive spinlocks a dedicated type Juergen Gross
2022-09-10 15:49 ` [RFC PATCH 1/3] xen/spinlock: add explicit non-recursive locking functions Juergen Gross
2022-12-14 10:21   ` Jan Beulich [this message]
2022-12-14 10:32     ` Juergen Gross
2022-12-14 10:32     ` Jan Beulich
2022-12-14 10:38       ` Juergen Gross
2022-09-10 15:49 ` [RFC PATCH 2/3] xen/spinlock: split recursive spinlocks from normal ones Juergen Gross
2022-12-14 10:39   ` Jan Beulich
2022-12-14 11:10     ` Juergen Gross
2022-12-14 11:29       ` Jan Beulich
2022-12-14 11:38         ` Juergen Gross
2022-09-10 15:49 ` [RFC PATCH 3/3] xen/spinlock: support higher number of cpus Juergen Gross
2022-12-14 15:03 ` [RFC PATCH 0/3] xen/spinlock: make recursive spinlocks a dedicated type Daniel P. Smith
2022-12-14 15:31   ` Juergen Gross
2022-12-14 16:25     ` Daniel P. Smith
2022-12-14 16:36       ` Juergen Gross
2022-12-15  7:48         ` Jan Beulich
2022-12-15  8:03           ` Juergen Gross
2022-12-15  8:29             ` Julien Grall

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=5a3c8cd5-7f78-aaaa-0338-d063bb04e357@suse.com \
    --to=jbeulich@suse.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=george.dunlap@citrix.com \
    --cc=jgross@suse.com \
    --cc=julien@xen.org \
    --cc=lukasz@hawrylko.pl \
    --cc=mateusz.mowka@intel.com \
    --cc=paul@xen.org \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas@tklengyel.com \
    --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.