[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87muvwsxfj.wl%kuninori.morimoto.gx@renesas.com>
Date: Fri, 15 Jun 2018 00:35:20 +0000
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, <vkoul@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Magnus Damm <magnus.damm@...il.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Kieran Bingham <kieran@...uared.org.uk>,
Geert Uytterhoeven <geert+renesas@...der.be>,
<dmaengine@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>
Subject: Re: [PATCH v2] dmaengine: rcar-dmac: don't use DMAC error interrupt
Hi, again
> > > Current rcar-dmac is using DMAC error interrupt which will handle all
> > > channel's error. But in this design, error handling itself will be
> > > issue if user want to use virtualization, multi OS, etc.
> > > This patch removes current DMAC error interrupt handling, and handle it
> > > on each channel interrupt handler.
> >
> > Just wondering, what's the usage pattern where this causes a problem?
> > Do you plan to export part of a SYS-DMAC instance to a guest?
>
> "virtualization, multi OS" part is maybe misleading.
> It will be problem on non virtualization, too.
>
> > How to maintain host/guest isolation?
>
> This is another topic/issue, I think
I will post v3 patch, soon
Best regards
---
Kuninori Morimoto
Powered by blists - more mailing lists