From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 23/29] bitmap: add atomic set functions
Date: Wed, 27 May 2015 15:58:08 +0800	[thread overview]
Message-ID: <20150527075808.GG1751@dhcp-14-238.nay.redhat.com> (raw)
In-Reply-To: <1432659305-54578-24-git-send-email-pbonzini@redhat.com>
On Tue, 05/26 18:54, Paolo Bonzini wrote:
> From: Stefan Hajnoczi <stefanha@redhat.com>
> 
> Use atomic_or() for atomic bitmaps where several threads may set bits at
> the same time.  This avoids the race condition between threads loading
> an element, bitwise ORing, and then storing the element.
> 
> When setting all bits in a word we can avoid atomic ops and instead just
> use an smp_mb() at the end.
> 
> Most bitmap users don't need atomicity so introduce new functions.
> 
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> Message-Id: <1417519399-3166-2-git-send-email-stefanha@redhat.com>
> [Avoid barrier in the single word case, use full barrier instead of write.
>  - Paolo]
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  include/qemu/bitmap.h |  2 ++
>  include/qemu/bitops.h | 14 ++++++++++++++
>  util/bitmap.c         | 38 ++++++++++++++++++++++++++++++++++++++
>  3 files changed, 54 insertions(+)
> 
> diff --git a/include/qemu/bitmap.h b/include/qemu/bitmap.h
> index f0273c9..3e0a4f3 100644
> --- a/include/qemu/bitmap.h
> +++ b/include/qemu/bitmap.h
> @@ -39,6 +39,7 @@
>   * bitmap_empty(src, nbits)			Are all bits zero in *src?
>   * bitmap_full(src, nbits)			Are all bits set in *src?
>   * bitmap_set(dst, pos, nbits)			Set specified bit area
> + * bitmap_set_atomic(dst, pos, nbits)   Set specified bit area with atomic ops
The tab/space mix is not consistent. Fixing can be on top.
>   * bitmap_clear(dst, pos, nbits)		Clear specified bit area
>   * bitmap_find_next_zero_area(buf, len, pos, n, mask)	Find bit free area
>   */
> @@ -226,6 +227,7 @@ static inline int bitmap_intersects(const unsigned long *src1,
>  }
>  
>  void bitmap_set(unsigned long *map, long i, long len);
> +void bitmap_set_atomic(unsigned long *map, long i, long len);
>  void bitmap_clear(unsigned long *map, long start, long nr);
>  unsigned long bitmap_find_next_zero_area(unsigned long *map,
>                                           unsigned long size,
> diff --git a/include/qemu/bitops.h b/include/qemu/bitops.h
> index 8abdcf9..8164225 100644
> --- a/include/qemu/bitops.h
> +++ b/include/qemu/bitops.h
> @@ -16,6 +16,7 @@
>  #include <assert.h>
>  
>  #include "host-utils.h"
> +#include "atomic.h"
>  
>  #define BITS_PER_BYTE           CHAR_BIT
>  #define BITS_PER_LONG           (sizeof (unsigned long) * BITS_PER_BYTE)
> @@ -39,6 +40,19 @@ static inline void set_bit(long nr, unsigned long *addr)
>  }
>  
>  /**
> + * set_bit_atomic - Set a bit in memory atomically
> + * @nr: the bit to set
> + * @addr: the address to start counting from
> + */
> +static inline void set_bit_atomic(long nr, unsigned long *addr)
> +{
> +    unsigned long mask = BIT_MASK(nr);
> +    unsigned long *p = addr + BIT_WORD(nr);
> +
> +    atomic_or(p, mask);
> +}
Where is this function used?
Fam
next prev parent reply	other threads:[~2015-05-27  7:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 16:54 [Qemu-devel] [PATCH v3 00/29] Dirty bitmap atomic access and optimizations Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 01/29] memory: the only dirty memory flag for users is DIRTY_MEMORY_VGA Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 02/29] g364fb: remove pointless call to memory_region_set_coalescing Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 03/29] display: enable DIRTY_MEMORY_VGA tracking explicitly Paolo Bonzini
2015-05-27  7:47   ` Fam Zheng
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 04/29] display: add memory_region_sync_dirty_bitmap calls Paolo Bonzini
2015-05-27  7:49   ` Fam Zheng
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 05/29] memory: differentiate memory_region_is_logging and memory_region_get_dirty_log_mask Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 06/29] memory: prepare for multiple bits in the dirty log mask Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 07/29] framebuffer: check memory_region_is_logging Paolo Bonzini
2015-05-27  7:51   ` Fam Zheng
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 08/29] ui/console: remove dpy_gfx_update_dirty Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 09/29] memory: track DIRTY_MEMORY_CODE in mr->dirty_log_mask Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 10/29] kvm: accept non-mapped memory in kvm_dirty_pages_log_change Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 11/29] memory: include DIRTY_MEMORY_MIGRATION in the dirty log mask Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 12/29] kvm: remove special handling of " Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 13/29] ram_addr: tweaks to xen_modified_memory Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 14/29] exec: use memory_region_get_dirty_log_mask to optimize dirty tracking Paolo Bonzini
2015-05-27  7:54   ` Fam Zheng
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 15/29] exec: move functions to translate-all.h Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 16/29] translate-all: remove unnecessary argument to tb_invalidate_phys_range Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 17/29] cputlb: remove useless arguments to tlb_unprotect_code_phys, rename Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 18/29] translate-all: make less of tb_invalidate_phys_page_range depend on is_cpu_write_access Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 19/29] exec: pass client mask to cpu_physical_memory_set_dirty_range Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 20/29] exec: invert return value of cpu_physical_memory_get_clean, rename Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 21/29] exec: only check relevant bitmaps for cleanliness Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 22/29] memory: do not touch code dirty bitmap unless TCG is enabled Paolo Bonzini
2015-05-26 16:54 ` [Qemu-devel] [PATCH v3 23/29] bitmap: add atomic set functions Paolo Bonzini
2015-05-27  7:58   ` Fam Zheng [this message]
2015-05-27  9:41     ` Paolo Bonzini
2015-05-28  2:15   ` Fam Zheng
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 24/29] bitmap: add atomic test and clear Paolo Bonzini
2015-05-27  8:05   ` Fam Zheng
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 25/29] memory: use atomic ops for setting dirty memory bits Paolo Bonzini
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 26/29] migration: move dirty bitmap sync to ram_addr.h Paolo Bonzini
2015-05-27  8:21   ` Fam Zheng
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 27/29] memory: replace cpu_physical_memory_reset_dirty() with test-and-clear Paolo Bonzini
2015-05-26 22:40   ` Aurelien Jarno
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 28/29] memory: make cpu_physical_memory_sync_dirty_bitmap() fully atomic Paolo Bonzini
2015-05-26 16:55 ` [Qemu-devel] [PATCH v3 29/29] memory: use mr->ram_addr in "is this RAM?" assertions Paolo Bonzini
2015-05-26 22:43 ` [Qemu-devel] [PATCH v3 00/29] Dirty bitmap atomic access and optimizations Aurelien Jarno
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=20150527075808.GG1751@dhcp-14-238.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).