[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Keystone Issue


  • To: Julien Grall <julien@xxxxxxx>
  • From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
  • Date: Thu, 4 Jun 2020 09:08:26 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UkgxyVdMG3hPkxRUYURCQ8qGCtpJOxqrUT6RtKnXsXA=; b=KZLtmbUqniLHDJU966WUFwLwU09rmuXjF4rbeoHtl00DgK17pPJA76BC7QcO75bgslwieJcV3WwVLnot9aui50KQJ1TnL1WD6vWGB8FqoJyL/ia531+0WOXEri/BaSAMbQr6IiXxjU8aIvRoKkYdWy6QVWGKWSuNJqjqxCs2PK6uusb41rSFIKmPcob9pCB8SeTco6DCM0vqUcTPpD1plAHLyVUe1gUp9gFz2VbnfogogEpP0bm41QNHVgg/vDCe43EUxaspajsbcuY5qRglvmjN2biU4weTu5k0+gr0zLjuZ+d7hl6IB/EWAxVXE77808iPJWRdMn/6DcbRQn6SMw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iEmtfAlPwn8YkEqBs8ujWDsTDXqMCrJ5JrA1Sb2e3W8liWYVs2V9133qj8s6z2U3tSe/YlvQQb99V1L8y80vsITtF1IYaHRXi22fj9VLyXyywEMGL4SqBdOCkzWkHole2BVOQVOkqGi65M+TpPpWaCqVoqDAprFFebf92WtT41xng2GRvL1nHX7ArVyp4fuWqmx+pa/djgqg6VB14zkaljAsVZohF+v1WAefvSOX1/9kpXMM1NY6gsHufdZPPhDuE0q3IG6h4znR9+oFkFdGr7EzfM6Xtv1rFfhBeCG4fFkQizxt3iXilBVE1UvRh3p8io8tkYmBqJldepOCjXy7Ww==
  • Authentication-results-original: xen.org; dkim=none (message not signed) header.d=none;xen.org; dmarc=none action=none header.from=arm.com;
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, nd <nd@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, CodeWiz2280 <codewiz2280@xxxxxxxxx>
  • Delivery-date: Thu, 04 Jun 2020 09:08:46 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: xen.org; dkim=none (message not signed) header.d=none;xen.org; dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHWOBaIAfEL/lLkK0WiNSn4kZcZc6jDwRQAgAAfVYCAACZwgIACvmKAgABfPYCAAA+JgIAA6NEAgAAP9wCAAAJxgA==
  • Thread-topic: Keystone Issue


> On 4 Jun 2020, at 09:59, Julien Grall <julien@xxxxxxx> wrote:
> 
> 
> 
> On 04/06/2020 09:02, Bertrand Marquis wrote:
>> Hi,
> 
> Hi Bertrand,
> 
>>> On 3 Jun 2020, at 19:09, Julien Grall <julien@xxxxxxx> wrote:
>>> 
>>> 
>>> 
>>> On 03/06/2020 18:13, CodeWiz2280 wrote:
>>>> Hi Julien,
>>> 
>>> Hello,
>>> 
>>> In general, we avoid top post on xen-devel, instead we reply inline. I 
>>> believe gmail should allow you to do it :).
>>> 
>>>> The offset is already applied to the memory nodes in the device tree, 
>>>> meaning a direct Linux boot from uboot would have only the 36-bit 
>>>> addresses in the device tree (0x8_0000_0000 and 0x8_8000_0000).  Linux 
>>>> would start executing from a 32-bit address space however and then switch 
>>>> over to the aliased 36-bit addresses in the device tree as discussed below 
>>>> by early_paging_init().
>>>> I had to add the 32-bit memory node 0x8000_0000 in uboot in place of the 
>>>> 0x8_0000_0000 node otherwise Xen would detect the 32-bit processor and 
>>>> panic on "Unable to detect the first memory bank" in domain_build.c.
>>> 
>>> So for 32-bit Xen requires to have the first bank below 4GB. This is 
>>> because you can't boot from a physical address above 32-bit.
>>> 
>>> Obviously, this check wouldn't work on your platform because all your 
>>> memory will be above 4GB.
>> I think that the Keystone board has low memory accessible at 2 different 
>> address (one low and one high).
>> I would here suggest to have a dtb with 2 regions (one under 4GB and one 
>> over) and remove from the region over 4G the area already addressed by the 
>> region under 4GB.
> 
> I thought about this. However, in an earlier reply, David wrote:
> 
> "4. The dom0 kernel will boot from xen if the early_paging_init switch step 
> is skipped, and the low mem stays in 32-bit....but there is a
> problem with the peripherals so this is not an acceptable solution."
> 
> It is not clear to me what sort of issues will arise with the peripherals. 
> But I have assumed that it wouldn't be possible for Dom0 to keep using the 
> memory below 4GB.

I would have thought that linux would have need some memory, even small in the 
32bit space in order to boot.
I could understand that some memory in the low address space needs to be 
reserved by Linux as DMA area for peripherals not supporting 36-bit addresses, 
but the whole low memory sounds like a big restriction.

Would it be possible to have a bit more information on the “problem with 
peripherals” here ?

Cheers
Bertrand


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.