From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chen Baozi <baozich@gmail.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Grall Julien <julien.grall@linaro.org>,
"tim@xen.org Deegan" <tim@xen.org>,
Andre Przywara <andre.przywara@linaro.org>,
List Developer Xen <xen-devel@lists.xen.org>,
Anup Patel <apatel@apm.com>,
Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
Subject: Re: [PATCH] xen: arm: remove hardcoded gnttab location from dom0
Date: Wed, 4 Dec 2013 09:58:31 +0000 [thread overview]
Message-ID: <1386151111.15530.11.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <989ECDAD-08E1-4057-B7D7-9C08ED6F8735@gmail.com>
On Wed, 2013-12-04 at 02:18 +0800, Chen Baozi wrote:
> On Dec 3, 2013, at 23:04, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>
> > The DT provided to guests (including dom0) includes a Xen node which, among
> > other things, describes an MMIO region which can be safely used for grant
> > table mappings (i.e. it is a hole in the physical address space). For domU we
> > provide a hardcoded values based on our hardcoded guest virtual machine
> > layout. However for dom0 we need to fit in with the underlying platform.
> > Leaving this hardcoded was an oversight which on some platforms could result
> > in the grant table overlaying RAM or MMIO regions which are in use by domain
> > 0.
> >
> > For the 4.4 release do as we did with the dom0 evtchn PPI and provide a hook
> > for the platform code to supply a suitable hardcoded address for the platform
> > (derived from reading the data sheet). Platforms which do not provide the hook
> > get the existing address as a default.
> >
> > After 4.4 we should switch to selecting a region of host RAM which is not RAM
> > in the guest address map. This should be more flexible and safer but the patch
> > was looking too complex for 4.4.
> >
> > Platform Gnttab Address
> > ======== ==============
> > exynos5.c 0xb0000000, confirmed with Julien.
> > sunxi.c 0x01d00000, confirmed in data sheet.
> > midway.c 0xff800000, confirmed with Andre, boot tested.
> > vexpress.c 0xb0000000, existing hardcoded value was selected for vexpress.
> > omap5.c 0xb0000000, no datasheet, looks safe in DTB.
> According to OMAP5432 data sheet, 0x80000000~0xbfffffff is the DRAM
> address space. So this is Ok.
If this is DRAM address space then it's not OK -- what if the guest has
RAM mapped there?
Looks like there are reserved regions at 0x4b000000 or 0x58800000, which
ought to be suitable I think.
> Acked-by: Chen Baozi <baozich@gmail.com>
>
> Cheers,
>
> Baozi
next prev parent reply other threads:[~2013-12-04 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 15:04 [PATCH] xen: arm: remove hardcoded gnttab location from dom0 Ian Campbell
2013-12-03 15:20 ` Julien Grall
2013-12-03 15:22 ` Ian Campbell
2013-12-03 15:52 ` Julien Grall
2013-12-03 15:32 ` Andre Przywara
2013-12-03 18:18 ` Chen Baozi
2013-12-04 9:58 ` Ian Campbell [this message]
2013-12-04 14:49 ` Chen Baozi
2013-12-04 7:27 ` Pranavkumar Sawargaonkar
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=1386151111.15530.11.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=andre.przywara@linaro.org \
--cc=apatel@apm.com \
--cc=baozich@gmail.com \
--cc=julien.grall@linaro.org \
--cc=psawargaonkar@apm.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).