[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140628163734.GV23102@port70.net>
Date: Sat, 28 Jun 2014 18:37:36 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Rich Felker <dalias@...c.org>, musl@...ts.openwall.com,
Kees Cook <keescook@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
Andy Lutomirski <luto@...capital.net>
Subject: Re: Re: Thread pointer changes
* Russell King - ARM Linux <linux@....linux.org.uk> [2014-06-28 00:12:24 +0100]:
> On Sat, Jun 28, 2014 at 12:40:17AM +0200, Szabolcs Nagy wrote:
> > but cp15 barrier is deprecated on armv7+
>
> Can you _please_ read all my replies and stop cherry picking what you
> want? There's many of you, and only one of me - please do me the
> effort of fully reading my replies before replying on points I've
> already included.
I've read it, we knew about uname, /proc and the TLS HWCAP flag,
and i thought it's clear that uname is inappropriate for determining
isa features because we don't know the arm naming scheme used in the
future..
so the situation is
- dmb vs cp15 dispatch needs extra uname syscall and fragile string
parsing at program startup
- there is no reasonable way to determine kuser page availability
on armv6k+ if pax kernel needs to be supported (asking the system
integrator or using process_vm_readv are not reasonable)
- there is no reasonable way to determine if the system is smp and
needs barriers (parsing /proc/cpuinfo is not reasonable)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
