From: Michael Forney <mforney@mforney.org>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
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 10:25:52 -0700 [thread overview]
Message-ID: <CAGw6cBtMu7qs2in-=eX1J6bpPK-L-8cSa5pocQ6CA=en-ju3EA@mail.gmail.com> (raw)
Message-ID: <20181030172552.XBzBNiE4KOKfP4GlUeBMNMlBVc9ponPNse6RqgTV-Ec@z> (raw)
In-Reply-To: <CAEn-LTopspBXzoLZEFWQGxxC7uNJ9RZHiHyYmJPpWR4zKnj5zw@mail.gmail.com>
On 2018-10-29, David Abdurachmanov <david.abdurachmanov@gmail.com> wrote:
> On Mon, Oct 29, 2018 at 8:47 PM Michael Forney <mforney@mforney.org> wrote:
>>
>> - Should riscv support ARCH_HAS_SG_CHAIN?
>
> Non-expert here, but it looks like ARCH_HAS_SG_CHAIN
> support is generic, and a number of well known architectures
> support it.
>
> So it's basically two line patch someone needs to send and
> at least make a test by building the kernel. I can do that if you want.
If that's all there is to it, then yeah, that would be appreciated. Thanks!
Though, I assume there's *some* architecture-specific consideration
that needs to be done, since it has to be selected on each
architecture that supports it.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-10-30 17:26 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 [this message]
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
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='CAGw6cBtMu7qs2in-=eX1J6bpPK-L-8cSa5pocQ6CA=en-ju3EA@mail.gmail.com' \
--to=mforney@mforney.org \
--cc=david.abdurachmanov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-riscv@lists.infradead.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).