From: Arun Sharma <arun.sharma@intel.com>
To: Michael A Fetterman <Michael.Fetterman@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] shadow-fixes.patch
Date: Mon, 30 May 2005 09:33:27 -0700 [thread overview]
Message-ID: <429B4057.7030500@intel.com> (raw)
In-Reply-To: <E1DcCCV-0000L7-00@mta1.cl.cam.ac.uk>
Michael A Fetterman wrote:
> Re #1, below: can you provide a call stack when snapshot_entry_match faults?
> Seems like it's only ever called from __shadow_out_of_sync(), and that
> function
> tests for possible faulting conditions before invoking
> snapshot_entry_match().
> I'm not sure I see how you could be seeing this.
>
This is what the stack trace looked like:
(XEN) EIP: e008:[<ff125037>]
(XEN) EFLAGS: 00010246 CONTEXT: hypervisor
(XEN) eax: fefa2000 ebx: fe31b000 ecx: ffbce0e0 edx: 00000000
(XEN) esi: c0000000 edi: ffbdb080 ebp: 000000b1 esp: ff103f04
(XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008
(XEN) cr0: 00000004 cr3: 00000384
(XEN) Xen stack trace from esp=ff103f04:
(XEN) 3d6e4000 00000c1b c0000000 ffbdb080 fe31b000 bff1b2c4 00000000
ffbdb080
(XEN) ffbda080 ffbcb080 c6cb1000 [ff124b20] ffbda080 c6cb1000
ffbda080 [ff12f601]
(XEN) 07ccc063 00c1b063 01b05063 0000681e ffbda080 c6cb1000 ffbda080
[ff12f04d]
(XEN) ffbda080 c6cb1000 00000002 ffbf7080 ffbda080 004c4b43 00000000
61402178
(XEN) bffff700 bffff6f8 bffff6d8 00000000 bffff6a0 00000001 00185000
c6cbd000
(XEN) c35e4448 00000100 c76daa84 [ff13600d] c6cbd000 ffffffff
c6cbd000 c35e4448
(XEN) 00000100 c76daa84 c6cb1000 00000002 c36a5000 00130000 00000000
0000e008
(XEN) 00000202 00000010 00000010 00000000 00000000 00000000 ffbda080
(XEN) Xen call trace from esp=ff103f04:
(XEN) [<ff124b20>] [<ff12f601>] [<ff12f04d>] [<ff13600d>]
I remember va=c6cb1000 and it was a vmexit due to invlpg ->
shadow_invlpg -> __shadow_sync_va -> __shadow_out_of_sync()
I think the issue is, even though you've verified that it has a valid L2
entry, update_hl2e() hasn't been called. So linear pagetable can still
fault.
-Arun
prev parent reply other threads:[~2005-05-30 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 22:34 [PATCH] shadow-fixes.patch Arun Sharma
2005-05-29 1:02 ` Michael A Fetterman
2005-05-30 16:33 ` Arun Sharma [this message]
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=429B4057.7030500@intel.com \
--to=arun.sharma@intel.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Michael.Fetterman@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.