public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Kees Cook <keescook@chromium.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns
Date: Sun, 23 Aug 2015 08:15:17 +0200	[thread overview]
Message-ID: <20150823061517.GA18134@gmail.com> (raw)
In-Reply-To: <55D8C61B.3010902@redhat.com>


* Denys Vlasenko <dvlasenk@redhat.com> wrote:

> >  static FUNC const st_instr_table[64] = {
> > -	fadd__,  fld_i_,  fcmovb,   fcmovnb,  fadd_i,  ffree_,  faddp_,  _df_c0_,
> > -	fmul__,  fxch_i,  fcmove,   fcmovne,  fmul_i,  _dd_c8_, fmulp_,  _df_c8_,
> > -	fcom_st, fp_nop,  fcmovbe,  fcmovnbe, _dc_d0_, fst_i_,  _de_d0_, _df_d0_,
> > -	fcompst, _d9_d8_, fcmovu,   fcmovnu,  _dc_d8_, fstp_i,  fcompp,  _df_d8_,
> > -	fsub__, FPU_etc, __BAD__, finit_, fsubri, fucom_, fsubrp, fstsw_,
> > -	fsubr_, fconst,   fucompp,  fucomi_,  fsub_i,  fucomp,  fsubp_,  fucomip,
> > -	fdiv__, FPU_triga, __BAD__, fcomi_,   fdivri,  __BAD__, fdivrp,  fcomip,
> > -	fdivr_, FPU_trigb, __BAD__, __BAD__, fdiv_i, __BAD__, fdivp_, __BAD__,
> > +/* 0x00 */	fadd__,		fld_i_,		fcmovb,		fcmovnb,
> > +/* 0x04 */	fadd_i,		ffree_,		faddp_,		_df_c0_,
> > +/* 0x08 */	fmul__,		fxch_i,		fcmove,		fcmovne,
> > +/* 0x0c */	fmul_i,		_dd_c8_,	fmulp_,		_df_c8_,
> > +/* 0x10 */	fcom_st,	fp_nop,		fcmovbe,	fcmovnbe,
> > +/* 0x14 */	_dc_d0_,	fst_i_,		_de_d0_,	_df_d0_,
> > +/* 0x18 */	fcompst,	_d9_d8_,	fcmovu,		fcmovnu,
> > +/* 0x1c */	_dc_d8_,	fstp_i,		fcompp,		_df_d8_,
> > +/* 0x20 */	fsub__,		FPU_etc,	__BAD__,	finit_,
> > +/* 0x24 */	fsubri,		fucom_,		fsubrp,		fstsw_,
> > +/* 0x28 */	fsubr_,		fconst,		fucompp,	fucomi_,
> > +/* 0x2c */	fsub_i,		fucomp,		fsubp_,		fucomip,
> > +/* 0x30 */	fdiv__,		FPU_triga,	__BAD__,	fcomi_,
> > +/* 0x34 */	fdivri,		__BAD__,	fdivrp,		fcomip,
> > +/* 0x38 */	fdivr_,		FPU_trigb,	__BAD__,	__BAD__,
> > +/* 0x3c */	fdiv_i,		__BAD__,	fdivp_,		__BAD__,
> 
> The numeric comments added at the left don't look correct.

Yeah, so they are correct for the purpose I used it: I simply wanted to index the 
table by its natural index: 'instr_idx', which is derived from the opcode.

But you are right that indexing it by the opcode is more useful for future 
extensions:

> In this table, each _column_ corresponds to one 0xd? opcode.
> Each row corresponds to a group of mod-reg-rm bytes
> with only "rm" field chnaging. (These insns act on registers,
> not memory, and "rm" value encodes register number, st(i).)
> 
> Something like this:
> 
> /*Opcode: d8      d9        da      db       dc      dd      de      df */
> /*c0..7*/ fadd__, fld_i_,   fcmovb, fcmovnb, fadd_i, ffree_, faddp_, _df_c0_,
> /*c8..f*/ fmul__, fxch_i,   fcmove, fcmovne, fmul_i, _dd_c8_,fmulp_, _df_c8_,
> /*d0..7*/ fcom_st,fp_nop,   fcmovbe,fcmovnbe,_dc_d0_,fst_i_, _de_d0_,_df_d0_,
> /*d8..f*/ fcompst,_d9_d8_,  fcmovu, fcmovnu, _dc_d8_,fstp_i, fcompp, _df_d8_,
> /*e0..7*/ fsub__, FPU_etc,  __BAD__,finit_,  fsubri, fucom_, fsubrp, fstsw_,
> /*e8..f*/ fsubr_, fconst,   fucompp,fucomi_, fsub_i, fucomp, fsubp_, fucomip,
> /*f0..7*/ fdiv__, FPU_triga,__BAD__,fcomi_,  fdivri, __BAD__,fdivrp, fcomip,
> /*f8..f*/ fdivr_, FPU_trigb,__BAD__,__BAD__, fdiv_i, __BAD__,fdivp_, __BAD__,

(Assuming you also do the table alignment improvements I did, the current format 
is pretty hard to navigate.)

> 
> 
> They should be:

Hm, your mail seems to have been cut off at this point.

Thanks,

	Ingo

  reply	other threads:[~2015-08-23  6:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 10:19 [PATCH] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns Denys Vlasenko
2015-08-22  8:13 ` Ingo Molnar
2015-08-22  8:54 ` Ingo Molnar
2015-08-22 18:57   ` Denys Vlasenko
2015-08-23  6:15     ` Ingo Molnar [this message]
2015-08-23 15:47       ` Denys Vlasenko
2015-08-24  6:46         ` Ingo Molnar
2015-08-24  6:50           ` Ingo Molnar
2015-08-24 14:15             ` Denys Vlasenko
2015-08-25  8:36               ` Ingo Molnar

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=20150823061517.GA18134@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=x86@kernel.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