From: Xiao Guangrong Subject: Re: [kvm-unit-test RFC] x86: Memory instructions test case Date: Thu, 5 Nov 2015 11:32:29 +0800 Message-ID: <563ACDCD.7050404@linux.intel.com> References: <1446672079-8549-1-git-send-email-ehabkost@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Paolo Bonzini , kvm@vger.kernel.org, Richard Henderson To: Eduardo Habkost , qemu-devel@nongnu.org Return-path: In-Reply-To: <1446672079-8549-1-git-send-email-ehabkost@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org 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