All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jonathan Fraser <jfraser@broadcom.com>
Cc: Julien Grall <julien.grall@linaro.org>,
	"tim@xen.org" <tim@xen.org>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V2 3/4] xen/arm: Add support for Broadcom 7445D0 A15 platform.
Date: Fri, 3 Oct 2014 16:22:59 +0100	[thread overview]
Message-ID: <1412349779.12695.29.camel@citrix.com> (raw)
In-Reply-To: <3D592480DD42CA41814EC9221D46F45931DDA2EC@SJEXCHMB12.corp.ad.broadcom.com>

On Fri, 2014-10-03 at 15:15 +0000, Jonathan Fraser wrote:
> On Fri, 2014-10-03 at 11:44 +0100, Julien Grall wrote:
> > Hello Jon,
> > 
> > On 02/10/2014 23:16, Jon Fraser wrote:
> > > This code supports the Broadcom 7445D0 32-bit A15 based platform.
> > 
> > While this patch has been acked and applied. Did you check that the (by 
> > default mapped 0xb0000000-0xb0020000) doesn't overlap to the RAM or 
> > another device on your platform?
> > 
> > Regards,
> > 
> 
> I had a question about that.  This is a guest physical address, not the
> machine physical address?

It's guest physical but dom0 is mapped 1:1 so that is somewhat the same
as machine physical in this instance.

>   What are the restrictions?

It just needs to be a hole in the address space which isn't used for
anything else, so not RAM and not MMIO.

Since dom0 is 1:1 mapped for MMIO this means a hole in the machine
address map, or as a last resort an address used by something which
isn't given to dom0.

In 4.6 we are going to sort out a way of finding these addresses
automatically, so the suckitude of having to figure one out will go
away...

> On our current platforms, memory always starts at 0 and we currently
> support between 1 and 6 GB.  There's always a 1GB hole at 0xc0000000.

I suppose this is an MMIO hole? Any free space in thatregion would do.

> However in the future, memory will start at 0x40000000 and extend
> contiguously past 32-bit space for up to 4GB of memory, then segmented
> in 36-bit address space.

In this case I guess the MMIO has moved to 0...0x40000000? Might need to
move the gnttab then too, or maybe we'll have fixed this in the core by
then (fingers crossed!)

> I haven't tried a guest with much more than 1GB of memory, but will
> try that today.
> 
> Thanks,
> Jon
> 
> 

  reply	other threads:[~2014-10-03 15:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 22:57 [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-01 15:28 ` Julien Grall
2014-10-02 22:16   ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Jon Fraser
2014-10-02 22:16     ` [PATCH V2 1/4] xen/arm: Broadcom 7445D0 ARM cpu support Jon Fraser
2014-10-03 10:39       ` Julien Grall
2014-10-02 22:16     ` [PATCH V2 2/4] xen/arm: Update early print console UART address for Broadcom 7445D0 Jon Fraser
2014-10-02 22:16     ` [PATCH V2 3/4] xen/arm: Add support for Broadcom 7445D0 A15 platform Jon Fraser
2014-10-03 10:44       ` Julien Grall
2014-10-03 15:15         ` Jonathan Fraser
2014-10-03 15:22           ` Ian Campbell [this message]
2014-10-03 15:45             ` Jonathan Fraser
2014-10-02 22:16     ` [PATCH V2 4/4] xen/arm/docs: Document Broadcom 7445D0 early printk support Jon Fraser
2014-10-03 10:41       ` Julien Grall
2014-10-03 10:29     ` [PATCH V2 0/4] Add Broadcom 7445D0 A15 board support Ian Campbell
2014-10-03 10:42       ` Julien Grall
2014-10-03 15:03       ` Jonathan Fraser
2014-10-03 15:29         ` Ian Campbell
2014-10-02 12:57 ` [PATCH 1/3] xen/arm: Broadcom 7445D0 ARM cpu support Ian Campbell
2014-10-02 15:09   ` Konrad Rzeszutek Wilk

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=1412349779.12695.29.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jfraser@broadcom.com \
    --cc=julien.grall@linaro.org \
    --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 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.