From: mans@mansr•com (Måns Rullgård)
To: linux-arm-kernel@lists•infradead.org
Subject: ARM64: Disabling warnings about deprecated armv8 instructions
Date: Mon, 30 Jan 2017 16:38:15 +0000 [thread overview]
Message-ID: <yw1xwpdcfqq0.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <CAKv+Gu98i4=COqr_Eikwja28U5MAL83rxe-_QBXWFhJ7v1E6yA@mail.gmail.com> (Ard Biesheuvel's message of "Mon, 30 Jan 2017 14:50:23 +0000")
Ard Biesheuvel <ard.biesheuvel@linaro•org> writes:
> On 30 January 2017 at 14:13, Russell King - ARM Linux
> <linux@armlinux•org.uk> wrote:
>> On Sun, Jan 22, 2017 at 01:01:53PM +0000, Ard Biesheuvel wrote:
>>> Emulating unaligned access in the ARM kernel was a mistake: it even
>>> emulates unaligned accesses for instructions like ldm and ldrd, which
>>> require word alignment at the hardware level even in the latest v8
>>> version of the architecture. In contrast, the v8 deprecation warnings
>>> are about enforcing compliance.
>>
>> Ard, you're totally wrong on the unaligned access thing. Unaligned
>> accesses are a fundamental requirement of the kernel's networking
>> stack. If you don't have support for unaligned accesses, then you
>> don't have network support - it's as simple as that.
>>
>> So, in order for ARMv5 and earlier to have network support, there
>> was no option to add support for emulating those accesses.
>>
>
> I wasn't aware of that.
Not even David Miller is "aware" of that. Then again, we're living in a
world of "alternative facts" now.
--
M?ns Rullg?rd
next prev parent reply other threads:[~2017-01-30 16:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 8:07 ARM64: Disabling warnings about deprecated armv8 instructions Michael Zoran
2017-01-22 8:52 ` Alexander Stein
2017-01-22 8:58 ` Michael Zoran
2017-01-22 9:05 ` Jisheng Zhang
2017-01-22 9:38 ` Michael Zoran
2017-01-22 9:43 ` Ard Biesheuvel
2017-01-22 9:52 ` Michael Zoran
2017-01-22 9:56 ` Michael Zoran
2017-01-22 10:54 ` Ard Biesheuvel
2017-01-22 11:05 ` Michael Zoran
2017-01-22 11:22 ` Michael Zoran
2017-01-22 9:09 ` Ard Biesheuvel
2017-01-22 9:33 ` Michael Zoran
2017-01-22 9:36 ` Ard Biesheuvel
2017-01-22 9:49 ` Michael Zoran
2017-01-22 11:46 ` Alexander Stein
2017-01-22 12:21 ` Michael Zoran
2017-01-22 13:01 ` Ard Biesheuvel
2017-01-22 14:02 ` Michael Zoran
2017-01-22 15:05 ` Ard Biesheuvel
2017-01-30 14:13 ` Russell King - ARM Linux
2017-01-30 14:50 ` Ard Biesheuvel
2017-01-30 16:38 ` Måns Rullgård [this message]
2017-01-30 16:58 ` Russell King - ARM Linux
2017-01-30 17:09 ` Ard Biesheuvel
2017-01-30 17:39 ` Eric Anholt
2017-01-30 17:41 ` Michael Zoran
2017-01-30 18:17 ` Måns Rullgård
2017-01-30 18:34 ` Michael Zoran
2017-01-30 18:49 ` Will Deacon
2017-01-30 19:53 ` Michael Zoran
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=yw1xwpdcfqq0.fsf@unicorn.mansr.com \
--to=mans@mansr$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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