This is the mail archive of the
mailing list for the glibc project.
Re: framebuffer corruption due to overlapping stp instructions on arm64
- From: Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>
- To: Pavel Machek <pavel at ucw dot cz>
- Cc: Andrew Pinski <pinskia at gmail dot com>, Mikulas Patocka <mpatocka at redhat dot com>, Catalin Marinas <catalin dot marinas at arm dot com>, Will Deacon <will dot deacon at arm dot com>, Russell King <linux at armlinux dot org dot uk>, Thomas Petazzoni <thomas dot petazzoni at free-electrons dot com>, linux-arm-kernel <linux-arm-kernel at lists dot infradead dot org>, LKML <linux-kernel at vger dot kernel dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 6 Aug 2018 09:04:33 +0100
- Subject: Re: framebuffer corruption due to overlapping stp instructions on arm64
- References: <alpine.LRH.firstname.lastname@example.org> <CA+=Sn1mWkjuwVnjw6OWWUM=UcP76bdFa680FebCseewHfx3NpA@mail.gmail.com> <20180805213615.GA1862@amd>
On Sun, Aug 5, 2018 at 10:36 PM, Pavel Machek <email@example.com> wrote:
>> > I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a
>> > strange problem.
>> > When I use the links browser in graphics mode on the framebuffer, I get
>> > occasional pixel corruption. Links does memcpy, memset and 4-byte writes
>> > on the framebuffer - nothing else.
>> > I found out that the pixel corruption is caused by overlapping unaligned
>> > stp instructions inside memcpy. In order to avoid branching, the arm64
>> > memcpy implementation may write the same destination twice with different
>> > alignment. If I put "dmb sy" between the overlapping stp instructions, the
>> > pixel corruption goes away.
>> > This seems like a hardware bug. Is it a known errata? Do you have any
>> > workarounds for it?
>> Yes fix Links not to use memcpy on the framebuffer.
>> It is undefined behavior to use device memory with memcpy.
> No, I don't think so. Why do you think so?
It is undefined behaviour in the architecture.