From: Suzuki.Poulose@arm.com (Suzuki K Poulose)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix /proc/cpuinfo for elf32
Date: Tue, 26 Apr 2016 10:20:51 +0100 [thread overview]
Message-ID: <571F32F3.7080005@arm.com> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED0A6E6FB7@SZXEMA509-MBX.china.huawei.com>
On 26/04/16 03:21, Zengtao (B) wrote:
>
> So you mean the 64-bit grep should see the same cpuinfo as its father process
> which is 32-bit?
>
> For 32-bit process running on 64-bit kernel, we have to explicitly call the personality
> syscall to get the right cpuinfo, but how to deal with the old 32-bit binaries?
Yes, you could use the syscall to switch the personality. Alternately, you could run
"linux32" command to switch the personality to PER_LINUX32 and then execute
64/32 bit applications.
Suzuki
WARNING: multiple messages have this Message-ID (diff)
From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: "Zengtao (B)" <prime.zeng@hisilicon.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: "will.deacon@arm.com" <will.deacon@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"yang.shi@linaro.org" <yang.shi@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: fix /proc/cpuinfo for elf32
Date: Tue, 26 Apr 2016 10:20:51 +0100 [thread overview]
Message-ID: <571F32F3.7080005@arm.com> (raw)
In-Reply-To: <678F3D1BB717D949B966B68EAEB446ED0A6E6FB7@SZXEMA509-MBX.china.huawei.com>
On 26/04/16 03:21, Zengtao (B) wrote:
>
> So you mean the 64-bit grep should see the same cpuinfo as its father process
> which is 32-bit?
>
> For 32-bit process running on 64-bit kernel, we have to explicitly call the personality
> syscall to get the right cpuinfo, but how to deal with the old 32-bit binaries?
Yes, you could use the syscall to switch the personality. Alternately, you could run
"linux32" command to switch the personality to PER_LINUX32 and then execute
64/32 bit applications.
Suzuki
next prev parent reply other threads:[~2016-04-26 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 3:37 [PATCH] arm64: fix /proc/cpuinfo for elf32 Zeng Tao
2016-04-25 3:37 ` Zeng Tao
2016-04-25 9:12 ` Catalin Marinas
2016-04-25 9:12 ` Catalin Marinas
2016-04-26 2:21 ` Zengtao (B)
2016-04-26 2:21 ` Zengtao (B)
2016-04-26 9:20 ` Suzuki K Poulose [this message]
2016-04-26 9:20 ` Suzuki K Poulose
2016-04-27 2:13 ` Zengtao (B)
2016-04-27 2:13 ` Zengtao (B)
2016-04-27 10:24 ` Catalin Marinas
2016-04-27 10:24 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2016-04-26 2:07 Zengtao (B)
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=571F32F3.7080005@arm.com \
--to=suzuki.poulose@arm.com \
--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.