From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Jakub Kicinski <kuba@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Khalid Aziz <khalid@gonehiking.org>,
"Maciej W . Rozycki" <macro@orcam.me.uk>,
Matt Wang <wwentao@vmware.com>,
Miquel van Smoorenburg <mikevs@xs4all.net>,
Mark Salyzyn <salyzyn@android.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
alpha <linux-alpha@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Parisc List <linux-parisc@vger.kernel.org>,
Denis Efremov <efremov@linux.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v2 3/3] arch/*/: remove CONFIG_VIRT_TO_BUS
Date: Tue, 28 Jun 2022 09:03:53 +0200 [thread overview]
Message-ID: <CAMuHMdXUihTPD9A9hs__Xr2ErfOqkZ5KgCHqm+9HvRf39uS5kA@mail.gmail.com> (raw)
In-Reply-To: <9289fd82-285c-035f-5355-4d70ce4f87b0@gmail.com>
Hi Michael,
On Tue, Jun 28, 2022 at 5:26 AM Michael Schmitz <schmitzmic@gmail.com> wrote:
> Am 28.06.2022 um 09:12 schrieb Michael Schmitz:
> > On 27/06/22 20:26, Geert Uytterhoeven wrote:
> >> On Sat, Jun 18, 2022 at 3:06 AM Michael Schmitz <schmitzmic@gmail.com>
> >> wrote:
> >>> Am 18.06.2022 um 00:57 schrieb Arnd Bergmann:
> >>>> From: Arnd Bergmann <arnd@arndb.de>
> >>>>
> >>>> All architecture-independent users of virt_to_bus() and bus_to_virt()
> >>>> have been fixed to use the dma mapping interfaces or have been
> >>>> removed now. This means the definitions on most architectures, and the
> >>>> CONFIG_VIRT_TO_BUS symbol are now obsolete and can be removed.
> >>>>
> >>>> The only exceptions to this are a few network and scsi drivers for m68k
> >>>> Amiga and VME machines and ppc32 Macintosh. These drivers work
> >>>> correctly
> >>>> with the old interfaces and are probably not worth changing.
> >>> The Amiga SCSI drivers are all old WD33C93 ones, and replacing
> >>> virt_to_bus by virt_to_phys in the dma_setup() function there would
> >>> cause no functional change at all.
> >> FTR, the sgiwd93 driver use dma_map_single().
> >
> > Thanks! From what I see, it doesn't have to deal with bounce buffers
> > though?
>
> Leaving the bounce buffer handling in place, and taking a few other
> liberties - this is what converting the easiest case (a3000 SCSI) might
> look like. Any obvious mistakes? The mvme147 driver would be very
> similar to handle (after conversion to a platform device).
Thanks, looks reasonable.
> The driver allocates bounce buffers using kmalloc if it hits an
> unaligned data buffer - can such buffers still even happen these days?
No idea.
> If I understand dma_map_single() correctly, the resulting dma handle
> would be equally misaligned?
>
> To allocate a bounce buffer, would it be OK to use dma_alloc_coherent()
> even though AFAIU memory used for DMA buffers generally isn't consistent
> on m68k?
>
> Thinking ahead to the other two Amiga drivers - I wonder whether
> allocating a static bounce buffer or a DMA pool at driver init is likely
> to succeed if the kernel runs from the low 16 MB RAM chunk? It certainly
> won't succeed if the kernel runs from a higher memory address, so the
> present bounce buffer logic around amiga_chip_alloc() might still need
> to be used here.
>
> Leaves the question whether converting the gvp11 and a2091 drivers is
> actually worth it, if bounce buffers still have to be handled explicitly.
A2091 should be straight-forward, as A3000 is basically A2091 on the
motherboard (comparing the two drivers, looks like someone's been
sprinkling mb()s over the A3000 driver).
I don't have any of these SCSI host adapters (not counting the A590
(~A2091) expansion of the old A500, which is not Linux-capable, and
hasn't been powered on for 20 years).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-06-28 7:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 12:57 [PATCH v2 0/3] phase out CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-17 12:57 ` [PATCH v2 1/3] scsi: dpt_i2o: drop stale VIRT_TO_BUS dependency Arnd Bergmann
2022-06-21 8:43 ` Hannes Reinecke
2022-06-17 12:57 ` [PATCH v2 2/3] scsi: BusLogic remove bus_to_virt Arnd Bergmann
2022-06-17 14:02 ` Robin Murphy
2022-06-21 8:45 ` Hannes Reinecke
2022-06-21 21:56 ` Khalid Aziz
2022-06-23 14:47 ` Arnd Bergmann
2022-06-24 15:38 ` Khalid Aziz
2022-06-24 15:43 ` Arnd Bergmann
2022-06-17 12:57 ` [PATCH v2 3/3] arch/*/: remove CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-18 1:06 ` Michael Schmitz
2022-06-24 9:10 ` Arnd Bergmann
2022-06-26 5:21 ` Michael Schmitz
2022-06-26 8:36 ` Arnd Bergmann
2022-06-27 8:09 ` Michael Schmitz
2022-06-27 8:26 ` Geert Uytterhoeven
2022-06-27 21:12 ` Michael Schmitz
2022-06-28 3:25 ` Michael Schmitz
2022-06-28 7:03 ` Geert Uytterhoeven [this message]
2022-06-28 21:03 ` Michael Schmitz
2022-06-28 21:50 ` Arnd Bergmann
2022-06-28 23:09 ` Michael Schmitz
2022-06-28 23:50 ` Bart Van Assche
2022-06-29 0:01 ` Michael Schmitz
2022-06-29 0:14 ` Michael Schmitz
2022-06-29 6:21 ` Christoph Hellwig
2022-06-30 19:21 ` Michael Schmitz
2022-06-30 8:04 ` David Laight
2022-06-30 9:40 ` Christophe Leroy
2022-06-30 10:32 ` David Laight
2022-06-28 7:08 ` Arnd Bergmann
2022-06-28 21:38 ` Michael Schmitz
2022-06-28 21:55 ` Arnd Bergmann
2022-06-28 23:43 ` Michael Schmitz
2022-06-29 6:25 ` Christoph Hellwig
2022-06-30 19:26 ` Michael Schmitz
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=CAMuHMdXUihTPD9A9hs__Xr2ErfOqkZ5KgCHqm+9HvRf39uS5kA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=efremov@linux.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=khalid@gonehiking.org \
--cc=kuba@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m.szyprowski@samsung.com \
--cc=macro@orcam.me.uk \
--cc=mikevs@xs4all.net \
--cc=mpe@ellerman.id.au \
--cc=robin.murphy@arm.com \
--cc=salyzyn@android.com \
--cc=schmitzmic@gmail.com \
--cc=wwentao@vmware.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).