All of lore.kernel.org
 help / color / mirror / Atom feed
From: nsz@port70.net (Szabolcs Nagy)
To: linux-arm-kernel@lists.infradead.org
Subject: [musl] Re: Thread pointer changes
Date: Sat, 28 Jun 2014 18:37:36 +0200	[thread overview]
Message-ID: <20140628163734.GV23102@port70.net> (raw)
In-Reply-To: <20140627231224.GY32514@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.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)

  reply	other threads:[~2014-06-28 16:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140610072835.GA8466@brightrain.aerifal.cx>
     [not found] ` <20140611145533.GT179@brightrain.aerifal.cx>
2014-06-27 19:27   ` Thread pointer changes Andy Lutomirski
2014-06-27 20:09     ` Russell King - ARM Linux
2014-06-27 21:09       ` [musl] " Szabolcs Nagy
2014-06-27 21:30         ` Russell King - ARM Linux
2014-06-27 21:47           ` Andy Lutomirski
2014-06-27 21:58             ` Rich Felker
2014-06-27 21:55           ` Rich Felker
2014-06-27 22:17             ` Russell King - ARM Linux
2014-06-27 22:25               ` Andy Lutomirski
2014-06-27 22:54                 ` Russell King - ARM Linux
2014-06-28  0:11                   ` Rich Felker
2014-06-27 22:33               ` Rich Felker
2014-06-27 23:07                 ` Russell King - ARM Linux
2014-06-27 23:17                   ` Andy Lutomirski
2014-06-27 23:35                     ` Russell King - ARM Linux
2014-06-27 23:40                       ` Andy Lutomirski
2014-06-30 15:38                         ` Christopher Covington
2014-07-02 21:16                           ` Rich Felker
2014-06-28  0:20                       ` Rich Felker
2014-06-27 22:40               ` Szabolcs Nagy
2014-06-27 22:51                 ` Andy Lutomirski
2014-06-27 23:12                 ` Russell King - ARM Linux
2014-06-28 16:37                   ` Szabolcs Nagy [this message]
2014-06-27 21:37     ` Rich Felker
2014-06-27 22:04       ` Russell King - ARM Linux
2014-06-27 22:26         ` Rich Felker
2014-06-27 23:03           ` Russell King - ARM Linux
2014-06-28  7:09         ` u-igbb at aetey.se
2014-06-27 23:20     ` Russell King - ARM Linux
2014-06-28  0:38       ` [musl] " Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140628163734.GV23102@port70.net \
    --to=nsz@port70.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.