From: wayne gong <wayne.gong@oracle.com>
To: xen-devel@lists.xensource.com
Subject: EVTCHNOP_send crash Windows
Date: Tue, 13 Apr 2010 17:20:22 +0800 [thread overview]
Message-ID: <4BC43756.5020605@oracle.com> (raw)
Hello there,
When I run migration test for my PV drivers, I find that EVTCHNOP_send
hypercall crash windows with error code 0x7F (0x8...)
http://msdn.microsoft.com/en-us/library/ff559244(v=VS.85).aspx
<http://msdn.microsoft.com/en-us/library/ff559244%28v=VS.85%29.aspx>
when system was migrated for more than 500 times. PV drivers can call it
successfully for several times before crash when system is suspending or
resuming. It always happens in some xenstore watch event callback
routine. Such as read/write device state key or state key changing
watcher callback routine. The hypercall didn't return from hypervisor
but windows crashes. I've checked the xenstore base address from share
info and parameter of that hyper call, looks like are fine. So which
situation of that hypercall will crash windows? Which part I should
double check in my PV drivers?
I am using WDK 7600.16385.1, Windows 7 X86, Xen 3.4.0.
BTW, seems that Windows 7 X64 works fine in migration test.
Thanks
Wayne
reply other threads:[~2010-04-13 9:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BC43756.5020605@oracle.com \
--to=wayne.gong@oracle.com \
--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.