From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takuya Yoshikawa Subject: Updating dirty bitmap by non-atomic set bit is safe? Date: Tue, 23 Mar 2010 15:12:04 +0900 Message-ID: <4BA85BB4.8030001@oss.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from serv2.oss.ntt.co.jp ([222.151.198.100]:34170 "EHLO serv2.oss.ntt.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752826Ab0CWGJV (ORCPT ); Tue, 23 Mar 2010 02:09:21 -0400 Received: from serv2.oss.ntt.co.jp (localhost [127.0.0.1]) by serv2.oss.ntt.co.jp (Postfix) with ESMTP id ADE582482A4 for ; Tue, 23 Mar 2010 15:09:20 +0900 (JST) Received: from serv1.oss.ntt.co.jp (serv1.oss.ntt.co.jp [172.19.0.2]) by serv2.oss.ntt.co.jp (Postfix) with ESMTP id 9AEDF2481EF for ; Tue, 23 Mar 2010 15:09:20 +0900 (JST) Received: from [127.0.0.1] (unknown [172.17.1.64]) by serv1.oss.ntt.co.jp (Postfix) with ESMTP id 72BA511C0BA for ; Tue, 23 Mar 2010 15:09:18 +0900 (JST) Sender: kvm-owner@vger.kernel.org List-ID: 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