From: SuperWong <wang_nets@163.com>
To: xen-devel@lists.xensource.com
Subject: Re: I have used printk in some hypercall.But Dom0 can't be booted.
Date: Thu, 12 Apr 2012 07:46:32 -0700 (PDT) [thread overview]
Message-ID: <1334241992994-5635895.post@n5.nabble.com> (raw)
In-Reply-To: <CAFLBxZa7fha+Hh2v7gY0Cgn8eGmnKhWQ2TCdBtp8wSb8v4kOCg@mail.gmail.com>
George Dunlap-4 wrote
>
> On Sat, Mar 31, 2012 at 2:15 PM, SuperWong <wang_nets@> wrote:
>> Hi all:
>> I wanted to record some information about some hypercalls and trace
>> the
>> hypercalls.So I have tried to add printk in the hypercall.But the Dom0
>> can't
>> be *booted*.For example, I add printk at the beginning of
>> do_set_trap_table.
>> printk("<1>""HYPERCALL:do_set_trap_table");
>> Why I can't add printk in hypercall?
>> Does anyone know the reason and the solution?Thanks.
>
> There's no way we can answer this question without the output of the
> dom0 saying why it failed.
>
> The best way to do this is to set up a serial console:
> http://wiki.xen.org/wiki/Xen_Serial_Console
>
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
>
Thanks so much.I have set up a serial console.Then,I found there were full
of my printk output.It's likely that writing a printk in a hypercall isn't
feasible.I want to record which hypercall is issued when I input insmod.How
should I do it?
--
View this message in context: http://xen.1045712.n5.nabble.com/I-have-used-printk-in-some-hypercall-But-Dom0-can-t-be-booted-tp5608788p5635895.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-04-12 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 13:15 I have used printk in some hypercall.But Dom0 can't be booted SuperWong
2012-04-02 9:00 ` George Dunlap
2012-04-12 14:46 ` SuperWong [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=1334241992994-5635895.post@n5.nabble.com \
--to=wang_nets@163.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).