Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp2884881imm; Sun, 5 Aug 2018 14:53:42 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdtyKRm+jiLcCDs/Ev0cTJr34Yw1kuCcymUeGkNkAKe3zEgFr1UYoXENepoQgT9tq2EtxuO X-Received: by 2002:a65:4107:: with SMTP id w7-v6mr11633371pgp.302.1533506022436; Sun, 05 Aug 2018 14:53:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533506022; cv=none; d=google.com; s=arc-20160816; b=jZAvp9UC3VoHa6H7a/Yv/J9jfbox4cd6XBTdmdbTzCjmJ1YUexYo/8S0LXD7NK/3qo 03RNW/acJznHOYXFn2TnZThGo9Khz7ZUi382KA2sROr3N8dEkDRjBo7EamiAAlE4ExId 06jTLxtiPbpOhcd4djcwuAm6lpnQZRbLizlfLRJck9y3HVoXO5NtIB5InFadlI4rzm9j 0+9t4EBiOiZWV/JJWziYrisU0vyckQsp7Kqmo6eAyVD0lwnBub7MXc0fl4cx04S6Z8h+ ePuYPB9QfLlqsWl0sgK7YCbnt4fY33ByJV96cV2ncixPjayp3gUwpxGZpvHk3ZdNi72J sHEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=UyDdgw7dFzs6GaQVVXy3LcwL1GGw8nyg7qxuBxV4bsM=; b=Ki7nRaSt8o+VhWGm8+ZS2KbnpRstg2bZU5/yqUYYlIs9KvQKX2ppJYW7L7cIj0RoT2 BAEzDqNPExAqOnTemYde3RTbpv8yyuClf/z0a621JH1Oc0p3EpxXsBC6p5An69pzdo7Q PtmeuUUi9rnS9soIx5iVUsQYtorZgzj6F2i2bmD2l++X2Qn6atJ6jNVTpofHZ5tq4B9O BrnolX4ewbe/IOLsM6uVu/mVFpH9swXfhGr4xdnB5rPdm3c5naMQk0o9y356zVdsJ/CY LhjbSogikSrZ5qlsAVjigmWuOc8QWY6xc8cBoCXY2zP5CRoOn8YGeQXvZ7LZUJYPkggd J2qg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y22-v6si11586795pgj.436.2018.08.05.14.53.27; Sun, 05 Aug 2018 14:53:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728340AbeHEX55 (ORCPT + 99 others); Sun, 5 Aug 2018 19:57:57 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:43088 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726992AbeHEX55 (ORCPT ); Sun, 5 Aug 2018 19:57:57 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id D7FC08063C; Sun, 5 Aug 2018 23:51:50 +0200 (CEST) Date: Sun, 5 Aug 2018 23:51:50 +0200 From: Pavel Machek To: Mikulas Patocka Cc: Andrew Pinski , Richard Earnshaw , ard.biesheuvel@linaro.org, Ramana Radhakrishnan , Florian Weimer , thomas.petazzoni@free-electrons.com, GNU C Library , Catalin Marinas , Will Deacon , linux@armlinux.org.uk, LKML , linux-arm-kernel@lists.infradead.org Subject: Re: framebuffer corruption due to overlapping stp instructions on arm64 Message-ID: <20180805215150.GB1862@amd> References: <9acdacdb-3bd5-b71a-3003-e48132ee1371@redhat.com> <11f9185a-7f71-83df-3a57-0a0ae9c1f934@arm.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZfOjI3PrQbgiZnxM" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > Can you run the test program on x86 using the similar framebuffer > > setup? Does doing two writes (one aligned and one unaligned but > > overlapping with previous one) cause the same issue? I suspect it > > does, then using memcpy for frame buffers is wrong. I'm pretty sure it will work ok on x86. > Overlapping unaligned writes work on x86 - they have to, because of=20 > backward compatibility. It is not that easy. 8086s (and similar) did not have MTRRs and PATs either. Overlapping unaligned writes _on main memory_, _with normal MTRR settings_ certainly work ok on x86. Chances is memory type can be configured to work similar way on your ARM/PCIe case? > 8086, 80286 and 80386 didn't have any cache at all. 386s had cache (but not on die). Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --ZfOjI3PrQbgiZnxM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltncXYACgkQMOfwapXb+vLjnACgviHS0QA96XvspC2s/b9nRkCR K4cAoKc484UBeHoiMMGsNdgqoeaO8ADS =xTyZ -----END PGP SIGNATURE----- --ZfOjI3PrQbgiZnxM--