From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@alien8.de>, Oleg Nesterov <oleg@redhat.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Brian Gerst <brgerst@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86/entry: Improve system call entry comments
Date: Tue, 8 Mar 2016 10:40:24 -0800 [thread overview]
Message-ID: <56DF1C98.6030506@zytor.com> (raw)
In-Reply-To: <20160308103004.GB5407@gmail.com>
On 03/08/16 02:30, Ingo Molnar wrote:
>>>> + *
>>>> + * This is considered a slow path. It is not used by modern libc
>>>> + * implementations on modern hardware except during process startup.
>>>> + *
>>
>> Sadly I believe Android still uses int $0x80 in the upstream version.
>
> I don't see how that fact conflicts with my statement: on 64-bit kernels INT $0x80
> will (of course) work, but will land on another entry point: entry_INT80_compat(),
> not entry_INT80_32().
>
> On 32-bit kernels the INT $0x80 entry point is entry_INT80_32().
>
It doesn't. I was referring to the above quote. Trying to fix that.
-hpa
next prev parent reply other threads:[~2016-03-08 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 17:39 Andy Lutomirski
2016-03-07 8:22 ` Ingo Molnar
2016-03-07 16:34 ` H. Peter Anvin
2016-03-08 10:30 ` Ingo Molnar
2016-03-08 18:40 ` H. Peter Anvin [this message]
2016-03-08 18:45 ` Andy Lutomirski
2016-03-08 18:47 ` H. Peter Anvin
2016-03-08 18:50 ` Andy Lutomirski
2016-03-08 18:59 ` H. Peter Anvin
2016-03-08 19:11 ` Andy Lutomirski
2016-03-07 17:01 ` Andy Lutomirski
2016-03-08 10:27 ` Ingo Molnar
2016-03-08 18:29 ` Andy Lutomirski
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=56DF1C98.6030506@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome