From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: MMU: fix wrong dma_flush_range in arm_create_pte()
Date: Wed, 15 Aug 2018 09:55:32 -0700 [thread overview]
Message-ID: <CAHQ1cqHTmB_p1kO9YmYyipA35JYS13sdhvhP4V+NcW=Li8kyTw@mail.gmail.com> (raw)
In-Reply-To: <20180815134937.ylp6k7ibo67rft5p@pengutronix.de>
On Wed, Aug 15, 2018 at 6:49 AM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> On Wed, Aug 15, 2018 at 03:46:59PM +0200, Sascha Hauer wrote:
> > Since 7ba0f2d299 arm_create_pte() flushes the page table entries itself
> > and it's no longer done in arch_remap_range(). Unfortunately it does
> > not flush the modified 1st level page table entry, but instead the base
> > of the page table. Fix it up.
> >
> > Fixes: 7ba0f2d299 ARM: mmu: fix cache flushing when replacing a section with a PTE
>
> Since the patch breaking it was the reason for creating v2018.07.1, this
> will be a reason for creating v2018.07.2 (and also v2018.08.1)
>
> I noticed misbehaviour when trying to sue network on a i.MX53 based
> board, here we got tronsmission timeouts. These are fixed with this patch
>
Heh, you beat me to it by a couple of hours! I came up with the same
patch debugging networking (and various others) issues on i.MX51 last
night and was about to submit it.
Thanks,
Andrey Smirnov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-15 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 13:46 Sascha Hauer
2018-08-15 13:49 ` Sascha Hauer
2018-08-15 16:55 ` Andrey Smirnov [this message]
2018-08-16 7:21 ` Sascha Hauer
2018-08-16 21:30 ` Giorgio Dal Molin
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='CAHQ1cqHTmB_p1kO9YmYyipA35JYS13sdhvhP4V+NcW=Li8kyTw@mail.gmail.com' \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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