From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM Xen Bug #45: Is there a solution?
Date: Tue, 24 May 2016 21:05:06 +0100 [thread overview]
Message-ID: <357f38d1-beac-316d-a035-cbaee45e442a@arm.com> (raw)
In-Reply-To: <5744597A.8060503@gmail.com>
On 24/05/2016 14:39, Dirk Behme wrote:
> Hi Julien,
Hello Dirk,
> On 23.05.2016 22:15, Julien Grall wrote:
>> Hello Dirk,
>>
>>> is there a solution for
>>>
>>> arm: domain 0 disables clocks which are in fact being used
>>> http://bugs.xenproject.org/xen/bug/45
>>>
>>> ?
>>>
>>> On an ARM based board I have to use 'clk_ignore_unused' preventing that
>>> Dom0 disables the UART clock for the console UART configured with
>>> console=hvc0.
>>
>> There is no better solution than passing "clk_ignore_unused" on the
>> kernel command line so far.
>
>
> What would be the solution for this issue? The
>
> "propagate any clock related properties from the UART
> node into the Xen hypervisor node"
>
> mentioned in the ticket?
That is correct. Xen would copy the property "clocks" of the UART into
the hypervisor node.
DOM0 would then parse the clocks associated to this node and mark them
as used by Xen (I think CLK_IGNORE_UNUSED could do the job for us).
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-24 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 15:47 ARM Xen Bug #45: Is there a solution? Dirk Behme
2016-05-23 20:15 ` Julien Grall
2016-05-24 13:39 ` Dirk Behme
2016-05-24 20:05 ` Julien Grall [this message]
2016-05-25 15:10 ` Dirk Behme
2016-05-26 9:00 ` Julien Grall
2016-05-27 12:34 ` Dirk Behme
2016-05-31 10:44 ` Julien Grall
[not found] ` <574DC0DC.9040904@gmx.de>
2016-06-21 10:27 ` Dirk Behme
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=357f38d1-beac-316d-a035-cbaee45e442a@arm.com \
--to=julien.grall@arm.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dirk.behme@gmail.com \
--cc=sstabellini@kernel.org \
--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.