linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Wookey <wookey@wookware.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	arnd@arndb.de, will@kernel.org, mark.rutland@arm.com,
	maz@kernel.org, broonie@kernel.org, debian-arm@lists.debian.org,
	Vagrant Cascadian <vagrant@debian.org>,
	Riku Voipio <riku.voipio@iki.fi>,
	Steve McIntyre <steve@einval.com>
Subject: Re: [PATCH v2] arm64: compat: Implement misalignment fixups for multiword loads
Date: Thu, 14 Jul 2022 02:52:15 +0100	[thread overview]
Message-ID: <20220714015214.GP27816@mail.wookware.org> (raw)
In-Reply-To: <20220701135322.3025321-1-ardb@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 1485 bytes --]

On 2022-07-01 15:53 +0200, Ard Biesheuvel wrote:
> The 32-bit ARM kernel implements fixups on behalf of user space when
> using LDM/STM or LDRD/STRD instructions on addresses that are not 32-bit
> aligned.

> This feature is one of the remaining impediments to being able to switch
> to 64-bit kernels on 64-bit capable hardware running 32-bit user space,
> so let's implement it for the arm64 compat layer as well.
 
> Note to cc'ees: if this is something you would like to see merged,
> please indicate so. This stuff is unlikely to get in if there are no
> users.

Decent 32-bit arm hardware is thin on the ground these days. Debian
still has some but it's getting old and flaky. Being able to build
reliably on 64-bit hardware is important and useful. Unaligned
accesses are much less of a problem than they used to be, but they can
still happen, so having these fixups available is definitely a good
thing.

Debian runs its 32-bit buildds with alignment fixups turned on. It
looks like the boxes still hit about 1 per day.

We also do 32 bit builds on 64-bit kernels (in 32-bit userspaces) and
it mostly works. We do have packages that fail on 64-bit kernels and
have to be built on real 32-bit hardware, but I don't know how much of
that would be fixed by this patch. Some, presumably.

So yes, cheers for this. It is helpful in the real world (or at least
it should be).

Wookey
-- 
Principal hats:  Debian, Wookware, ARM
http://wookware.org/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-07-14  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 13:53 [PATCH v2] arm64: compat: Implement misalignment fixups for multiword loads Ard Biesheuvel
2022-07-01 14:04 ` Arnd Bergmann
2022-07-14  1:52 ` Wookey [this message]
2022-08-16 19:28   ` Aurelien Jarno
2022-08-16 20:29     ` Ard Biesheuvel
2022-08-17  9:47       ` Arnd Bergmann
2022-08-31 17:06 ` Catalin Marinas
2022-09-05 10:04   ` Ard Biesheuvel
2022-09-05 11:31     ` Catalin Marinas
2022-09-06 17:45 ` Catalin Marinas

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=20220714015214.GP27816@mail.wookware.org \
    --to=wookey@wookware.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=debian-arm@lists.debian.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=riku.voipio@iki.fi \
    --cc=steve@einval.com \
    --cc=vagrant@debian.org \
    --cc=will@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).