From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
tedheadster@gmail.com, George Spelvin <linux@horizon.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: What exactly do 32-bit x86 exceptions push on the stack in the CS slot?
Date: Mon, 21 Nov 2016 10:26:11 -0800 [thread overview]
Message-ID: <5bc7c7b2-875e-6366-9244-7dc6e2fae5c1@zytor.com> (raw)
In-Reply-To: <CA+55aFwH8zQNj42LyqFTbXqU+nUbDgDhqMW+so_-OPpM5SRwuQ@mail.gmail.com>
On 11/21/16 10:00, Linus Torvalds wrote:
>
> Ugh.
>
> I'd much rather we go back to just making the "cs" entry explicitly
> 16-bit, and have a separate padding entry, the way we used to long
> long ago.
>
I would agree 100% with this.
-hpa
next prev parent reply other threads:[~2016-11-21 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 1:52 What exactly do 32-bit x86 exceptions push on the stack in the CS slot? Andy Lutomirski
2016-11-20 2:11 ` Brian Gerst
2016-11-20 2:15 ` Andy Lutomirski
2016-11-21 7:13 ` Ingo Molnar
2016-11-21 18:00 ` Linus Torvalds
2016-11-21 18:26 ` H. Peter Anvin [this message]
2016-11-21 21:21 ` Linus Torvalds
2016-11-21 22:17 ` hpa
2016-11-21 22:25 ` Linus Torvalds
2016-11-24 17:16 ` Andy Lutomirski
2016-11-22 8:30 ` Ingo Molnar
2016-11-22 17:30 ` Andy Lutomirski
2016-11-23 8:57 ` Ingo Molnar
2016-11-21 4:54 ` hpa
2016-11-21 15:58 ` H. Peter Anvin
2016-11-21 18:20 ` Linus Torvalds
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=5bc7c7b2-875e-6366-9244-7dc6e2fae5c1@zytor.com \
--to=hpa@zytor.com \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tedheadster@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).