From: David Daney <ddaney.cavm@gmail.com>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [RFC PATCH v5 2/2] MIPS: optional floating point support
Date: Mon, 07 Apr 2014 11:10:36 -0700 [thread overview]
Message-ID: <5342EA1C.3010605@gmail.com> (raw)
In-Reply-To: <1396893214-298664-2-git-send-email-manuel.lauss@gmail.com>
On 04/07/2014 10:53 AM, Manuel Lauss wrote:
[...]
> +#else /* no CONFIG_MIPS_FPU_SUPPORT */
> +static inline int do_dsemulret(struct pt_regs *xcp)
> +{
> + return 0; /* 0 means error, should never get here anyway */
> +}
> +
> +static inline int fpu_emulator_cop1Handler(struct pt_regs *xcp,
> + struct mips_fpu_struct *ctx, int has_fpu,
> + void *__user *fault_addr)
> +{
> + return SIGILL; /* we don't speak MIPS FPU */
In a message in the other branch, Ralf suggested emitting very ugly
messages in the case that something tries to use the FPU.
This code doesn't quite satisfy that request.
> +}
> +#endif /* CONFIG_MIPS_FPU_SUPPORT */
> +
> int process_fpemu_return(int sig, void __user *fault_addr);
>
> /*
>
prev parent reply other threads:[~2014-04-07 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 17:53 [RFC PATCH v5 1/2] MIPS: move mmips branch support code out of the fpu emu code Manuel Lauss
2014-04-07 17:53 ` [RFC PATCH v5 2/2] MIPS: optional floating point support Manuel Lauss
2014-04-07 18:10 ` David Daney [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=5342EA1C.3010605@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
/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