stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] xtensa: limit offsets in __loop_cache_{all,page}
Date: Sat, 11 Aug 2018 13:50:35 +0200	[thread overview]
Message-ID: <20180811115035.GA444@kroah.com> (raw)
In-Reply-To: <20180811074405.4124-1-jcmvbkbc@gmail.com>

On Sat, Aug 11, 2018 at 12:44:05AM -0700, Max Filippov wrote:
> When building kernel for xtensa cores with big cache lines (e.g. 128
> bytes or more) __loop_cache_all and __loop_cache_page may generate
> assembly instructions with immediate fields that are too big. This
> results in the following build errors:
> 
>   arch/xtensa/mm/misc.S: Assembler messages:
>   arch/xtensa/mm/misc.S:464: Error: operand 2 of 'diwbi' has invalid value '256'
>   arch/xtensa/mm/misc.S:464: Error: operand 2 of 'diwbi' has invalid value '384'
>   arch/xtensa/kernel/head.S: Assembler messages:
>   arch/xtensa/kernel/head.S:172: Error: operand 2 of 'diu' has invalid value '256'
>   arch/xtensa/kernel/head.S:172: Error: operand 2 of 'diu' has invalid value '384'
>   arch/xtensa/kernel/head.S:176: Error: operand 2 of 'iiu' has invalid value '256'
>   arch/xtensa/kernel/head.S:176: Error: operand 2 of 'iiu' has invalid value '384'
>   arch/xtensa/kernel/head.S:255: Error: operand 2 of 'diwb' has invalid value '256'
>   arch/xtensa/kernel/head.S:255: Error: operand 2 of 'diwb' has invalid value '384'
> 
> Add parameter max_immed to these macros and use it to limit values of
> immediate operands. Extract common code of these macros into the new
> macro __loop_cache_unroll.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
>  arch/xtensa/include/asm/cacheasm.h | 65 +++++++++++++++++++++++---------------
>  1 file changed, 40 insertions(+), 25 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

      reply	other threads:[~2018-08-11 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11  7:44 [PATCH] xtensa: limit offsets in __loop_cache_{all,page} Max Filippov
2018-08-11 11:50 ` Greg KH [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=20180811115035.GA444@kroah.com \
    --to=greg@kroah.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).