All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Siarhei Volkau <lis8215@gmail.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mips@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Siarhei Volkau <lis8215@gmail.com>
Cc: Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH] MIPS: Take in account load hazards for HI/LO restoring
Date: Mon, 29 Apr 2024 09:42:11 +0300	[thread overview]
Message-ID: <CAKNVLfZnD+Yh5_dNUwUooCi72dxX7XO1den1oZf_rwtzk2Kckw@mail.gmail.com> (raw)
In-Reply-To: <20231012162027.3411684-1-lis8215@gmail.com>

Ping. The patch looks abandoned.

Paul, could you recommend right persons / lists for that ?

чт, 12 окт. 2023 г. в 19:21, Siarhei Volkau <lis8215@gmail.com>:
>
> MIPS CPUs usually have 1 to 4 cycles load hazards, thus doing load
> and right after move to HI/LO will usually stall the pipeline for
> significant amount of time. Let's take it into account and separate
> loads and mthi/lo in instruction sequence.
>
> The patch uses t6 and t7 registers as temporaries in addition to t8.
>
> The patch tries to deal with SmartMIPS, but I know little about and
> haven't tested it.
>
> Signed-off-by: Siarhei Volkau <lis8215@gmail.com>
> ---
>  arch/mips/include/asm/stackframe.h | 22 ++++++++++++----------
>  1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/arch/mips/include/asm/stackframe.h b/arch/mips/include/asm/stackframe.h
> index a8705aef47e1..3821d91b00fd 100644
> --- a/arch/mips/include/asm/stackframe.h
> +++ b/arch/mips/include/asm/stackframe.h
> @@ -308,17 +308,11 @@
>                 jal     octeon_mult_restore
>  #endif
>  #ifdef CONFIG_CPU_HAS_SMARTMIPS
> -               LONG_L  $24, PT_ACX(sp)
> -               mtlhx   $24
> -               LONG_L  $24, PT_HI(sp)
> -               mtlhx   $24
> -               LONG_L  $24, PT_LO(sp)
> -               mtlhx   $24
> -#elif !defined(CONFIG_CPU_MIPSR6)
> +               LONG_L  $14, PT_ACX(sp)
> +#endif
> +#if defined(CONFIG_CPU_HAS_SMARTMIPS) || !defined(CONFIG_CPU_MIPSR6)
>                 LONG_L  $24, PT_LO(sp)
> -               mtlo    $24
> -               LONG_L  $24, PT_HI(sp)
> -               mthi    $24
> +               LONG_L  $15, PT_HI(sp)
>  #endif
>  #ifdef CONFIG_32BIT
>                 cfi_ld  $8, PT_R8, \docfi
> @@ -327,6 +321,14 @@
>                 cfi_ld  $10, PT_R10, \docfi
>                 cfi_ld  $11, PT_R11, \docfi
>                 cfi_ld  $12, PT_R12, \docfi
> +#ifdef CONFIG_CPU_HAS_SMARTMIPS
> +               mtlhx   $14
> +               mtlhx   $15
> +               mtlhx   $24
> +#elif !defined(CONFIG_CPU_MIPSR6)
> +               mtlo    $24
> +               mthi    $15
> +#endif
>                 cfi_ld  $13, PT_R13, \docfi
>                 cfi_ld  $14, PT_R14, \docfi
>                 cfi_ld  $15, PT_R15, \docfi
> --
> 2.41.0
>

  reply	other threads:[~2024-04-29  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 16:20 [PATCH] MIPS: Take in account load hazards for HI/LO restoring Siarhei Volkau
2024-04-29  6:42 ` Siarhei Volkau [this message]
2024-04-29  8:18 ` Thomas Bogendoerfer
2024-04-29  8:30   ` Thomas Bogendoerfer

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=CAKNVLfZnD+Yh5_dNUwUooCi72dxX7XO1den1oZf_rwtzk2Kckw@mail.gmail.com \
    --to=lis8215@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=tsbogend@alpha.franken.de \
    /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.