From: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
To: Laurent Pinchart
<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Sakari Ailus <sakari.ailus-X3B1VOXEql0@public.gmane.org>,
Florian Vaussard <florian.vaussard-p8DiymsW2f8@public.gmane.org>
Subject: Re: [PATCH v2 4/6] iommu/omap: Fix 'no page for' debug message in flush_iotlb_page()
Date: Thu, 3 Apr 2014 15:56:02 -0500 [thread overview]
Message-ID: <533DCAE2.3030900@ti.com> (raw)
In-Reply-To: <1396555298-25246-5-git-send-email-laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
Hi Laurent,
On 04/03/2014 03:01 PM, Laurent Pinchart wrote:
> The flush_iotlb_page() function prints a debug message when no
> corresponding page was found in the TLB. That condition is incorrectly
> checked and always resolves to true, given that the for_each_iotlb_cr()
> loop is never interrupted and always reaches obj->nr_tlb_entries.
>
> Given that we can't have two TLB entries for the same VA, break from the
> loop when a match is found.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
Thanks for the reworked and simplified patch.
Acked-by: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
> ---
> drivers/iommu/omap-iommu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
> index fdf3dd0..428b47a 100644
> --- a/drivers/iommu/omap-iommu.c
> +++ b/drivers/iommu/omap-iommu.c
> @@ -394,6 +394,7 @@ static void flush_iotlb_page(struct omap_iommu *obj, u32 da)
> __func__, start, da, bytes);
> iotlb_load_cr(obj, &cr);
> iommu_write_reg(obj, 1, MMU_FLUSH_ENTRY);
> + break;
> }
> }
> pm_runtime_put_sync(obj->dev);
>
next prev parent reply other threads:[~2014-04-03 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 20:01 [PATCH v2 0/6] OMAP IOMMU fixes Laurent Pinchart
2014-04-03 20:01 ` [PATCH v2 2/6] iommu/omap: Remove omap_iommu_domain_has_cap() function Laurent Pinchart
[not found] ` <1396555298-25246-1-git-send-email-laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-04-03 20:01 ` [PATCH v2 1/6] iommu/omap: Correct init value of iotlb_entry valid field Laurent Pinchart
2014-04-03 20:01 ` [PATCH v2 3/6] iommu/omap: Move to_iommu definition from omap-iopgtable.h Laurent Pinchart
2014-04-03 20:01 ` [PATCH v2 4/6] iommu/omap: Fix 'no page for' debug message in flush_iotlb_page() Laurent Pinchart
[not found] ` <1396555298-25246-5-git-send-email-laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2014-04-03 20:56 ` Suman Anna [this message]
2014-04-03 20:01 ` [PATCH v2 5/6] iommu/omap: Remove comment about supporting single page mappings only Laurent Pinchart
2014-04-03 21:02 ` [PATCH v2 0/6] OMAP IOMMU fixes Suman Anna
[not found] ` <533DCC51.60101-l0cyMroinI0@public.gmane.org>
2014-04-03 21:11 ` Suman Anna
2014-04-03 21:23 ` Laurent Pinchart
2014-04-03 20:01 ` [PATCH v2 6/6] iommu/omap: Fix map protection value handling Laurent Pinchart
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=533DCAE2.3030900@ti.com \
--to=s-anna-l0cymroini0@public.gmane.org \
--cc=florian.vaussard-p8DiymsW2f8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sakari.ailus-X3B1VOXEql0@public.gmane.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