All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, pbonzini@redhat.com, ehabkost@redhat.com,
	berrange@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Automatic RCU read unlock
Date: Wed, 25 Sep 2019 14:13:24 +0100	[thread overview]
Message-ID: <20190925131324.GG21544@work-vm> (raw)
In-Reply-To: <20190913102538.24167-1-dgilbert@redhat.com>

* Dr. David Alan Gilbert (git) (dgilbert@redhat.com) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> This patch uses glib's g_auto mechanism to automatically free
> rcu_read_lock's at the end of the block.  Given that humans
> have a habit of forgetting an error path somewhere it's
> best to leave it to the compiler.

I've had to unqueue this - clang doesn't like the apparently unused
auto variable; we need to find a way to make that happy.

Dave

> v3
>   Add block-head version of macro
>   Rename
>   Add docs
>   Convert more cases using the block-head version
> 
> Dr. David Alan Gilbert (5):
>   rcu: Add automatically released rcu_read_lock variants
>   migration: Fix missing rcu_read_unlock
>   migration: Use automatic rcu_read unlock in ram.c
>   migration: Use automatic rcu_read unlock in rdma.c
>   rcu: Use automatic rc_read unlock in core memory/exec code
> 
>  docs/devel/rcu.txt      |  16 +++
>  exec.c                  | 120 +++++++---------
>  include/exec/ram_addr.h | 138 +++++++++----------
>  include/qemu/rcu.h      |  25 ++++
>  memory.c                |  15 +-
>  migration/ram.c         | 295 +++++++++++++++++++---------------------
>  migration/rdma.c        |  57 ++------
>  7 files changed, 310 insertions(+), 356 deletions(-)
> 
> -- 
> 2.21.0
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK


  parent reply	other threads:[~2019-09-25 13:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 10:25 [Qemu-devel] [PATCH v3 0/5] Automatic RCU read unlock Dr. David Alan Gilbert (git)
2019-09-13 10:25 ` [Qemu-devel] [PATCH v3 1/5] rcu: Add automatically released rcu_read_lock variants Dr. David Alan Gilbert (git)
2019-09-13 12:01   ` Paolo Bonzini
2019-09-13 18:45     ` Dr. David Alan Gilbert
2019-09-19 17:31   ` Daniel P. Berrangé
2019-09-13 10:25 ` [Qemu-devel] [PATCH v3 2/5] migration: Fix missing rcu_read_unlock Dr. David Alan Gilbert (git)
2019-09-19 17:32   ` Daniel P. Berrangé
2019-09-13 10:25 ` [Qemu-devel] [PATCH v3 3/5] migration: Use automatic rcu_read unlock in ram.c Dr. David Alan Gilbert (git)
2019-09-19 17:33   ` Daniel P. Berrangé
2019-09-13 10:25 ` [Qemu-devel] [PATCH v3 4/5] migration: Use automatic rcu_read unlock in rdma.c Dr. David Alan Gilbert (git)
2019-09-19 17:34   ` Daniel P. Berrangé
2019-09-13 10:25 ` [Qemu-devel] [PATCH v3 5/5] rcu: Use automatic rc_read unlock in core memory/exec code Dr. David Alan Gilbert (git)
2019-09-19 17:35   ` Daniel P. Berrangé
2019-09-25 10:32 ` [Qemu-devel] [PATCH v3 0/5] Automatic RCU read unlock Dr. David Alan Gilbert
2019-09-25 13:13 ` Dr. David Alan Gilbert [this message]
2019-09-25 13:21   ` Paolo Bonzini
2019-09-25 15:28     ` Dr. David Alan Gilbert
2019-09-25 15:49       ` Daniel P. Berrangé
2019-09-25 16:47       ` Paolo Bonzini

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=20190925131324.GG21544@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.