All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, pbonzini@redhat.com,
	quintela@redhat.com
Subject: Re: [RFC PATCH v4 2/5] ramlist mutex
Date: Tue, 23 Aug 2011 06:15:33 -0300	[thread overview]
Message-ID: <20110823091533.GA5207@amt.cnet> (raw)
In-Reply-To: <8f99d56f3a48b6255cf70425bc435d8f231f5352.1313552764.git.udeshpan@redhat.com>

On Tue, Aug 16, 2011 at 11:56:37PM -0400, Umesh Deshpande wrote:
> ramlist mutex is implemented to protect the RAMBlock list traversal in the
> migration thread from their addition/removal from the iothread.
> 
> Signed-off-by: Umesh Deshpande <udeshpan@redhat.com>
> ---
>  cpu-all.h     |    2 ++
>  exec.c        |   19 +++++++++++++++++++
>  qemu-common.h |    2 ++
>  3 files changed, 23 insertions(+), 0 deletions(-)
> 
> diff --git a/cpu-all.h b/cpu-all.h
> index 6b217a2..eab9803 100644
> --- a/cpu-all.h
> +++ b/cpu-all.h
> @@ -21,6 +21,7 @@
>  
>  #include "qemu-common.h"
>  #include "cpu-common.h"
> +#include "qemu-thread.h"
>  
>  /* some important defines:
>   *
> @@ -932,6 +933,7 @@ typedef struct RAMBlock {
>  } RAMBlock;
>  
>  typedef struct RAMList {
> +    QemuMutex mutex;
>      uint8_t *phys_dirty;
>      QLIST_HEAD(ram, RAMBlock) blocks;
>      QLIST_HEAD(, RAMBlock) blocks_mru;

A comment on what the mutex protects would be good.

WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
	quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v4 2/5] ramlist mutex
Date: Tue, 23 Aug 2011 06:15:33 -0300	[thread overview]
Message-ID: <20110823091533.GA5207@amt.cnet> (raw)
In-Reply-To: <8f99d56f3a48b6255cf70425bc435d8f231f5352.1313552764.git.udeshpan@redhat.com>

On Tue, Aug 16, 2011 at 11:56:37PM -0400, Umesh Deshpande wrote:
> ramlist mutex is implemented to protect the RAMBlock list traversal in the
> migration thread from their addition/removal from the iothread.
> 
> Signed-off-by: Umesh Deshpande <udeshpan@redhat.com>
> ---
>  cpu-all.h     |    2 ++
>  exec.c        |   19 +++++++++++++++++++
>  qemu-common.h |    2 ++
>  3 files changed, 23 insertions(+), 0 deletions(-)
> 
> diff --git a/cpu-all.h b/cpu-all.h
> index 6b217a2..eab9803 100644
> --- a/cpu-all.h
> +++ b/cpu-all.h
> @@ -21,6 +21,7 @@
>  
>  #include "qemu-common.h"
>  #include "cpu-common.h"
> +#include "qemu-thread.h"
>  
>  /* some important defines:
>   *
> @@ -932,6 +933,7 @@ typedef struct RAMBlock {
>  } RAMBlock;
>  
>  typedef struct RAMList {
> +    QemuMutex mutex;
>      uint8_t *phys_dirty;
>      QLIST_HEAD(ram, RAMBlock) blocks;
>      QLIST_HEAD(, RAMBlock) blocks_mru;

A comment on what the mutex protects would be good.

  parent reply	other threads:[~2011-08-23 10:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17  3:56 [RFC PATCH v4 0/5] Separate thread for VM migration Umesh Deshpande
2011-08-17  3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17  3:56 ` [RFC PATCH v4 1/5] MRU ram list Umesh Deshpande
2011-08-17  3:56   ` [Qemu-devel] " Umesh Deshpande
2011-08-17  3:56 ` [RFC PATCH v4 2/5] ramlist mutex Umesh Deshpande
2011-08-17  3:56   ` [Qemu-devel] " Umesh Deshpande
2011-08-17  6:28   ` Paolo Bonzini
2011-08-17  6:28     ` [Qemu-devel] " Paolo Bonzini
2011-08-19  6:20     ` Umesh Deshpande
2011-08-19  6:20       ` [Qemu-devel] " Umesh Deshpande
2011-08-22  6:48       ` Paolo Bonzini
2011-08-22  6:48         ` [Qemu-devel] " Paolo Bonzini
2011-08-23  9:15   ` Marcelo Tosatti [this message]
2011-08-23  9:15     ` Marcelo Tosatti
2011-08-23  9:17     ` Marcelo Tosatti
2011-08-23  9:17       ` [Qemu-devel] " Marcelo Tosatti
2011-08-23 11:41       ` Paolo Bonzini
2011-08-23 11:41         ` [Qemu-devel] " Paolo Bonzini
2011-08-23 12:16         ` Marcelo Tosatti
2011-08-23 12:16           ` [Qemu-devel] " Marcelo Tosatti
2011-08-17  3:56 ` [RFC PATCH v4 3/5] separate migration bitmap Umesh Deshpande
2011-08-17  3:56   ` [Qemu-devel] " Umesh Deshpande
2011-08-17  3:56 ` [RFC PATCH v4 4/5] separate thread for VM migration Umesh Deshpande
2011-08-17  3:56   ` [Qemu-devel] " Umesh Deshpande
2011-08-17  7:13   ` Paolo Bonzini
2011-08-17  7:13     ` [Qemu-devel] " Paolo Bonzini
2011-08-17  3:56 ` [RFC PATCH v3 5/5] Making iothread block for migrate_cancel Umesh Deshpande
2011-08-17  3:56   ` [Qemu-devel] " Umesh Deshpande
2011-08-17  7:14   ` Paolo Bonzini
2011-08-17  7:14     ` [Qemu-devel] " 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=20110823091533.GA5207@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=udeshpan@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.