From: Kip Macy <kip.macy@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: garbage registers when domain killed by xen
Date: Sat, 7 May 2005 07:10:54 -0700 [thread overview]
Message-ID: <b1fa29170505070710343677e1@mail.gmail.com> (raw)
In-Reply-To: <1bea7043d407c09e23b119c6c278dbe3@cl.cam.ac.uk>
I'm not sure about ecx/edx but I know eip is bad. There are legitimate
cases of trying to call a null function pointer, but I know from the
context that that isn't the case. It appears to be a page fault - but
I don't have trap handlers installed yet.
-Kip
On 5/7/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 7 May 2005, at 02:26, Kip Macy wrote:
>
> > Is it really necessary for xen to overwrite part of a domain's context
> > on a fatal trap?
>
> Which ones are overwritten -- ecx/edx? I'm not sure how that could
> happen but it's clearly a bug rather than intentional.
>
> -- Keir
>
>
next prev parent reply other threads:[~2005-05-07 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 1:26 garbage registers when domain killed by xen Kip Macy
2005-05-07 9:15 ` Keir Fraser
2005-05-07 14:10 ` Kip Macy [this message]
2005-05-07 14:23 ` Kip Macy
2005-05-07 14:56 ` Keir Fraser
2005-05-07 16:02 ` Kip Macy
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=b1fa29170505070710343677e1@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.