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] emulated cmpxchg8b should be atomic on i386
Date: Wed, 12 Dec 2007 10:46:12 -0500 [thread overview]
Message-ID: <20071212154612.GA1674@dmt> (raw)
In-Reply-To: <475DAFE3.30501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, Dec 10, 2007 at 11:30:11PM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
> >Emulate cmpxchg8b atomically on i386. This is required to avoid a guest
> >pte walker from seeing a splitted write.
> >
> >Signed-off-by: Marcelo Tosatti <mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> >
> >diff --git a/drivers/kvm/x86.c b/drivers/kvm/x86.c
> >index 9db4e32..d58d795 100644
> >--- a/drivers/kvm/x86.c
> >+++ b/drivers/kvm/x86.c
> >@@ -1674,6 +1674,33 @@ static int emulator_cmpxchg_emulated(uns
> > reported = 1;
> > printk(KERN_WARNING "kvm: emulating exchange as write\n");
> > }
> >+#ifndef CONFIG_X86_64
> >+ /* 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(page, gpa >> PAGE_SHIFT);
> >+ addr = kmap_atomic(page, KM_USER0);
> >+ addr += offset_in_page(gpa);
> >+
> >+ set_64bit((unsigned long long *)addr, val);
> >+
> >+ kunmap_atomic(page, KM_USER0);
> >+ kvm_release_page_dirty(page);
> >+
> >+ return X86EMUL_CONTINUE;
> >+ }
> >+#endif
> >+
> >+emul_write:
> > return emulator_write_emulated(addr, new, bytes, vcpu);
> > }
> >
>
> Won't the compiler complain when it sees an unreferenced label?
>
> Also, we should handle the page boundary crossing case (probably by just
> emulating as a write and crosssing fingers).
Pagetable writes should not cross page boundaries, so that should be fine.
------------------
Emulate cmpxchg8b atomically on i386. This is required to avoid a guest
pte walker from seeing a splitted write.
Signed-off-by: Marcelo Tosatti <mtosatti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
diff --git a/drivers/kvm/x86.c b/drivers/kvm/x86.c
index 9db4e32..e37c19d 100644
--- a/drivers/kvm/x86.c
+++ b/drivers/kvm/x86.c
@@ -1674,6 +1674,33 @@ static int emulator_cmpxchg_emulated(uns
reported = 1;
printk(KERN_WARNING "kvm: emulating exchange as write\n");
}
+#ifndef CONFIG_X86_64
+ /* 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;
+
+ if (((addr + bytes - 1) & PAGE_MASK) != (addr & PAGE_MASK))
+ goto emul_write;
+
+ val = (u64 *)new;
+ page = gfn_to_page(page, gpa >> PAGE_SHIFT);
+ addr = kmap_atomic(page, KM_USER0);
+ addr += offset_in_page(gpa);
+
+ set_64bit((unsigned long long *)addr, val);
+ kunmap_atomic(page, KM_USER0);
+ kvm_release_page_dirty(page);
+ }
+emul_write:
+#endif
+
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-12 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 20:31 [PATCH] emulated cmpxchg8b should be atomic on i386 Marcelo Tosatti
2007-12-10 21:30 ` Avi Kivity
[not found] ` <475DAFE3.30501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-12 15:46 ` Marcelo Tosatti [this message]
2007-12-13 9:02 ` 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=20071212154612.GA1674@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