From: Christoph Hellwig <hch@infradead.org>
To: Andy Duan <fugang.duan@nxp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"ohad@wizery.com" <ohad@wizery.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
Robin Murphy <robin.murphy@arm.com>,
"linux-remoteproc@vger.kernel.org"
<linux-remoteproc@vger.kernel.org>,
"anup@brainfault.org" <anup@brainfault.org>,
"loic.pallardy@st.com" <loic.pallardy@st.com>,
dl-linux-imx <linux-imx@nxp.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Jason Liu <jason.hui.liu@nxp.com>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [rpmsg PATCH v2 1/1] rpmsg: virtio_rpmsg_bus: fix unexpected huge vmap mappings
Date: Thu, 10 Jan 2019 06:07:26 -0800 [thread overview]
Message-ID: <20190110140726.GA6223@infradead.org> (raw)
In-Reply-To: <VI1PR0402MB36000BD05AF4B242E13D9D05FF840@VI1PR0402MB3600.eurprd04.prod.outlook.com>
On Thu, Jan 10, 2019 at 01:45:20AM +0000, Andy Duan wrote:
> Do you have any other comments for the patch ?
> Current driver break remoteproc on NXP i.MX8 platform , the patch is bugfix the virtio rpmsg bus, we hope the patch enter to next and stable tree if no other comments.
The answer remains that you CAN NOT call vmalloc_to_page or virt_to_page
on DMA coherent memory, and the driver has been broken ever since it
was merged. We need to fix the root cause and not the symptom.
next prev parent reply other threads:[~2019-01-10 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 8:25 Andy Duan
2018-12-26 12:27 ` Ard Biesheuvel
2018-12-26 12:27 ` Ard Biesheuvel
2018-12-26 14:50 ` Christoph Hellwig
2018-12-27 2:36 ` Andy Duan
2018-12-27 12:19 ` Christoph Hellwig
2018-12-28 1:48 ` Andy Duan
2019-01-10 1:45 ` Andy Duan
2019-01-10 13:06 ` Loic PALLARDY
2019-01-11 1:56 ` Andy Duan
2019-01-10 14:07 ` Christoph Hellwig [this message]
2019-01-11 1:28 ` Andy Duan
2019-01-14 9:53 ` Christoph Hellwig
2019-01-16 3:38 ` Andy Duan
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=20190110140726.GA6223@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anup@brainfault.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=fugang.duan@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=jason.hui.liu@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-mm@kvack.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.com \
--cc=peng.fan@nxp.com \
--cc=robin.murphy@arm.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