All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Mike Day <ncmike@ncultra.org>
Cc: Paul Mckenney <paulmck@linux.vnet.ibm.com>,
	Mathew Desnoyers <mathieu.desnoyers@efficios.com>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [RFC PATCH] Convert ram_list to RCU DQ V2
Date: Tue, 03 Sep 2013 16:21:04 +0200	[thread overview]
Message-ID: <5225F050.7090600@redhat.com> (raw)
In-Reply-To: <CAGaKXu1YsX-7mg9DkygwNbyL41E46m1v9LpqyThvCe4n9X_9Yw@mail.gmail.com>

Il 03/09/2013 16:19, Mike Day ha scritto:
> 
> Yeah. So how about we say for now that the rcu critical section status
> upon entry to the ram_control_*_iterate functions is undefined. I'll
> make some updates.

Sure.

Paolo

      reply	other threads:[~2013-09-03 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 16:06 [Qemu-devel] [RFC PATCH] Convert ram_list to RCU DQ V2 Mike Day
2013-08-30 16:38 ` Paolo Bonzini
2013-09-03 13:56   ` Mike Day
2013-09-03 14:09     ` Paolo Bonzini
2013-09-03 14:19       ` Mike Day
2013-09-03 14:21         ` Paolo Bonzini [this message]

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=5225F050.7090600@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=ncmike@ncultra.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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.