From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: From: David Laight To: 'Mikulas Patocka' Subject: RE: framebuffer corruption due to overlapping stp instructions on arm64 Date: Wed, 8 Aug 2018 14:26:11 +0000 Message-ID: <19c70d2a0b224db78f72dd316ad006b8@AcuMS.aculab.com> References: <20180803094129.GB17798@arm.com> <20180808121641.GB24736@iMac.local> In-Reply-To: MIME-Version: 1.0 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Thomas Petazzoni , Joao Pinto , Ard Biesheuvel , 'Catalin Marinas' , Will Deacon , Russell King , Linux Kernel Mailing List , Matt Sealey , linux-pci , Jingoo Han , linux-arm-kernel Content-Type: text/plain; charset="us-ascii" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+bjorn=helgaas.com@lists.infradead.org List-ID: From: Mikulas Patocka > Sent: 08 August 2018 14:47 ... > The problem on ARM is that I see data corruption when the overlapping > unaligned writes are done just by a single core. Is this a sequence of unaligned writes (that shouldn't modify the same physical locations) or an aligned write followed by an unaligned one that updates part of the earlier write. (Or the opposite order?) It might be that the unaligned writes are bypassing the write-combining buffer (without flushing it) - so overtake the aligned write. Alternatively the unaligned writes go through the write-combining buffer but the byte-enables aren't handled in the expected way. It ought to be possible to work out which sequence is actually broken. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel