From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Andrew Pinski <pinskia@gmail.com>, Florian Weimer <fweimer@redhat.com>
Cc: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [libc/string] State of PAGE_COPY_FWD / PAGE_COPY_THRESHOLD
Date: Wed, 30 Nov 2016 11:18:00 -0000 [thread overview]
Message-ID: <b0da872c-4505-519a-8cee-e17884d49171@gotplt.org> (raw)
In-Reply-To: <CA+=Sn1=2S4B46SZZyUbEemhYNMK1Fbs6b1BTRx4QXkXp+OVrjQ@mail.gmail.com>
On Thursday 10 November 2016 02:24 PM, Andrew Pinski wrote:
>> Unless you want to read a file (either /proc/cpuinfo or
>> /sys/devices/system/cpu/cpuN/regs/identification/midr_el1) the arch
>> does not provide a way to identify what processor you are running on
>> in userspace. There has been some discussions already on the kernel
>> list and I was going to have another discussion with the arm folks but
>> I can't find the email thread where the meeting was setup for :).
>
> I found the email thread, it is setup for this Friday.
Hi Andrew,
Did this meeting happen? If yes, then can you please summarize the
result of the discussion? I saw a patchset on LKML that emulates MRS
for MIDR and other registers and assumed it may have something to do
with this discussion.
Siddhesh
next prev parent reply other threads:[~2016-11-30 11:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 9:28 Maxim Kuvyrkov
2016-11-01 13:59 ` Adhemerval Zanella
2016-11-10 7:39 ` Maxim Kuvyrkov
2016-11-10 7:48 ` Andrew Pinski
2016-11-10 7:52 ` Maxim Kuvyrkov
2016-11-10 8:01 ` Andrew Pinski
2016-11-10 8:05 ` Andrew Pinski
2016-11-10 8:25 ` Florian Weimer
2016-11-10 8:34 ` Andrew Pinski
2016-11-10 8:55 ` Andrew Pinski
2016-11-10 9:25 ` Siddhesh Poyarekar
2016-11-10 9:29 ` Florian Weimer
2016-11-10 9:34 ` Siddhesh Poyarekar
2016-11-30 11:18 ` Siddhesh Poyarekar [this message]
2016-11-10 8:26 ` Florian Weimer
2016-11-10 8:27 ` Florian Weimer
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=b0da872c-4505-519a-8cee-e17884d49171@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=pinskia@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).