All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 0/5] MIPS: FP cleanup & no-FP support
Date: Fri, 16 Jun 2017 03:55:26 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1706160348450.23046@tp.orcam.me.uk> (raw)
In-Reply-To: <20170605182131.16853-1-paul.burton@imgtec.com>

On Mon, 5 Jun 2017, Paul Burton wrote:

> This series tidies up support for floating point a little, then
> introduces support for disabling it via Kconfig. The end result is that
> it becomes possible to compile a kernel which does not include any
> support for userland which makes use of floating point instructions -
> meaning that it never enables an FPU & does not include the FPU
> emulator. The benefit of this is that if you know your userland code
> will not use FP instructions then you can shrink the kernel by around
> 65KiB.
> 
> Applies atop v4.12-rc4.
> 
> Paul Burton (5):
>   MIPS: Remove unused R6000 support
>   MIPS: Move r4k FP code from r4k_switch.S to r4k_fpu.S
>   MIPS: Move r2300 FP code from r2300_switch.S to r2300_fpu.S
>   MIPS: Remove unused ST_OFF from r2300_switch.S
>   MIPS: Allow floating point support to be disabled

 Doesn't ptrace(2) require suitable updates for requests that deal with 
the FP context?  Preferably along with the last change (or maybe ahead of 
it) so that we don't have a kernel revision that presents rubbish to the 
userland (of course tools like GDB will have to be updated accordingly to 
cope, but that's out of scope for Linux itself).

 Also how about those prctl(2) calls that also operate on FP state?

  Maciej

WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 0/5] MIPS: FP cleanup & no-FP support
Date: Fri, 16 Jun 2017 03:55:26 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1706160348450.23046@tp.orcam.me.uk> (raw)
Message-ID: <20170616025526.KprdH_32tYmrmR3P-6_ZOm_pqopKYuGWdmq5oi1R8fQ@z> (raw)
In-Reply-To: <20170605182131.16853-1-paul.burton@imgtec.com>

On Mon, 5 Jun 2017, Paul Burton wrote:

> This series tidies up support for floating point a little, then
> introduces support for disabling it via Kconfig. The end result is that
> it becomes possible to compile a kernel which does not include any
> support for userland which makes use of floating point instructions -
> meaning that it never enables an FPU & does not include the FPU
> emulator. The benefit of this is that if you know your userland code
> will not use FP instructions then you can shrink the kernel by around
> 65KiB.
> 
> Applies atop v4.12-rc4.
> 
> Paul Burton (5):
>   MIPS: Remove unused R6000 support
>   MIPS: Move r4k FP code from r4k_switch.S to r4k_fpu.S
>   MIPS: Move r2300 FP code from r2300_switch.S to r2300_fpu.S
>   MIPS: Remove unused ST_OFF from r2300_switch.S
>   MIPS: Allow floating point support to be disabled

 Doesn't ptrace(2) require suitable updates for requests that deal with 
the FP context?  Preferably along with the last change (or maybe ahead of 
it) so that we don't have a kernel revision that presents rubbish to the 
userland (of course tools like GDB will have to be updated accordingly to 
cope, but that's out of scope for Linux itself).

 Also how about those prctl(2) calls that also operate on FP state?

  Maciej

  parent reply	other threads:[~2017-06-16  2:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 18:21 [PATCH 0/5] MIPS: FP cleanup & no-FP support Paul Burton
2017-06-05 18:21 ` Paul Burton
2017-06-05 18:21 ` [PATCH 1/5] MIPS: Remove unused R6000 support Paul Burton
2017-06-05 18:21   ` Paul Burton
2017-06-05 18:21 ` [PATCH 2/5] MIPS: Move r4k FP code from r4k_switch.S to r4k_fpu.S Paul Burton
2017-06-05 18:21   ` Paul Burton
2017-06-05 18:21 ` [PATCH 3/5] MIPS: Move r2300 FP code from r2300_switch.S to r2300_fpu.S Paul Burton
2017-06-05 18:21   ` Paul Burton
2017-06-05 18:21 ` [PATCH 4/5] MIPS: Remove unused ST_OFF from r2300_switch.S Paul Burton
2017-06-05 18:21   ` Paul Burton
2017-06-05 18:21 ` [PATCH 5/5] MIPS: Allow floating point support to be disabled Paul Burton
2017-06-05 18:21   ` Paul Burton
2017-06-16  2:55 ` Maciej W. Rozycki [this message]
2017-06-16  2:55   ` [PATCH 0/5] MIPS: FP cleanup & no-FP support Maciej W. Rozycki
2017-06-16 16:49   ` Paul Burton
2017-06-16 16:49     ` Paul Burton
2017-06-16 19:50     ` Maciej W. Rozycki
2017-06-16 19:50       ` Maciej W. Rozycki
2017-06-16 20:21       ` [PATCH v2 5/5] MIPS: Allow floating point support to be disabled Paul Burton
2017-06-16 20:21         ` Paul Burton
2017-08-07  9:41         ` Ralf Baechle
2017-08-10  8:46           ` Maciej W. Rozycki
2017-08-10  8:46             ` Maciej W. Rozycki

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=alpine.DEB.2.00.1706160348450.23046@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.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.