Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1373255

Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number of running thread

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number of running thread
Date 2016-04-07 12:40 +0200
Message-ID <rlfvY-2qa-1@gated-at.bofh.it> (permalink)
References (3 earlier) <rkiFA-89A-9@gated-at.bofh.it> <rkjBE-lz-11@gated-at.bofh.it> <rkBId-6yB-5@gated-at.bofh.it> <rkCkX-70h-15@gated-at.bofh.it> <rle6R-1ww-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Thu, Apr 07, 2016 at 11:01:25AM +0200, Florian Weimer wrote:
> > Because ideally this structure would be part of the initial (glibc) TCB
> > with fixed offset etc.
> 
> This is not possible because we have layering violations and code
> assumes it knows the precise of the glibc TCB.  I think Address
> Sanitizer is in this category.  This means we cannot adjust the TCB size
> based on the kernel headers used to compile glibc, and there will have
> to be some indirection.

So with the proposed fixed sized object it would work, right?

Which is part of the reason its being proposed as a fixed sized object.

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[RFC PATCH v6 0/5] Thread-local ABI system call (CPU number cache) Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 19:10 +0200
  [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 19:10 +0200
    Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread "H. Peter Anvin" <hpa@zytor.com> - 2016-04-04 19:20 +0200
      Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 21:50 +0200
        Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 22:50 +0200
          Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-05 18:10 +0200
            Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Peter Zijlstra <peterz@infradead.org> - 2016-04-05 18:50 +0200
              Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 11:10 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Peter Zijlstra <peterz@infradead.org> - 2016-04-07 12:40 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 12:40 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Peter Zijlstra <peterz@infradead.org> - 2016-04-07 13:30 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 14:10 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Peter Zijlstra <peterz@infradead.org> - 2016-04-07 14:30 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 14:40 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-07 18:00 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-07 14:40 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Linus Torvalds <torvalds@linux-foundation.org> - 2016-04-07 18:40 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Andy Lutomirski <luto@amacapital.net> - 2016-04-07 18:50 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Linus Torvalds <torvalds@linux-foundation.org> - 2016-04-07 19:00 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 19:00 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Linus Torvalds <torvalds@linux-foundation.org> - 2016-04-07 19:00 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-07 20:50 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Andi Kleen <andi@firstfloor.org> - 2016-04-07 22:30 +0200
                Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU  number of running thread Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-07 23:00 +0200
    Re: [RFC PATCH v6 1/5] Thread-local ABI system call: cache CPU number  of running thread Florian Weimer <fweimer@redhat.com> - 2016-04-07 12:50 +0200
  [RFC PATCH v6 5/5] Thread-local ABI: wire up x86 32/64 system call Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 19:10 +0200
  [RFC PATCH v6 3/5] Thread-local ABI: wire up ARM system call Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 19:10 +0200
  [RFC PATCH v6 4/5] Thread-local ABI cpu_id: x86 32/64 resume notifier Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-04-04 19:10 +0200

csiph-web