From: Julien Grall <julien.grall@arm.com>
To: Dirk Behme <dirk.behme@de.bosch.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v2] xen/arm: register clocks used by the hypervisor
Date: Fri, 8 Jul 2016 10:21:44 +0100 [thread overview]
Message-ID: <577F70A8.7020406@arm.com> (raw)
In-Reply-To: <373bf006-1a5e-0b2b-278d-d5ec0d8737fd@de.bosch.com>
Hi Dirk,
On 08/07/16 06:51, Dirk Behme wrote:
> On 08.07.2016 04:50, Michael Turquette wrote:
>> Quoting Dirk Behme (2016-07-07 00:32:34)
>> The two issues to resolve are:
>>
>> 1) does consuming these hardware resources from the Linux kernel fit
>> correctly with the Xen model?
>
>
> I think so. Julien, what do you think?
I don't think it fits the Xen model. I will give more details on the v3
as your commit message give an example with is contradictory to the model.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2016-07-08 9:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 10:32 [PATCH v2] xen/arm: register clocks used by the hypervisor Dirk Behme
2016-06-30 14:21 ` Mark Rutland
2016-06-30 14:56 ` [Xen-devel] " Dirk Behme
2016-06-30 15:18 ` Mark Rutland
2016-06-30 15:33 ` Julien Grall
2016-07-05 13:53 ` Stefano Stabellini
2016-07-05 13:54 ` Julien Grall
2016-07-05 14:02 ` Julien Grall
2016-07-05 14:04 ` Stefano Stabellini
2016-07-05 14:08 ` Julien Grall
2016-07-05 14:37 ` Stefano Stabellini
2016-07-06 1:34 ` Michael Turquette
2016-07-06 13:10 ` Julien Grall
2016-07-06 13:16 ` Stefano Stabellini
2016-07-06 13:26 ` Julien Grall
2016-07-06 13:48 ` Mark Rutland
2016-07-06 20:42 ` Michael Turquette
2016-07-07 7:32 ` Dirk Behme
2016-07-08 2:50 ` Michael Turquette
2016-07-08 5:51 ` [Xen-devel] " Dirk Behme
2016-07-08 9:21 ` Julien Grall [this message]
2016-07-08 6:48 ` Dirk Behme
2016-07-08 9:35 ` 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=577F70A8.7020406@arm.com \
--to=julien.grall@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).