From: Wei Huang <wei.huang2@amd.com>
To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: [PATCH] clflush instruction emulation
Date: Thu, 15 Apr 2010 11:38:21 -0500 [thread overview]
Message-ID: <4BC740FD.5090502@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
We recently found that FreeBSD 8.0 guest failed to install and boot on
Xen. The reason was that FreeBSD detected clflush feature and invoked
this instruction to flush MMIO space. This caused a page fault; but
x86_emulate.c failed to emulate this instruction (not supported). As a
result, a page fault was detected inside FreeBSD. A similar issue was
reported earlier.
http://lists.xensource.com/archives/html/xen-devel/2010-03/msg00362.html
I created a patch which enables clflush emulation. I have verified that
this patch solves FreeBSD issue. This patch returns immediately without
doing anything. Note that we don't have to intercept clflush in SVM. So
the only time we have page_fault for clflush instruction is when guest
VM flushes MMIO space. In this case, do we need to send this command
over to QEMU? I didn't do it in this patch anyway.
Best,
-Wei
[-- Attachment #2: xen_clflush_emul.txt --]
[-- Type: text/plain, Size: 1023 bytes --]
diff -r 12a610b600b0 xen/arch/x86/x86_emulate/x86_emulate.c
--- a/xen/arch/x86/x86_emulate/x86_emulate.c Wed Apr 14 11:50:00 2010 -0500
+++ b/xen/arch/x86/x86_emulate/x86_emulate.c Wed Apr 14 16:11:36 2010 -0500
@@ -227,7 +227,8 @@
DstMem|SrcReg|ModRM, DstMem|SrcReg|ModRM, 0, 0,
/* 0xA8 - 0xAF */
ImplicitOps, ImplicitOps, 0, DstBitBase|SrcReg|ModRM,
- DstMem|SrcReg|ModRM, DstMem|SrcReg|ModRM, 0, DstReg|SrcMem|ModRM,
+ DstMem|SrcReg|ModRM, DstMem|SrcReg|ModRM, DstMem|SrcReg|ModRM,
+ DstReg|SrcMem|ModRM,
/* 0xB0 - 0xB7 */
ByteOp|DstMem|SrcReg|ModRM, DstMem|SrcReg|ModRM,
DstReg|SrcMem|ModRM|Mov, DstBitBase|SrcReg|ModRM,
@@ -3948,6 +3949,11 @@
src.val = x86_seg_gs;
goto pop_seg;
+ case 0xae: /* clflush mem8 */
+ /* we don't need to do anything here */
+ rc = X86EMUL_OKAY;
+ break;
+
case 0xb0 ... 0xb1: /* cmpxchg */
/* Save real source value, then compare EAX against destination. */
src.orig_val = src.val;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-04-15 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 16:38 Wei Huang [this message]
2010-04-15 16:59 ` [PATCH] clflush instruction emulation Keir Fraser
2010-04-15 17:25 ` Wei Huang
2010-04-15 17:32 ` Keir Fraser
2010-04-15 17:49 ` Keir Fraser
2010-04-15 18:43 ` Huang2, Wei
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=4BC740FD.5090502@amd.com \
--to=wei.huang2@amd.com \
--cc=xen-devel@lists.xensource.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.