From: Marcelo Tosatti <marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] Use cmpxchg for pte updates on walk_addr()
Date: Fri, 7 Dec 2007 17:47:18 -0500 [thread overview]
Message-ID: <20071207224718.GA31752@dmt> (raw)
In-Reply-To: <4758D4D2.8090208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Fri, Dec 07, 2007 at 07:06:26AM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >Right, patch at end of the message restarts the process if the pte
> >changes under the walker. The goto is pretty ugly, but I fail to see any
> >elegant way of doing that. Ideas?
> >
> >
>
> goto is fine for that. But there's a subtle livelock here: suppose vcpu
> 0 is in guest mode with continuously updating a memory location. vcpu 1
> is faulting with that memory location acting as a pte. While we're in
> kernel mode, we aren't responding to signals like we should; so we need
> to abort the walk and let the guest retry; that way we go through the
> signal_pending() check.
>
> However, this is an intrusive change, so let's start with the goto and
> drop it later in favor or an abort.
>
> >>>@@ -1510,6 +1510,9 @@ static int emulator_write_phys(struct kvm_vcpu
> >>>*vcpu, gpa_t gpa,
> >>> {
> >>> int ret;
> >>>
> >>>+ /* No need for kvm_cmpxchg_guest_pte here, its the guest
> >>>+ * responsability to synchronize pte updates and page faults.
> >>>+ */
> >>> ret = kvm_write_guest(vcpu->kvm, gpa, val, bytes);
> >>> if (ret < 0)
> >>> return 0;
> >>>
> >>Hmm. What if an i386 pae guest carefully uses cmpxchg8b to atomically
> >>set a pte? kvm_write_guest() doesn't guarantee atomicity, so an
> >>intended atomic write can be seen splitted by the guest walker doing a
> >>concurrent walk.
> >>
> >
> >True, an atomic write is needed... a separate patch for that seems more
> >appropriate.
> >
> >
> >
>
> Yes.
Hi Avi,
How about the following
diff --git a/drivers/kvm/x86.c b/drivers/kvm/x86.c
index c70ac33..8678651 100644
--- a/drivers/kvm/x86.c
+++ b/drivers/kvm/x86.c
@@ -25,6 +25,7 @@
#include <linux/vmalloc.h>
#include <linux/module.h>
#include <linux/mman.h>
+#include <linux/highmem.h>
#include <asm/uaccess.h>
#include <asm/msr.h>
@@ -1589,6 +1590,34 @@ static int emulator_cmpxchg_emulated(unsigned long addr,
reported = 1;
printk(KERN_WARNING "kvm: emulating exchange as write\n");
}
+
+ /* guests cmpxchg8b have to be emulated atomically */
+ if (bytes == 8) {
+ gpa_t gpa = vcpu->mmu.gva_to_gpa(vcpu, addr);
+ struct page *page;
+ char *addr;
+ u64 *val;
+
+ if (gpa == UNMAPPED_GVA ||
+ (gpa & PAGE_MASK) == APIC_DEFAULT_PHYS_BASE)
+ goto emul_write;
+
+ val = (u64 *)new;
+ page = gfn_to_page(vcpu->kvm, gpa >> PAGE_SHIFT);
+ addr = kmap_atomic(page, KM_USER0);
+ addr += offset_in_page(gpa);
+
+#ifdef CONFIG_X86_64
+ set_64bit((unsigned long *)addr, *val);
+#else
+ set_64bit((unsigned long long *)addr, *val);
+#endif
+ kunmap_atomic(page, KM_USER0);
+ kvm_release_page_dirty(page);
+
+ }
+
+emul_write:
return emulator_write_emulated(addr, new, bytes, vcpu);
}
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
next prev parent reply other threads:[~2007-12-07 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 15:04 [PATCH] Use cmpxchg for pte updates on walk_addr() Marcelo Tosatti
2007-12-06 15:24 ` Avi Kivity
[not found] ` <47581418.8000506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-07 2:32 ` Marcelo Tosatti
2007-12-07 5:06 ` Avi Kivity
[not found] ` <4758D4D2.8090208-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-07 12:56 ` Marcelo Tosatti
2007-12-07 17:54 ` Andrea Arcangeli
2007-12-09 8:38 ` Avi Kivity
2007-12-07 22:47 ` Marcelo Tosatti [this message]
2007-12-09 8:47 ` Avi Kivity
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=20071207224718.GA31752@dmt \
--to=marcelo-bw31mazkks3ytjvyw6ydsg@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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