From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] KVM: mmu_notifier: Flush TLBs before releasing mmu_lock
Date: Fri, 17 Feb 2012 10:36:45 +0800 [thread overview]
Message-ID: <4F3DBD3D.4060202@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F3CEF16.5060405@redhat.com>
On 02/16/2012 07:57 PM, Avi Kivity wrote:
> Suppose at point A another thread executes defer_remote_flush(),
> commit_remote_flush(), and defer_remote_flush() again. This brings the
> balue of tlbs_dirty back to 1 again, with the tlbs dirty. The cmpxchg()
> then resets tlbs_dirty, leaving the actual tlbs dirty.
>
Oh, right, sorry for my careless!
prev parent reply other threads:[~2012-02-17 2:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 6:28 [PATCH 1/2] KVM: mmu_notifier: Flush TLBs before releasing mmu_lock Takuya Yoshikawa
2012-02-10 6:29 ` [PATCH 2/2] KVM: MMU: Flush TLBs only once in invlpg() " Takuya Yoshikawa
2012-02-10 6:55 ` Xiao Guangrong
2012-02-10 7:21 ` Takuya Yoshikawa
2012-02-10 7:42 ` Xiao Guangrong
2012-02-14 4:36 ` Takuya Yoshikawa
2012-02-14 4:56 ` Takuya Yoshikawa
2012-02-14 17:21 ` Andrea Arcangeli
2012-02-10 7:52 ` [PATCH 1/2] KVM: mmu_notifier: Flush TLBs " Xiao Guangrong
2012-02-13 6:00 ` Takuya Yoshikawa
2012-02-14 17:27 ` Andrea Arcangeli
2012-02-10 17:26 ` Marcelo Tosatti
2012-02-14 17:10 ` Andrea Arcangeli
2012-02-14 17:29 ` Marcelo Tosatti
2012-02-14 18:53 ` Andrea Arcangeli
2012-02-14 19:43 ` Marcelo Tosatti
2012-02-15 9:18 ` Avi Kivity
2012-02-15 9:47 ` Avi Kivity
2012-02-15 11:37 ` Xiao Guangrong
2012-02-15 14:07 ` Avi Kivity
2012-02-15 19:16 ` Andrea Arcangeli
2012-02-16 4:50 ` Xiao Guangrong
2012-02-16 11:57 ` Avi Kivity
2012-02-17 2:36 ` Xiao Guangrong [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=4F3DBD3D.4060202@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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.