From: Dmitry Osipenko <digetx@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Ingo Molnar <mingo@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1] ARM: vfp: Use long jump to fix THUMB2 kernel compilation error
Date: Tue, 10 Nov 2020 10:44:14 +0300 [thread overview]
Message-ID: <a438f99d-26a4-a1b5-9fc3-5abd2e76edb3@gmail.com> (raw)
In-Reply-To: <CAMj1kXEJL31KOMs7h_XzxFKXgqi2jOXCmLaxfKwW=wgo2so_RA@mail.gmail.com>
09.11.2020 10:25, Ard Biesheuvel пишет:
...
>>> So the options are
>>>
>>> a) merge my patch that adds 2 bytes of opcode to the Thumb2 build
>>> b) merge Dmitry's patch that adds an unconditional literal load to all builds
>>> c) remove kernel mode handling from vfp_support_entry() [my other patch]
>>> d) move sections around so that vfp_kmode_exception is guaranteed to
>>> be in range.
>>> e) do nothing
...
>> The performance argument is questionable to me, to be honest. In
>> practice the performance difference should be absolutely negligible for
>> either of the proposed options, it should stay in a noise even if
>> somebody thoroughly counting cycles, IMO.
>>
>> I'm still thinking that the best option will be to apply a).
>>
>
> Can we take that as an acked-by?
Are you asking me for the ack? I think this is a more appropriate
question to Russel. I'm not arm/ maintainer, but could give r-b and t-b.
If you're going to follow approach that I'm suggesting with a) + d),
then could you please resend the two patches in a single series? The
first one-line patch-fix should contain the fixes tag.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-10 7:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 22:57 [PATCH v1] ARM: vfp: Use long jump to fix THUMB2 kernel compilation error Dmitry Osipenko
2020-10-21 23:40 ` Kees Cook
2020-10-22 0:00 ` Dmitry Osipenko
2020-10-22 3:28 ` Kees Cook
2020-10-22 7:06 ` Ard Biesheuvel
2020-10-22 15:57 ` Dmitry Osipenko
2020-10-22 16:06 ` Ard Biesheuvel
2020-10-22 16:11 ` Russell King - ARM Linux admin
2020-10-22 16:20 ` Ard Biesheuvel
2020-10-22 16:23 ` Russell King - ARM Linux admin
2020-10-22 16:33 ` Ard Biesheuvel
2020-10-22 17:48 ` Russell King - ARM Linux admin
2020-10-22 17:59 ` Ard Biesheuvel
2020-10-26 8:58 ` Ard Biesheuvel
2020-10-29 9:56 ` Ard Biesheuvel
2020-11-03 7:24 ` Ard Biesheuvel
2020-11-03 8:43 ` Dmitry Osipenko
2020-11-09 7:25 ` Ard Biesheuvel
2020-11-10 7:44 ` Dmitry Osipenko [this message]
2020-11-10 7:45 ` Ard Biesheuvel
2020-10-22 16:34 ` Dmitry Osipenko
2020-10-22 17:38 ` Russell King - ARM Linux admin
2020-10-22 17:47 ` Ard Biesheuvel
2020-10-22 17:50 ` Russell King - ARM Linux admin
2020-10-22 17:51 ` Ard Biesheuvel
2020-10-22 19:05 ` Dmitry Osipenko
2020-10-22 14:57 ` Russell King - ARM Linux admin
2020-10-22 15:56 ` Dmitry Osipenko
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=a438f99d-26a4-a1b5-9fc3-5abd2e76edb3@gmail.com \
--to=digetx@gmail.com \
--cc=ardb@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).