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 1/2] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns
Date: Fri, 18 Sep 2015 09:33:57 +0200 [thread overview]
Message-ID: <20150918073357.GA2691@gmail.com> (raw)
In-Reply-To: <1442432914-27022-1-git-send-email-dvlasenk@redhat.com>
* Denys Vlasenko <dvlasenk@redhat.com> wrote:
> Run-tested by booting with "no387 nofxsr" and running test programs:
>
> # ./test_FCMOV
> [RUN] Testing fcmovCC instructions
> [OK] fcmovCC
> # ./test_FCOMI
> [RUN] Testing f[u]comi[p] instructions
> [OK] f[u]comi[p]
>
> Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
> CC: Ingo Molnar <mingo@kernel.org>
> CC: Borislav Petkov <bp@alien8.de>
> CC: "H. Peter Anvin" <hpa@zytor.com>
> CC: Andy Lutomirski <luto@amacapital.net>
> CC: Kees Cook <keescook@chromium.org>
> CC: x86@kernel.org
> CC: linux-kernel@vger.kernel.org
> ---
>
> The patches did not change since last submission.
> The difference, now they are run-tested.
>
> arch/x86/math-emu/fpu_aux.c | 70 ++++++++++++++++++++++
> arch/x86/math-emu/fpu_entry.c | 49 +++++++++------
> arch/x86/math-emu/fpu_proto.h | 12 ++++
> arch/x86/math-emu/reg_compare.c | 128 ++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 241 insertions(+), 18 deletions(-)
I wanted to apply this patch, but noticed the following problem: why are two
instruction families added in a single patch?
Note that regressing math-emu for real is a real concern here: we start
interpreting real instructions. If anything breaks, and the failure isn't right at
the instruction that is buggy (but some time later), it would be nice which new
instruction causes the problem and make it all bisectable ...
So we should be finegrained and only add a single (family) of instructions in a
single patch. Please split this patch into two:
> +extern void fcmovb(void);
> +extern void fcmove(void);
> +extern void fcmovbe(void);
> +extern void fcmovu(void);
> +extern void fcmovnb(void);
> +extern void fcmovne(void);
> +extern void fcmovnbe(void);
> +extern void fcmovnu(void);
> extern void ffree_(void);
> extern void ffreep(void);
> extern void fst_i_(void);
> @@ -108,6 +116,10 @@ extern void fcompp(void);
> extern void fucom_(void);
> extern void fucomp(void);
> extern void fucompp(void);
> +extern void fcomi_(void);
> +extern void fcomip(void);
> +extern void fucomi_(void);
> +extern void fucomip(void);
Thanks,
Ingo
next prev parent reply other threads:[~2015-09-18 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 19:48 [PATCH 1/2] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns Denys Vlasenko
2015-09-16 19:48 ` [PATCH 2/2] x86/math-emu: Remove define layer for undocumented opcodes Denys Vlasenko
2015-09-18 7:36 ` Ingo Molnar
2015-09-16 19:51 ` [PATCH 1/2] x86/math-emu: Add support for FCMOVcc and F[U]COMI[P] insns Denys Vlasenko
2015-09-17 7:22 ` Ingo Molnar
2015-09-18 7:33 ` Ingo Molnar [this message]
2015-09-18 14:53 ` Denys Vlasenko
2015-09-20 8:13 ` 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=20150918073357.GA2691@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