From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH 7/7] xen/arm: Blacklist some sun7i UARTs
Date: Fri, 27 Sep 2013 18:02:09 +0100 [thread overview]
Message-ID: <5245BA11.1080903@linaro.org> (raw)
In-Reply-To: <1379860820.30708.18.camel@dagon.hellion.org.uk>
On 09/22/2013 03:40 PM, Ian Campbell wrote:
> On Sat, 2013-09-21 at 21:28 +0100, Julien Grall wrote:
>> On 09/20/2013 10:41 PM, Ian Campbell wrote:
>>> On Fri, 2013-09-20 at 20:02 +0100, Julien Grall wrote:
>>>
>>>>> + /*
>>>>> + * These UARTs share a page with the Xen console UART, so we don't
>>>>> + * want to map them through.
>>>>> + */
>>>>> + DT_MATCH_PATH("/soc@01c00000/serial@01c28000"),
>>>>> + DT_MATCH_PATH("/soc@01c00000/serial@01c28400"),
>>>>> + DT_MATCH_PATH("/soc@01c00000/serial@01c28800"),
>>>>> + DT_MATCH_PATH("/soc@01c00000/serial@01c28c00"),
>>>>
>>>> Can we blacklist all the UARTs via a DT_MATCH_COMPATIBLE? It's better
>>>> than relying on the path that can be changed easily in the device tree.
>>>
>>> There are other UARTS (at 0x1c29xxx) which could safely be exposed to
>>> dom0. Perhaps it is better to just blacklist the whole lot though.
>>
>> These UARTs also share the same page, what prevents the user to use
>> these UARTs?
>
> Nothing, but because they don't share a page with the xen UART they
> don't cause it to get exposed to dom0.
My question wasn't clear. What does prevent the user to use another UART
for Xen?
--
Julien Grall
next prev parent reply other threads:[~2013-09-27 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 16:17 [PATCH v3 0/7] support for cubieboard2 / sunxi processors Ian Campbell
2013-09-20 16:18 ` [PATCH 1/7] xen/arm: Implement ioremap Ian Campbell
2013-09-20 16:18 ` [PATCH 3/7] ns16550: make usable on ARM Ian Campbell
2013-09-20 16:18 ` [PATCH 4/7] ns16550: support DesignWare 8250 Ian Campbell
2013-09-20 16:18 ` [PATCH 5/7] xen/arm: Support Cortex-A7 GIC Ian Campbell
2013-09-20 18:51 ` Julien Grall
2013-09-20 16:18 ` [PATCH 6/7] xen/arm: Basic support for sunxi/sun7i platform Ian Campbell
2013-09-20 18:55 ` Julien Grall
2013-09-20 19:01 ` Ian Campbell
2013-10-08 9:50 ` Ian Campbell
2013-10-10 14:23 ` Julien Grall
2013-10-11 8:31 ` Ian Campbell
2013-09-20 16:18 ` [PATCH 7/7] xen/arm: Blacklist some sun7i UARTs Ian Campbell
2013-09-20 19:02 ` Julien Grall
2013-09-20 21:41 ` Ian Campbell
2013-09-21 20:28 ` Julien Grall
2013-09-22 14:40 ` Ian Campbell
2013-09-27 17:02 ` Julien Grall [this message]
2013-09-27 17:04 ` Andrew Cooper
2013-09-30 9:19 ` Ian Campbell
2013-09-21 15:59 ` [PATCH v3 0/7] support for cubieboard2 / sunxi processors 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=5245BA11.1080903@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.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 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).