xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com,
	stefano.stabellini@citrix.com, patches@linaro.org
Subject: Re: [PATCH] libxc/arm: Correctly handle the difference between virtual and physical address
Date: Wed, 11 Dec 2013 19:26:18 +0000	[thread overview]
Message-ID: <52A8BC5A.9080406@linaro.org> (raw)
In-Reply-To: <1386756142.30271.14.camel@kazak.uk.xensource.com>

On 12/11/2013 10:02 AM, Ian Campbell wrote:
> On Tue, 2013-12-10 at 18:16 +0000, Julien Grall wrote:
>> This issue is when as virt == phys, build ELF with virt != phys is very difficult.
> 
> OK, so I think I was mislead by your commit message, this is not
> actually about virt vs phys as such (or as represented in the ELF
> header) but is actually more about link address vs. load address. Where
> link address == ELF vaddr (==paddr). And because the MMU is disable load
> address == some vaddr (==paddr), which may differ from the ELF vaddr.
> 
> The terminology in xc_dom, which uses vaddr a lot because of PV x86,
> isn't helpful here but is that an accurate summary?

Right, and this address is actually equal to ELF vaddr. But the device
tree base address will be computed with the physical address.

> [...]
>> When the guest is creating, the ELF should loaded like zImage at the specific
>> physical address.
> 
> So that would be my next question -- where does this load address come
> from?

Load address ? Virtual ? Physical ?

> I suppose it has to be the 0x80100000 kernel physical address you gave
> earlier?
> 
> I think this means "where is dom->parms.virt_base" initialised. Have you
> added some ELF notes to your BSD kernel image?

I have tried to play with the ELF notes. My current configuration is:

XEN_ELFNOTE_VIRT_BASE    vaddr   	(0xC0000000)
XEN_ELFNOTE_PADDR_OFFSET vaddr		(0xC0000000)

It's copied from Linux.

If I try to modify PADDR_OFFSET with (KERNBASE - PHYSADDR) or whatever
value it doesn't work. I got
"segment kernel too large (0x355 > 0x4000 - 0x80100 pages): Out of memory".

>>  Then the guest will start will MMU turn off, and during the
>> first instructions it will use fixup to get the right address.
> 
> "fixup" == enable the MMU, or "fixup" == some sort of relocation/PIC?

Some sort of relocation. When MMU is turn off, every time the kernel
needs to call asm callback, it will add an offset.

-- 
Julien Grall

  reply	other threads:[~2013-12-11 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 17:36 [PATCH] libxc/arm: Correctly handle the difference between virtual and physical address Julien Grall
2013-12-10 17:44 ` Ian Campbell
2013-12-10 18:16   ` Julien Grall
2013-12-11 10:02     ` Ian Campbell
2013-12-11 19:26       ` Julien Grall [this message]
2013-12-12 10:35         ` Ian Campbell
2013-12-12 13:55           ` Julien Grall
2013-12-12 14:36             ` 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=52A8BC5A.9080406@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=patches@linaro.org \
    --cc=stefano.stabellini@citrix.com \
    --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).