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

Re: [PATCH] xen/arm: Skip memory nodes if not enabled


  • To: "leo.yan@xxxxxxxxxx" <leo.yan@xxxxxxxxxx>
  • From: Luca Fancellu <Luca.Fancellu@xxxxxxx>
  • Date: Tue, 26 Sep 2023 09:52:28 +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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=qDJmPYkWBxLI7LMIuGpUjNKZoPx2gSXZLKZHtMWoivo=; b=HQj0wYDpAhris1FJuw+Z8hTZB1eklyZlEEsFgQG3NHlIxYj+h2X4e8fybUAyMQgEKc0XQqqKkZUYsjQRvaiQc6nNF19AYtOqs8KDQP95YzF4nDd0RQV+ccCSR7SGFVjtLiRRLZ6d+eTq2yHzhYHUGzFoR8bsxDgWlfIIuu5JF446n3dvx4qTXEOk2Iziq+ROusR6SLyjJ7G32hZ1wqJ00+ckAt1aL5hrYsUi86neOTsOTo1wsIc6ig9y66E+y8cMFQXAEjbYingxUNNp+MMMtRupzYwxK9Up6C1AKkYBCOsojb1pDqaP5928WHGR5CCIZGAQM1KeOTiWlxStD53F2w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jJk9QTi0NNZVZGgr8a9LITcm+BaD3KYllGr90YhdIoPLTIB14QRiu6n1+lGaDaJMlpaRi73YbQ2Ree9S29h6uWs3A9MojunWJPnehP1TRnp88sMO034eYrAJ47njTE2LLsLUNshR/xuwV1rKkdc2kSXw47hjbu46oq2n5CBW9iudGi681uBkYD8HBjiJz53Ajq7bwk+rThVBldFdRB0Nbd2VzAUWxFkrFkUFuTSQ5Jv420iXvFw3jYoMt5BH6WNEHwCcPScg1lIWS37VdmH17BrPtEGPSLmkfhx8AV4s530Aza6tld3ETILD5KUhMqmteN33fxhbctmpfYSMMlwV1w==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
  • Delivery-date: Tue, 26 Sep 2023 09:52:52 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Thread-index: AQHZ8DsUAeh4H14sIUq1QR77iDXfDrAs3c8A
  • Thread-topic: [PATCH] xen/arm: Skip memory nodes if not enabled


> On 26 Sep 2023, at 06:33, Leo Yan <leo.yan@xxxxxxxxxx> wrote:
> 
> During the Linux kernel booting, an error is reported by the Xen
> hypervisor:
> 
>  (XEN) arch/arm/p2m.c:2202: d0v0: Failing to acquire the MFN 0x1a02dc
> 
> The kernel attempts to use an invalid memory frame number, which can be
> converted to: 0x1a02dc << PAGE_SHIFT, resulting in 0x1_a02d_c000.
> 
> The invalid memory frame falls into a reserved memory node, which is
> defined in the device tree as below:
> 
>  reserved-memory {
>          #address-cells = <0x02>;
>          #size-cells = <0x02>;
>          ranges;
> 
>  ...
> 
>          ethosn_reserved {
>                  compatible = "shared-dma-pool";
>                  reg = <0x01 0xa0000000 0x00 0x20000000>;
>                  status = "disabled";
>                  no-map;
>          };
> 
>  ...
>  };
> 
> Xen excludes all reserved memory regions from the frame management
> through the dt_unreserved_regions() function. On the other hand, the
> reserved memory nodes are passed to the Linux kernel. However, the Linux
> kernel ignores the 'ethosn_reserved' node since its status is
> "disabled". This leads to the Linux kernel to allocate pages from the
> reserved memory range.

I might be wrong, but reading the specifications seems that “status” is not a 
property
of the child nodes of /reserved-memory, so I’m not sure Xen should do something 
about it.

If it is the case, it’s possible that the device tree is wrong in this case.



 


Rackspace

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