All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>,
	kvm@vger.kernel.org, yoshikawa.takuya@oss.ntt.co.jp
Subject: Re: [PATCH v2] KVM: Avoid zapping unrelated shadows in __kvm_set_memory_region()
Date: Mon, 16 Apr 2012 15:35:19 +0300	[thread overview]
Message-ID: <4F8C1207.4040808@redhat.com> (raw)
In-Reply-To: <20120413213339.GB4190@amt.cnet>

On 04/14/2012 12:33 AM, Marcelo Tosatti wrote:
> mmio sptes are not related to any particular slot (by definition),
> i think you misunderstood the purpose of this flush. It handles
>
> 1) [start, end] gpa range unmapped.
> 2) mmio sptes are created that map this range.
> 3) a new slot is created. mmio sptes that map [start, end] range,
> which is now backed by new memslot should be removed.
>
> Perhaps there is an efficient way to clear all mmio sptes, or all
> mmio sptes pointing to [start, end] (instead of all sptes), here.

It shouldn't be too hard for direct maps.  For indirect maps, there is
now way to reach the spte, since we can't rmap mmio sptes.

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2012-04-16 12:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 13:05 [PATCH v2] KVM: Avoid zapping unrelated shadows in __kvm_set_memory_region() Takuya Yoshikawa
2012-04-11  3:11 ` Xiao Guangrong
2012-04-14  1:12   ` Takuya Yoshikawa
2012-04-16  3:53     ` Xiao Guangrong
2012-04-13 21:33 ` Marcelo Tosatti
2012-04-14  1:01   ` Takuya Yoshikawa
2012-04-16 12:35   ` Avi Kivity [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=4F8C1207.4040808@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 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.