linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Forney <mforney@mforney.org>
Cc: linux-riscv@lists.infradead.org, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org
Subject: Re: virtio-gpu without ARCH_HAS_SG_CHAIN
Date: Tue, 30 Oct 2018 23:12:06 -0700	[thread overview]
Message-ID: <20181031061206.GA2828@infradead.org> (raw)
Message-ID: <20181031061206.gvGYY1Rq_mWNUNM625X3guyghL8xwoUxi_OgqhS7PNg@z> (raw)
In-Reply-To: <CAGw6cBsWHB4aRf=kPoT+v-FbtL0ymeBtZNEwKYobFizc0cLeaQ@mail.gmail.com>

There is no good reason to not define ARCH_HAS_SG_CHAIN.  To fix
your immediate problem just select it from riscv, as riscv uses
the generic dma-direct code which is chained S/G safe by definition.

And if you want to get extra points do a quick audit of the remaning
iommu drivers on architectures that don't define it so that we can
kill the symbol.

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

  parent reply	other threads:[~2018-10-31  6:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 19:46 virtio-gpu without ARCH_HAS_SG_CHAIN Michael Forney
2018-10-29 19:46 ` Michael Forney
2018-10-29 20:06 ` David Abdurachmanov
2018-10-29 20:06   ` David Abdurachmanov
2018-10-30 17:25   ` Michael Forney
2018-10-30 17:25     ` Michael Forney
2018-10-31  8:48     ` David Abdurachmanov
2018-10-31  8:48       ` David Abdurachmanov
2018-10-30  7:23 ` Gerd Hoffmann
2018-10-30  7:23   ` Gerd Hoffmann
2018-10-30  9:27   ` Koenig, Christian
2018-10-30  9:27     ` Koenig, Christian
2018-10-31  6:12 ` Christoph Hellwig [this message]
2018-10-31  6:12   ` 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=20181031061206.GA2828@infradead.org \
    --to=hch@infradead.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mforney@mforney.org \
    --cc=virtualization@lists.linux-foundation.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).