From: Stas Sergeev <stsp@aknet.ru>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Zachary Amsden <zach@vmware.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: + espfix-code-cleanup.patch added to -mm tree
Date: Wed, 02 Aug 2006 23:31:30 +0400 [thread overview]
Message-ID: <44D0FD92.9010202@aknet.ru> (raw)
In-Reply-To: <200608021515_MC3-1-C6D7-2B90@compuserve.com>
Hi.
Chuck Ebbert wrote:
> Only problem I have with this is we lose the original fault info from
> the iret. So we have no real way of knowing whether it was #GP, #NP, #SF
> or whatever, and no record of the offending iret's address.
Thanks for the precise explanation.
There was also a problem with me reading the Intel's manual:
it uses Pop() in their pseudo-code, and it Pop()'s the values
*before* checking them. The description of the Pop() is very
confusing:
---
Pop() removes the value from the top of the stack and returns it.
---
What "removes" means here is unclear. Whether it adjusts a stack
pointer, is unclear. Since it is Pop(), I was assuming "removes"
means it also adjusts the stack pointer, but now I see it was a
wrong guess.
next prev parent reply other threads:[~2006-08-02 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 19:14 + espfix-code-cleanup.patch added to -mm tree Chuck Ebbert
2006-08-02 19:31 ` Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-12 2:27 Chuck Ebbert
2006-08-12 10:35 ` Stas Sergeev
[not found] <200607300016.k6U0GYu4023664@shell0.pdx.osdl.net>
[not found] ` <44CE766D.6000705@vmware.com>
2006-08-01 12:21 ` Stas Sergeev
2006-08-01 13:38 ` Jan Beulich
2006-08-01 14:37 ` Stas Sergeev
2006-08-01 14:43 ` Jan Beulich
2006-08-01 15:09 ` Stas Sergeev
2006-08-01 21:01 ` Zachary Amsden
2006-08-02 17:12 ` Stas Sergeev
2006-08-02 18:30 ` Zachary Amsden
2006-08-02 19:12 ` Stas Sergeev
2006-08-01 2:24 Chuck Ebbert
2006-08-01 12:39 ` Stas Sergeev
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=44D0FD92.9010202@aknet.ru \
--to=stsp@aknet.ru \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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 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.