From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: KVM list <kvm@vger.kernel.org>
Subject: Updating dirty bitmap by non-atomic set bit is safe?
Date: Tue, 23 Mar 2010 15:12:04 +0900 [thread overview]
Message-ID: <4BA85BB4.8030001@oss.ntt.co.jp> (raw)
Hi, does anybody knows about this?
Currently, dirty bitmap is updated by generic___set_le_bit().
I checked the git log and mail archives but could not find any
explanation why replacing set_bit() by generic___set_le_bit() is
safe.
Thanks,
Takuya
next reply other threads:[~2010-03-23 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 6:12 Takuya Yoshikawa [this message]
2010-03-23 9:18 ` Updating dirty bitmap by non-atomic set bit is safe? Avi Kivity
2010-03-23 10:17 ` Takuya Yoshikawa
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=4BA85BB4.8030001@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=kvm@vger.kernel.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.