From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: mm: Remove check for VM_IO to fix deferred I/O
Date: Sat, 29 Jan 2022 10:55:30 +1100 (AEDT) [thread overview]
Message-ID: <4d65d2e1-5fb3-456-3cc5-fbd3167d06c@linux-m68k.org> (raw)
In-Reply-To: <b1cd50eb-e476-b4bd-0b2f-b4a8699660f6@gmail.com>
On Sat, 29 Jan 2022, Michael Schmitz wrote:
> Hi Geert,
>
> for hwregs_present(), the exception fixup will handle any access error
> (through send_fault_sig()), so this should continue to work.
>
> Why the special handling of VM_IO pages? Maybe hp300 had marked all IO
> register pages VM_IO to distinguish IO faults from VM faults...
>
> The only other area I can imagine this might have an impact is the Mac's
> pseudo-DMA - FInn might want to give this some testing.
>
mac_scsi.c and mac_esp.c don't use ioremap(). They rely on head.S:
mmu_map_eq #0x50000000,#0x03000000,%d3
Having said that, I will run some tests if you still think it necessary.
next prev parent reply other threads:[~2022-01-28 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 17:30 [PATCH] m68k: mm: Remove check for VM_IO to fix deferred I/O Geert Uytterhoeven
2022-01-28 21:26 ` Michael Schmitz
2022-01-28 23:55 ` Finn Thain [this message]
2022-01-29 2:08 ` Michael Schmitz
2022-01-30 0:32 ` Michael Schmitz
2022-01-30 6:57 ` Michael Schmitz
2022-01-31 2:21 ` Michael Schmitz
2022-02-07 13:06 ` Geert Uytterhoeven
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=4d65d2e1-5fb3-456-3cc5-fbd3167d06c@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--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 NNTP newsgroup(s).