From: Ian Campbell <Ian.Campbell@citrix.com>
To: harry S <harry2845@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: How to intercept supervisor call using Xen?
Date: Wed, 3 Sep 2014 10:06:22 +0100 [thread overview]
Message-ID: <1409735182.24834.6.camel@citrix.com> (raw)
In-Reply-To: <CAKRHqxYcOq_6UKph7vdmDjxzgy+JOeNsK+RGcO2GXRJWykhxqA@mail.gmail.com>
On Tue, 2014-09-02 at 09:51 +0800, harry S wrote:
> 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.
>
Setting HCR.TGE requires handling a number of general exceptions.
Without more information on what exactly you have done (i.e. the patch
itself) we can't offer any more advice than you are handling something
wrongly.
BTW, HCR.TGE is rather expensive (since it does trap all sorts of
things, including VM controls etc).
Ian.
> 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]
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-03 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 1:51 How to intercept supervisor call using Xen? harry S
2014-09-03 9:06 ` Ian Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-03 1:12 harry2845
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=1409735182.24834.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=harry2845@gmail.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).