From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org, yoshikawa.takuya@oss.ntt.co.jp
Subject: Re: [PATCH 1/1 v2] KVM: Reduce mmu_lock contention during dirty logging by cond_resched()
Date: Sun, 29 Apr 2012 17:39:35 +0300 [thread overview]
Message-ID: <4F9D52A7.8020105@redhat.com> (raw)
In-Reply-To: <20120429232407.684da454a0862f121754a126@gmail.com>
On 04/29/2012 05:24 PM, Takuya Yoshikawa wrote:
> On Sun, 29 Apr 2012 15:59:18 +0300
> Avi Kivity <avi@redhat.com> wrote:
>
> > > As we discussed before, we need to add some tricks to de-couple mmu_lock and
> > > TLB flush.
> >
> > Ok, let's discuss them (we can apply the patch independently). Do you
> > have something in mind?
> >
>
> How about your own idea?
>
Looks pretty good, if I do say so myself. I'll take a shot at
implementing it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-04-29 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 10:05 [PATCH 0/1 v2] KVM: Alleviate mmu_lock contention during dirty logging Takuya Yoshikawa
2012-04-28 10:07 ` [PATCH 1/1 v2] KVM: Reduce mmu_lock contention during dirty logging by cond_resched() Takuya Yoshikawa
2012-04-29 11:27 ` Avi Kivity
2012-04-29 12:17 ` Takuya Yoshikawa
2012-04-29 12:59 ` Avi Kivity
2012-04-29 14:24 ` Takuya Yoshikawa
2012-04-29 14:39 ` Avi Kivity [this message]
2012-04-29 14:55 ` Takuya Yoshikawa
2012-04-29 15:00 ` Avi Kivity
2012-04-29 15:13 ` Takuya Yoshikawa
2012-04-29 15:20 ` Avi Kivity
2012-04-30 14:06 ` Takuya Yoshikawa
2012-05-01 3:04 ` Marcelo Tosatti
2012-05-01 13:14 ` Takuya Yoshikawa
2012-05-01 3:07 ` Marcelo Tosatti
2012-05-02 11:24 ` Heavy memory_region_get_dirty() -- Re: [PATCH 0/1 v2] KVM: Alleviate mmu_lock contention during dirty logging Takuya Yoshikawa
2012-05-02 11:33 ` Avi Kivity
2012-05-02 14:20 ` 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=4F9D52A7.8020105@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox