linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Christoph Hellwig <hch@lst.de>,
	iommu@lists.linux-foundation.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arch: switch the default on ARCH_HAS_SG_CHAIN
Date: Mon, 19 Nov 2018 14:58:52 +0100	[thread overview]
Message-ID: <20181119135852.GA16428@lst.de> (raw)
In-Reply-To: <mhng-9c1955e1-d7cf-4ee4-8bf8-6bef720c9b98@palmer-si-x1c4>

On Fri, Nov 16, 2018 at 08:52:14AM -0800, Palmer Dabbelt wrote:
> As far as I can tell, it looks like m68k, mips, and powerpc mention an 
> IOMMU in their ports, don't set ARCH_HAS_SG_CHAIN, and with this patch set 
> won't set ARCH_NO_SG_CHAIN.

m68k has no iommu, and not operations that operate on a scatterlist.

mips has a trivial iommu driver (jazzdma), but I wrote the current
instance of it, nad it is fine.

powerpc has various iommu, but actually enables ARCH_HAS_SG_CHAIN
unconditionally.

> The issue is that I'm not sure how to 
> determine what constitutes a horrible legacy IOMMU, at least with respect 
> to not being able to use scatterlist chaining.

It basically means someone is iterating using manual pointer arithmetics
over a multi-element scatterlist instead of using the sg_next and
for_each_sg helpers.

  parent reply	other threads:[~2018-11-19 13:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  9:00 scatterlist arch cleanups Christoph Hellwig
2018-11-09  9:00 ` Christoph Hellwig
2018-11-09  9:00 ` [PATCH 1/2] csky, h8300, riscv: remove <asm/scatterlist.h> leftovers Christoph Hellwig
2018-11-09  9:00   ` Christoph Hellwig
     [not found]   ` <20181109090008.24150-2-hch-jcswGhMUV9g@public.gmane.org>
2018-11-16  1:47     ` Palmer Dabbelt
2018-11-16  1:47       ` Palmer Dabbelt
2018-12-06 15:00   ` Christoph Hellwig
2018-12-06 15:00     ` Christoph Hellwig
2018-11-09  9:00 ` [PATCH 2/2] arch: switch the default on ARCH_HAS_SG_CHAIN Christoph Hellwig
2018-11-09  9:00   ` Christoph Hellwig
2018-11-16 16:52   ` Palmer Dabbelt
2018-11-16 16:52     ` Palmer Dabbelt
2018-11-19 13:58     ` Christoph Hellwig [this message]
2018-11-19 13:58       ` Christoph Hellwig
     [not found]       ` <20181119135852.GA16428-jcswGhMUV9g@public.gmane.org>
2018-11-20  0:48         ` Palmer Dabbelt
2018-11-20  0:48           ` Palmer Dabbelt
2018-12-06 15:01   ` Christoph Hellwig
2018-12-06 15:01     ` Christoph Hellwig
2018-11-29 17:06 ` scatterlist arch cleanups Christoph Hellwig
2018-11-29 17:06   ` Christoph Hellwig

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=20181119135852.GA16428@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palmer@sifive.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).