From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
Matthew Whitehead <tedheadster@gmail.com>,
"H. Peter Anvin" <hpa@zytor.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: Wed, 23 Nov 2016 09:57:27 +0100 [thread overview]
Message-ID: <20161123085640.GA7601@gmail.com> (raw)
In-Reply-To: <CALCETrU4fM1Juy=EDjtueYrbA_YpQv7J8wfPQ_GADo9MDv_5rw@mail.gmail.com>
* Andy Lutomirski <luto@amacapital.net> wrote:
> The SDM says:
>
> If the source operand is an immediate of size less than the operand size, a
> sign-extended value is pushed on the stack. If the source operand is a segment
> register (16 bits) and the operand size is 64-bits, a zero- extended value is
> pushed on the stack; if the operand size is 32-bits, either a zero-extended
> value is pushed on the stack or the segment selector is written on the stack
> using a 16-bit move. For the last case, all recent Core and Atom processors
> perform a 16-bit move, leaving the upper portion of the stack location
> unmodified.
>
> This makes me think that even new processors are quirky.
Oh well ...
Thanks,
Ingo
next prev parent reply other threads:[~2016-11-23 8:58 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
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 [this message]
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=20161123085640.GA7601@gmail.com \
--to=mingo@kernel.org \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=luto@amacapital.net \
--cc=luto@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