From mboxrd@z Thu Jan 1 00:00:00 1970 From: will.deacon@arm.com (Will Deacon) Date: Tue, 22 Jul 2014 09:13:54 +0100 Subject: [PATCH v7 8/9] ARM: vdso initialization, mapping, and synchronization In-Reply-To: References: <20140702144050.GD24879@arm.com> <53B430F3.9070804@mentor.com> <20140702162726.GG24879@arm.com> <20140702172443.GI24879@arm.com> <20140702185422.GP24879@arm.com> Message-ID: <20140722081354.GE24282@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Jul 22, 2014 at 01:14:35AM +0100, Andy Lutomirski wrote: > On Wed, Jul 2, 2014 at 11:54 AM, Will Deacon wrote: > > Ok, so that explains why things are working at the moment and it sounds like > > we have some wiggle room too. I'll look at moving the datapage anyway, since > > having these artificial limits is error-prone and fragile, but I don't think > > it's something we need to panic about immediately. > > > > Also, if you get to the bottom of your binutils issues with the section > > allocation, that might work for us since we don't really have any legacy > > binutils supporting arm64. > > Just in case anyone still cares about this thread, moving the vvar > area back before the vdso text is queued up for 3.17. I gave up on > reliably keeping binutils happy with my ugly hack. The same change is also queued for arm64. Thanks Andy, Will