From: Andreas Schwab <schwab@linux-m68k.org>
To: Eero Tamminen <oak@helsinkinet.fi>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@vger.kernel.org, Finn Thain <fthain@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH RFC] m68k: Handle __generic_copy_to_user faults more carefully
Date: Wed, 17 Apr 2024 18:26:49 +0200 [thread overview]
Message-ID: <87bk68gdkm.fsf@igel.home> (raw)
In-Reply-To: <71553982-6353-4786-9d12-fb83ea1b87a7@helsinkinet.fi> (Eero Tamminen's message of "Wed, 17 Apr 2024 11:16:57 +0300")
On Apr 17 2024, Eero Tamminen wrote:
> But is that valid also across page boundaries?
Yes, the cpu will split misaligned accesses into sequences of aligned
accesses.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2024-04-17 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:36 [PATCH RFC] m68k: Handle __generic_copy_to_user faults more carefully Michael Schmitz
2024-04-17 6:59 ` Geert Uytterhoeven
2024-04-17 8:08 ` Michael Schmitz
2024-04-17 8:16 ` Eero Tamminen
2024-04-17 16:26 ` Andreas Schwab [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=87bk68gdkm.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=oak@helsinkinet.fi \
--cc=schmitzmic@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).