From: Cho KyongHo <pullip.cho@samsung.com>
To: "'Grant Grundler'" <grundler@chromium.org>,
"'Joerg Roedel'" <joro@8bytes.org>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v6 01/12] iommu/exynos: add missing cache flush for removed pagetable entries
Date: Thu, 04 Jul 2013 20:20:49 +0900 [thread overview]
Message-ID: <003301ce78a8$89218fc0$9b64af40$@samsung.com> (raw)
In-Reply-To: <CANEJEGvAYxdyq7iK6Y+YcgCFOKhA4+01=m4ofUs3ZE=Mwf7PRw@mail.gmail.com>
> From: grundler@google.com [mailto:grundler@google.com] On Behalf Of Grant Grundler
> Sent: Thursday, July 04, 2013 5:44 AM
>
> Ping?
Hi.
Sorry for late update the patch set.
I am still working on the patch set when I am free.
Implementation of the updated patch set has been finished but not tested yet.
I will post the patches after simple test :)
Thank you.
>
> On Mon, Jul 1, 2013 at 6:49 PM, Grant Grundler <grundler@chromium.org> wrote:
> > On Tuesday, December 25, 2012 6:00:01 PM UTC-8, Cho KyongHo wrote:
> >> This commit adds cache flush for removed small page and large page
> >> entries in exynos_iommu_unmap(). Missing cache flush of removed page
> >> table entries can cause missing page fault interrupt when a master IP
> >> accesses an unmapped area.
> >
> > KyongHo,
> > It appears this patch was never applied and got caught up in the
> > device tree binding discussion. AFAICT, this patch is still necessary.
> > Can you resubmit this patch separately. Or ok if I do?
> >
> > Original patch is here:
> > https://patchwork.kernel.org/patch/1910261/
> >
> > thanks,
> > grant
next prev parent reply other threads:[~2013-07-04 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 1:49 Grant Grundler
2013-07-02 2:21 ` Grant Grundler
2013-07-03 20:43 ` Grant Grundler
2013-07-04 11:20 ` Cho KyongHo [this message]
2013-07-08 18:21 ` Grant Grundler
2013-07-08 18:29 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2012-12-26 1:53 Cho KyongHo
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='003301ce78a8$89218fc0$9b64af40$@samsung.com' \
--to=pullip.cho@samsung.com \
--cc=grundler@chromium.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®