From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [kvm-unit-test RFC] x86: Memory instructions test case
Date: Thu, 5 Nov 2015 11:32:29 +0800 [thread overview]
Message-ID: <563ACDCD.7050404@linux.intel.com> (raw)
In-Reply-To: <1446672079-8549-1-git-send-email-ehabkost@redhat.com>
On 11/05/2015 05:21 AM, Eduardo Habkost wrote:
> Quickly hacked test case for memory instructions (clflush, mfence,
> sfence, lfence, clflushopt, clwb, pcommit), that simply checks for #UD
> exceptions.
>
> This was useful to test TCG handling of those instructions.
>
> The "fake clwb" part will probably break once a new instruction use
> those opcodes.
Tested it on the box on that these instruction are available, it worked.
Tested-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [kvm-unit-test RFC] x86: Memory instructions test case
Date: Thu, 5 Nov 2015 11:32:29 +0800 [thread overview]
Message-ID: <563ACDCD.7050404@linux.intel.com> (raw)
In-Reply-To: <1446672079-8549-1-git-send-email-ehabkost@redhat.com>
On 11/05/2015 05:21 AM, Eduardo Habkost wrote:
> Quickly hacked test case for memory instructions (clflush, mfence,
> sfence, lfence, clflushopt, clwb, pcommit), that simply checks for #UD
> exceptions.
>
> This was useful to test TCG handling of those instructions.
>
> The "fake clwb" part will probably break once a new instruction use
> those opcodes.
Tested it on the box on that these instruction are available, it worked.
Tested-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
next prev parent reply other threads:[~2015-11-05 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 21:21 [kvm-unit-test RFC] x86: Memory instructions test case Eduardo Habkost
2015-11-04 21:21 ` [Qemu-devel] " Eduardo Habkost
2015-11-05 3:32 ` Xiao Guangrong [this message]
2015-11-05 3:32 ` Xiao Guangrong
2015-11-18 11:23 ` Paolo Bonzini
2015-11-18 11:23 ` [Qemu-devel] " Paolo Bonzini
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=563ACDCD.7050404@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.