xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: x86_64: Fix double fault stack setup
Date: Thu, 24 May 2012 17:12:50 +0100	[thread overview]
Message-ID: <4FBE5E02.1000400@citrix.com> (raw)
In-Reply-To: <4FBE73DB0200007800085FB7@nat28.tlf.novell.com>

On 24/05/12 16:46, Jan Beulich wrote:
>>>> On 24.05.12 at 17:28, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> Do we actually care about this error from an INT 08?
> Definitely not - the hypervisor doesn't (except in your debugging)
> ever use INT nn, and nothing else can access those gates.

Ok - I will avoid debugging in this fashion in the future.

>
>> I suppose we could check under rip for 0xcd 0x08,
> That's (from my pov) an absolute no-go for the double fault
> handler, even if the above didn't hold.
>
> Jan

Yes.  After further considering, this adds an extra fault in that the
#DF handler would not successfully return, which was being hidden in my
tests by the crash kernel.

What about the entry vector?  It would be safe to do in the case of a
real #DF, and wont really break the int08 case much more than it already is.

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-05-24 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 14:59 x86_64: Fix double fault stack setup Andrew Cooper
2012-05-24 15:14 ` Jan Beulich
2012-05-24 15:28   ` Andrew Cooper
2012-05-24 15:46     ` Jan Beulich
2012-05-24 16:12       ` Andrew Cooper [this message]
2012-05-25 10:35         ` Jan Beulich
2012-05-25 11:04           ` Keir Fraser
2012-05-24 18:04     ` Keir Fraser
2012-05-24 18:15       ` Andrew Cooper

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=4FBE5E02.1000400@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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).