All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Zhong <yang.zhong@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: yang.zhong@intel.com, andrew.cooper3@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v4 1/4] x86emul: Support GFNI insns
Date: Thu, 4 Jan 2018 17:20:56 +0800	[thread overview]
Message-ID: <20180104092056.GC11726@yangzhon-Virtual> (raw)
In-Reply-To: <5A4D1A53020000780019A9A6@prv-mh.provo.novell.com>

On Wed, Jan 03, 2018 at 10:00:51AM -0700, Jan Beulich wrote:
> >>> On 03.01.18 at 09:26, <yang.zhong@intel.com> wrote:
> > @@ -7741,6 +7752,16 @@ x86_emulate(
> >          op_bytes = 16;
> >          goto simd_0f3a_common;
> >  
> > +    case X86EMUL_OPC_66(0x0f3a, 0xce):     /* gf2p8affineqb $imm8,xmm/m128,xmm,xmm */
> > +    case X86EMUL_OPC_VEX_66(0x0f3a, 0xce): /* vgf2p8affineqb $imm8,{x,y}mm/mem,{x,y}mm,{x,y}mm */
> > +    case X86EMUL_OPC_66(0x0f3a, 0xcf):     /* gf2p8affineinvqb $imm8,xmm/m128,xmm,xmm */
> > +    case X86EMUL_OPC_VEX_66(0x0f3a, 0xcf): /* vgf2p8affineinvqb $imm8,{x,y}mm/mem,{x,y}mm,{x,y}mm */
> > +        host_and_vcpu_must_have(gfni);
> > +        if ( vex.opcx == vex_none )
> > +            goto simd_0f3a_common;
> > +        generate_exception_if(vex.w, EXC_UD);
> 
> The documentation says .W1, but I of course don't know whether
> you meanwhile tested your code (you still don't add a test case)
> and the doc is wrong, or this needs to be !vex.w.
>
  Thanks Jan pointed out this issue, you are right!

  vgf2p8affineqb and vgf2p8affineinvqb are W1, but vgf2p8mulb is W0.

  So, for vgf2p8affineqb and vgf2p8affineinvqb, !vex.w is right.
  for vgf2p8mulb vex.w is right.

  As for the test case for those insns, i am writing those related test cases in tools/tests/x86_emulator.

  How many test cases will you need ? One test case for one CPU feature(vaes,gfni and vpclmulqdq)?

  Another issue is would you please share your test guide? i will verify those insns on my simics enviornment.

  thanks a lot!

  Yang
 
> Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-01-04  9:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03  8:26 [PATCH v4 0/4] x86/cpuid: enable new cpu features Yang Zhong
2018-01-03  8:26 ` [PATCH v4 1/4] x86emul: Support GFNI insns Yang Zhong
2018-01-03 17:00   ` Jan Beulich
2018-01-04  9:20     ` Yang Zhong [this message]
2018-01-04 11:02       ` Jan Beulich
2018-01-03  8:26 ` [PATCH v4 2/4] x86emul: Support vpclmulqdq Yang Zhong
2018-01-18 14:05   ` Jan Beulich
2018-01-03  8:26 ` [PATCH v4 3/4] x86emul: Support vaes insns Yang Zhong
2018-01-18 14:13   ` Jan Beulich
2018-01-23 12:56     ` Yang Zhong
2018-01-23 13:27       ` Jan Beulich
2018-01-03  8:26 ` [PATCH v4 4/4] x86/cpuid: Enable new SSE/AVX/AVX512 cpu features Yang Zhong
2018-01-03  8:46   ` Jan Beulich
2018-01-04  6:06     ` Yang Zhong
     [not found] ` <5A4CA485020000780019A5DD@prv-mh.provo.novell.com>
2018-01-04  6:08   ` [PATCH v4 0/4] x86/cpuid: enable new " Yang Zhong

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=20180104092056.GC11726@yangzhon-Virtual \
    --to=yang.zhong@intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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 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.