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: Tue, 25 Aug 2015 10:36:40 +0200 [thread overview]
Message-ID: <20150825083639.GA21022@gmail.com> (raw)
In-Reply-To: <55DB26F5.1090805@redhat.com>
* Denys Vlasenko <dvlasenk@redhat.com> wrote:
> On 08/24/2015 08:50 AM, Ingo Molnar wrote:
> >
> > * Ingo Molnar <mingo@kernel.org> wrote:
> >
> >>
> >> * Denys Vlasenko <dvlasenk@redhat.com> wrote:
> >>
> >>> I propose the table to be commented like shown below:
> >>>
> >>> /*Opcode: d8 d9 da db dc dd de df */
> >>> /*c0..f*/ 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__,
> >>
> >> I agree with that, but please fix the vertical alignment (like my patch did), as
> >> the table is pretty hard to navigate in this form.
> >
> > and by that I mean to split each line into two, to have groups of 4 instructions
> > and enough tabs between them.
>
> How would you want it? Like this?
>
> /*Opcode: d8 d9 da db */
> /* dc dd de df */
> /*c0..f*/ fadd__, fld_i_, fcmovb, fcmovnb,
> /*c0..f*/ fadd_i, ffree_, faddp_, _df_c0_,
> /*c8..f*/ fmul__, fxch_i, fcmove, fcmovne,
> /*c8..f*/ fmul_i, _dd_c8_, fmulp_, _df_c8_,
> /*d0..7*/ fcom_st, fp_nop, fcmovbe, fcmovnbe,
> /*d0..7*/ _dc_d0_, fst_i_, _de_d0_, _df_d0_,
> /*d8..f*/ fcompst, _d9_d8_, fcmovu, fcmovnu,
> /*d8..f*/ _dc_d8_, fstp_i, fcompp, _df_d8_,
> /*e0..7*/ fsub__, FPU_etc, __BAD__, finit_,
> /*e0..7*/ fsubri, fucom_, fsubrp, fstsw_,
> /*e8..f*/ fsubr_, fconst, fucompp, fucomi_,
> /*e8..f*/ fsub_i, fucomp, fsubp_, fucomip,
> /*f0..7*/ fdiv__, FPU_triga, __BAD__, fcomi_,
> /*f0..7*/ fdivri, __BAD__, fdivrp, fcomip,
> /*f8..f*/ fdivr_, FPU_trigb, __BAD__, __BAD__,
> /*f8..f*/ fdiv_i, __BAD__, fdivp_, __BAD__,
Yeah, although we could afford a few more tabs and spaces to make it less
claustrophobic, right?
Something like this:
/* c0..f */ fadd__, fld_i_, fcmovb, fcmovnb,
/* c0..f */ fadd_i, ffree_, faddp_, _df_c0_,
/* c8..f */ fmul__, fxch_i, fcmove, fcmovne,
/* c8..f */ fmul_i, _dd_c8_, fmulp_, _df_c8_,
/* d0..7 */ fcom_st, fp_nop, fcmovbe, fcmovnbe,
/* d0..7 */ _dc_d0_, fst_i_, _de_d0_, _df_d0_,
/* d8..f */ fcompst, _d9_d8_ fcmovu, fcmovnu,
/* d8..f */ _dc_d8_, fstp_i, fcompp, _df_d8_,
/* e0..7 */ fsub__, FPU_etc, __BAD__, finit_,
/* e0..7 */ fsubri, fucom_, fsubrp, fstsw_,
/* e8..f */ fsubr_, fconst, fucompp, fucomi_,
/* e8..f */ fsub_i, fucomp, fsubp_, fucomip,
/* f0..7 */ fdiv__, FPU_triga, __BAD__, fcomi_,
/* f0..7 */ fdivri, __BAD__, fdivrp, fcomip,
/* f8..f */ fdivr_, FPU_trigb, __BAD__, __BAD__,
/* f8..f */ fdiv_i, __BAD__, fdivp_, __BAD__,
looks pretty good to me.
Thanks,
Ingo
prev parent reply other threads:[~2015-08-25 8:36 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
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 [this message]
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=20150825083639.GA21022@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