From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled
Date: Mon, 17 Mar 2014 22:03:17 +0000 [thread overview]
Message-ID: <53277125.7030409@linaro.org> (raw)
In-Reply-To: <CANoR_OCpj9zgK=rxXVdoJbfTR4YTeNDB5GhrqpqCPoZnkv1Mdg@mail.gmail.com>
Hello Suriyan,
On 17/03/14 18:10, Suriyan Ramasami wrote:
> Hello Julien and Ian,
> I at last got some output on the console (with some random first
> characters), by doing the below change:
> drivers/tty/hvc/hvc_xen.c:
> - call dom0_write_console(0, str, len) directly.. ie, remove the if
> (xen_domain()) condition. So, this is another issue, why is it not
> recognized as a xen domain ?
xen_domain() is correctly set quite late on ARM. I have already pointed
out this issue when the patch to modify xen_raw_console_write was sent
on the mailing (see https://lkml.org/lkml/2013/10/24/343). But, it seems
that my comment was not considered when the patch was pushed.
Ian Campbell has offered a solution here:
https://lkml.org/lkml/2013/10/26/21, but I never had the time to send it.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-17 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 14:44 ARM: EXYNOS 5410 - DOM0 not being scheduled Suriyan Ramasami
2014-03-16 20:31 ` Julien Grall
2014-03-17 13:17 ` Suriyan Ramasami
2014-03-17 13:21 ` Julien Grall
2014-03-17 13:32 ` Suriyan Ramasami
2014-03-17 13:52 ` Julien Grall
2014-03-17 17:39 ` Suriyan Ramasami
2014-03-17 18:10 ` Suriyan Ramasami
2014-03-17 18:22 ` Suriyan Ramasami
2014-03-17 22:15 ` Julien Grall
2014-03-18 9:52 ` Ian Campbell
2014-03-18 12:04 ` Julien Grall
2014-03-18 13:37 ` Ian Campbell
2014-03-18 15:41 ` Suriyan Ramasami
2014-03-18 16:09 ` Julien Grall
2014-03-17 22:03 ` Julien Grall [this message]
2014-03-17 10:09 ` Ian Campbell
2014-03-17 13:24 ` Suriyan Ramasami
2014-03-17 13:36 ` 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=53277125.7030409@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=suriyan.r@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 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.