From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>,
gleb@kernel.org, pbonzini@redhat.com
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH A] KVM: Simplify kvm->tlbs_dirty handling
Date: Tue, 18 Feb 2014 17:43:24 +0800 [thread overview]
Message-ID: <53032B3C.5000403@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140218172247.ca61f503.yoshikawa_takuya_b1@lab.ntt.co.jp>
On 02/18/2014 04:22 PM, Takuya Yoshikawa wrote:
> When this was introduced, kvm_flush_remote_tlbs() could be called
> without holding mmu_lock. It is now acknowledged that the function
> must be called before releasing mmu_lock, and all callers have already
> been changed to do so.
>
I have already posted the patch to moving flush tlb out of mmu-lock
when do dirty tracking:
KVM: MMU: flush tlb out of mmu lock when write-protect the sptes
Actually some patches (patch 1 - patch 4) in that patchset can be
pickup-ed separately and i should apologize for the patchset was
not updated for a long time since i was busy on other development.
And moving tlb flush out of mmu-lock should be going on in the
future, so i think the B patch is more acceptable.
next prev parent reply other threads:[~2014-02-18 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 8:21 [PATCH A or B] KVM: kvm->tlbs_dirty handling Takuya Yoshikawa
2014-02-18 8:22 ` [PATCH A] KVM: Simplify " Takuya Yoshikawa
2014-02-18 9:07 ` Paolo Bonzini
2014-02-19 0:44 ` Takuya Yoshikawa
2014-02-19 12:04 ` Paolo Bonzini
2014-02-18 9:43 ` Xiao Guangrong [this message]
2014-02-19 0:40 ` Takuya Yoshikawa
2014-02-18 8:23 ` [PATCH B] KVM: Explain tlbs_dirty trick in kvm_flush_remote_tlbs() 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=53032B3C.5000403@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yoshikawa_takuya_b1@lab.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.