All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Tim Deegan <tim@xen.org>, Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] xen/tools: Introduce QNX IFS loader
Date: Thu, 18 Sep 2014 12:11:06 -0700	[thread overview]
Message-ID: <541B2E4A.60502@linaro.org> (raw)
In-Reply-To: <CAJEb2DH48+VSvzZkpLW_i3vP-cF4bMfx7qXTZaSt-AHS3OZC_w@mail.gmail.com>

Hi Oleksandr,

On 18/09/14 03:55, Oleksandr Tyshchenko wrote:
>> Also, it looks like that with this solution, the QNX image will be tight to
>> a specific version of Xen. Indeed, you have to specify the physical address
>> in the QNX image.
>
> I just specify the starting address in buildfile which shiped with
> BSP. The starting address is the base address of the image.
> In our case we have next image attribute:
> [image=0x80008000]

This RAM base address has changed in Xen 4.5. I suspect you are trying 
this patch on top of Xen 4.4, right?

If so, it would be nice if you can try this patch also on Xen 4.5.

> This is one of the required actions for QNX to load on top of XEN.
> Yes, if the rambase addr changes in XEN, I will need to change the
> image attr in QNX.

Is it possible to make QNX position independent?

If not, I would add a check that the load address is effectively part of 
the RAM and throw an error if it's not the case.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-09-18 19:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 16:34 [PATCH v2] xen/tools: Introduce QNX IFS loader Oleksandr Tyshchenko
2014-09-17 16:34 ` Oleksandr Tyshchenko
2014-09-17 17:59   ` Julien Grall
2014-09-18  1:50     ` Ian Campbell
2014-09-18 13:16       ` Oleksandr Tyshchenko
2014-09-18 17:39         ` Ian Campbell
2014-09-19 15:45           ` Oleksandr Tyshchenko
2014-09-22 13:09             ` Ian Campbell
2014-09-22 14:23               ` Oleksandr Tyshchenko
2014-09-22 15:09                 ` Oleksandr Tyshchenko
2014-09-22 15:13                   ` Ian Campbell
2014-09-18 10:55     ` Oleksandr Tyshchenko
2014-09-18 19:11       ` Julien Grall [this message]
2014-09-19 16:45         ` Oleksandr Tyshchenko
2014-09-22 13:03           ` Ian Campbell
2014-09-22 15:08             ` Oleksandr Tyshchenko
2014-09-17 17:36 ` Julien Grall
2014-09-18 10:11   ` Oleksandr Tyshchenko

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=541B2E4A.60502@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=oleksandr.tyshchenko@globallogic.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 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.