Re: rseq/arm32: choosing rseq code signature

2019-04-18 Thread Richard Earnshaw (lists)
On 17/04/2019 16:30, Mathieu Desnoyers wrote: > - On Apr 17, 2019, at 10:43 AM, Mathieu Desnoyers > mathieu.desnoy...@efficios.com wrote: > >> - On Apr 17, 2019, at 6:37 AM, richard earnshaw richard.earns...@arm.com >> wrote: >> >>> On 16/04/2019 14:39, Mathieu Desnoyers wrote: -

Re: rseq/arm32: choosing rseq code signature

2019-04-17 Thread Richard Earnshaw (lists)
On 16/04/2019 14:39, Mathieu Desnoyers wrote: > - On Apr 15, 2019, at 9:37 AM, Mathieu Desnoyers > mathieu.desnoy...@efficios.com wrote: > >> - On Apr 15, 2019, at 9:30 AM, peter maydell peter.mayd...@linaro.org >> wrote: >> >>> On Mon, 15 Apr 2019 at 14:11, Mathieu Desnoyers >>> wrote:

Re: framebuffer corruption due to overlapping stp instructions on arm64

2018-08-08 Thread Richard Earnshaw (lists)
On 08/08/18 15:12, Mikulas Patocka wrote: > > > On Wed, 8 Aug 2018, Catalin Marinas wrote: > >> On Fri, Aug 03, 2018 at 01:09:02PM -0400, Mikulas Patocka wrote: >>> while (1) { >>> start = (unsigned)random() % (LEN + 1); >>> end = (unsigned)random() % (LEN + 1); >>>

Re: framebuffer corruption due to overlapping stp instructions on arm64

2018-08-03 Thread Richard Earnshaw (lists)
On 03/08/18 14:31, Mikulas Patocka wrote: > > > On Fri, 3 Aug 2018, Andrew Pinski wrote: > >> On Thu, Aug 2, 2018 at 12:31 PM Mikulas Patocka wrote: >>> >>> Hi >>> >>> I tried to use a PCIe graphics card on the MacchiatoBIN board and I hit a >>> strange problem. >>> >>> When I use the links bro

Re: framebuffer corruption due to overlapping stp instructions on arm64

2018-08-03 Thread Richard Earnshaw (lists)
On 03/08/18 10:29, Ard Biesheuvel wrote: > On 3 August 2018 at 11:15, Ramana Radhakrishnan > wrote: >> On Fri, Aug 3, 2018 at 8:53 AM, Florian Weimer wrote: >>> On 08/03/2018 09:11 AM, Andrew Pinski wrote: Yes fix Links not to use memcpy on the framebuffer. It is undefined behavior