From: Volodymyr Babchuk <vlad.babchuk@gmail.com>
To: Jayadev Kumaran <jayadevk123@gmail.com>
Cc: Andrii Anisov <andrii_anisov@epam.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Unable to create guest PV domain on OMAP5432
Date: Fri, 17 Nov 2017 14:15:45 +0200 [thread overview]
Message-ID: <CAOcqxo2=fQh5vWWMH9Vugqm+a67M3CChS4aSCDvqN2jBR36jHg@mail.gmail.com> (raw)
In-Reply-To: <a07d3eb9-e885-690a-8f57-0c291bfd5c62@epam.com>
Hi Jayadev,
On 17 November 2017 at 13:53, Andrii Anisov <andrii_anisov@epam.com> wrote:
>>
>> Is there a way to debug which one of the above two possibilities has lead
>> to the issue ?
>
> Four years ago I did it in a following way:
> - wire up to UART2 pins on an expansion connector (this sheet might be
> useful for you: http://www.ti.com/lit/ug/swcu130/swcu130.pdf)
> - assign UART2 IOMEM ranges to DomU
> - enable in domu kernel earlyprintk and patch it to output to omap UART2
>
> Nowadays assigning UART2 IOMEM ranges might be a bit more complex due to XEN
> evolution.
>
> Another way is to use JTAG which understands virtualization, and allows you
> to debug DomU.
I want to add some debugging techniques:
- By tapping CTRL+A three times to switch to XEN console. Then `d`
will show you CPU register states. You will be able to see where your
DomU executes right now. This can help along with addr2line, objdump
and other tools.
- You can modify traps.c in XEN to crash domain when SMC instruction
is trapped. Then you can put SMC invocation into various parts of
kernel code, to see if it reaches that place. This can help on early
stages, when console is not available.
--
WBR Volodymyr Babchuk aka lorc [+380976646013]
mailto: vlad.babchuk@gmail.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-17 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 5:17 Unable to create guest PV domain on OMAP5432 Jayadev Kumaran
2017-11-08 14:52 ` Konrad Rzeszutek Wilk
2017-11-09 6:39 ` Jayadev Kumaran
2017-11-09 6:43 ` Jayadev Kumaran
2017-11-17 18:54 ` Julien Grall
2017-11-09 14:52 ` Andrii Anisov
2017-11-15 6:08 ` Jayadev Kumaran
2017-11-15 10:15 ` Andrii Anisov
2017-11-15 10:46 ` Jayadev Kumaran
2017-11-15 11:01 ` Andrii Anisov
2017-11-15 11:34 ` Jayadev Kumaran
2017-11-17 11:53 ` Andrii Anisov
2017-11-17 12:15 ` Volodymyr Babchuk [this message]
2017-11-17 19:00 ` Julien Grall
2017-11-17 19:11 ` Julien Grall
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='CAOcqxo2=fQh5vWWMH9Vugqm+a67M3CChS4aSCDvqN2jBR36jHg@mail.gmail.com' \
--to=vlad.babchuk@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=jayadevk123@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).