All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Ferger, Max" <M.Ferger@KOSTAL.COM>,
	Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>,
	Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Subject: Re: Dom0 kernel for Xen4.6 on R-Car H2 (LAGER)
Date: Thu, 22 Oct 2015 16:29:15 +0100	[thread overview]
Message-ID: <562900CB.4030709@citrix.com> (raw)
In-Reply-To: <84130c4eb92d42e89f5dd11d6ca54ead@DEBEMAIL001.kostal.int>

On 22/10/15 16:07, Ferger, Max wrote:
> Hello,

Hi,

> 2) Dom0 kernel is coming up and showing messages:
> 
>> From: Julien Grall [mailto:julien.grall@citrix.com]
>> Sent: Wednesday, October 21, 2015 8:02 PM
>>
>> To be sure, even the patch I attached on the previous mail doesn't help
>> you to get the console?
> 
> The patch works. But now it is obsolete, and reverted.
> 
> My mistake was how I tried to configure the kernel:
> Following the OMAP wiki [1], which I think is a little misleading,
> I appended the CONFIG_XEN* and friends to .config, and called 'make',
> leading to the CONFIG_XEN*-flags to be overwritten by defaults.
> Once configured via menuconfig, Dom0 showed messages all right.

Linux tends to remove the CONFIG_* if it's not able to turn on it's
dependencies.

I usually double check after a 'make oldconfig'.

>> If so, the simplest way to investigate requires the serial driver in Xen
>> to be functional (IIRC it's not the case right now). If you got it, you
>> can type CTRL-a tree times and access to the Xen console.
> 
> This great tool works now.

>> If you have Xen built with debug=y, from the log you sent it seems to be
>> the case, you can use the asm instruction "hvc" to get Xen printing
>> useful information:
>>     - hvc 0xffff will dump the state of the vCPU
>>     - hvc 0xfffd will print the program counter
> 
> Nice to know.  Couldn't find it on the wiki, though.

I documented them in a talk I gave [1] but never took the opportunity to
wikify it.

I will try to do it on the next Document Day.

> I'll update the LAGER board wiki [2] with my findings.

That would be useful, thank you!

Regards,

[1] http://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

-- 
Julien Grall

  reply	other threads:[~2015-10-22 15:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 14:17 Dom0 kernel for Xen4.6 on R-Car H2 (LAGER) Ferger, Max
2015-10-15 14:27 ` Ian Campbell
2015-10-19 12:09   ` Ferger, Max
2015-10-19 12:44     ` Julien Grall
2015-10-20  8:48       ` Ferger, Max
2015-10-20 10:05         ` Julien Grall
2015-10-20 10:47           ` Julien Grall
2015-10-20 11:41             ` Ferger, Max
2015-10-20 11:23       ` Ferger, Max
2015-10-20 21:44         ` Julien Grall
2015-10-21 16:05           ` Ferger, Max
2015-10-21 16:23             ` Julien Grall
2015-10-21 17:20               ` Ferger, Max
2015-10-21 18:01                 ` Julien Grall
2015-10-22 15:07                   ` Ferger, Max
2015-10-22 15:29                     ` Julien Grall [this message]
2015-10-22  8:48                 ` 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=562900CB.4030709@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=M.Ferger@KOSTAL.COM \
    --cc=ian.campbell@citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=oleksandr.tyshchenko@globallogic.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 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.