From: harry2845 <harry2845@gmail.com>
To: xen-devel@lists.xensource.com
Subject: How to intercept supervisor call using Xen?
Date: Tue, 2 Sep 2014 18:12:09 -0700 (PDT) [thread overview]
Message-ID: <1409706729235-5724551.post@n5.nabble.com> (raw)
After reading the document of ARM, I set HCR.TGE to 1 at the init time.
WRITE_SYSREG(HCR_TGE|HCR_PTW|HCR_BSU_OUTER|HCR_AMO|HCR_IMO|HCR_VM|HCR_TWI|HCR_TSC|
HCR_TAC, HCR_EL2);
And I add a case in the function do_trap_hyperviosr.
But after modifying, there will be a kernel panic when I execute Xen.
[ 7.866384] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[ 7.866384]
[ 7.881866] CPU: 0 PID: 1 Comm: init Not tainted 3.15.0-rc5+ #91
[ 7.891024] [<80017dc4>] (unwind_backtrace) from [<800138f8>]
(show_stack+0x20/0x24)
[ 7.903640] [<800138f8>] (show_stack) from [<807864a4>]
(dump_stack+0x70/0xc0)
[ 7.915213] [<807864a4>] (dump_stack) from [<80781030>]
(panic+0x9c/0x204)
[ 7.926088] [<80781030>] (panic) from [<8002c900>] (do_exit+0x86c/0x9f0)
[ 7.936615] [<8002c900>] (do_exit) from [<8002cbc0>]
(do_group_exit+0x4c/0xcc)
[ 7.948188] [<8002cbc0>] (do_group_exit) from [<8003b5dc>]
(get_signal_to_deliver+0x37c/0x71c)
[ 7.962535] [<8003b5dc>] (get_signal_to_deliver) from [<80780aec>]
(do_signal+0xb4/0x380)
[ 7.976013] [<80780aec>] (do_signal) from [<800131a8>]
(do_work_pending+0x8c/0xe0)
[ 7.988278] [<800131a8>] (do_work_pending) from [<8000f680>]
(work_pending+0xc/0x20)
[ 8.000901] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[ 8.000901]
--
View this message in context: http://xen.1045712.n5.nabble.com/How-to-intercept-supervisor-call-using-Xen-tp5724551.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next reply other threads:[~2014-09-03 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 1:12 harry2845 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-02 1:51 How to intercept supervisor call using Xen? harry S
2014-09-03 9:06 ` Ian Campbell
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=1409706729235-5724551.post@n5.nabble.com \
--to=harry2845@gmail.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 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).