From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 4/4] KVM: MMU: Reinstate pte prefetch on invlpg
Date: Tue, 16 Feb 2010 10:40:26 +0200 [thread overview]
Message-ID: <4B7A59FA.4020908@redhat.com> (raw)
In-Reply-To: <1266238109-30280-5-git-send-email-avi@redhat.com>
On 02/15/2010 02:48 PM, Avi Kivity wrote:
> Commit fb341f57 removed the pte prefetch on guest invlpg, citing guest races.
> However, the SDM is adamant that prefetch is allowed:
>
> "The processor may create entries in paging-structure caches for
> translations required for prefetches and for accesses that are a
> result of speculative execution that would never actually occur
> in the executed code path."
>
> And, in fact, there was a race in the prefetch code: we picked up the pte
> without the mmu lock held, so an older invlpg could install the pte over
> a newer invlpg.
>
> Reinstate the prefetch logic, but this time note whether another invlpg has
> executed using a counter. If a race occured, do not install the pte.
>
>
This patch is broken (UP windows XP won't start), I'm debugging it.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-16 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 12:48 [PATCH 0/4] Fix some mmu/emulator atomicity issues Avi Kivity
2010-02-15 12:48 ` [PATCH 1/4] KVM: MMU: Consolidate two guest pte reads in kvm_mmu_pte_write() Avi Kivity
2010-02-15 12:48 ` [PATCH 2/4] KVM: Make locked operations truly atomic Avi Kivity
2010-02-15 12:48 ` [PATCH 3/4] KVM: Don't follow an atmoic operation by a non-atomic one Avi Kivity
2010-02-15 12:48 ` [PATCH 4/4] KVM: MMU: Reinstate pte prefetch on invlpg Avi Kivity
2010-02-16 8:40 ` 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=4B7A59FA.4020908@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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.