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

Re: [PATCH V2] xen/dom0less: Calculate guest DTB size based on MAX_VIRT_CPUS


  • To: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
  • From: Luca Fancellu <Luca.Fancellu@xxxxxxx>
  • Date: Thu, 4 Dec 2025 08:44:41 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 4.158.2.129) smtp.rcpttodomain=epam.com smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=arm.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
  • 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=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=ehfkvZHkUdLZkpqGnHzJx+s1dyrXJ5/mwH9i7SCxMRw=; b=WzdJoXjTnNq1HeKjiYj4ObrZEEiOqUHSI4esFDU3rePDYSX0IQvLye+3WHl4AzNE0Ss5FqX/EV29f1hjN+SP3AZ7uZzPCPYpSQWogAGLaN04F+QEzKHdaRIGEWrbSjH9yl7iJS7+jdgCyTJV9lew7E9ipXR6FwwmklPVgFx7bIq9LtuZtIfuO271lkmK2L22xSwCoy0oD8sVhUs9KL3TY84kCjA41mZXPt72UFSREa4h4lp6MXHepLRiSJu0vnIFLesCinXF4gEl+0uhyiyqA8ZPG8mZ3jBKn+mwwOAnZl7uwYUeBWwPLgxwi4Rz7vhjh8xI65ek8n7BVmKmtFL/Eg==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=ehfkvZHkUdLZkpqGnHzJx+s1dyrXJ5/mwH9i7SCxMRw=; b=UD9qTc8kYrOs1FK1Di7PWgGC9957mxIj0oYZE3vKWlXhKAWy9uxXXjJA+m7J7ULsXnU3HBCiFRPCiDLfkFsv89RYYqv8UQTc9zBe84TD40ZccsyHAcuge0ckWPiqZv/UCeT7jV/kEtQ1yZy07CqJh8N3UJzxFxg1gshi9ZOyIij/lVrxkEoD3T+O4QLFwFNRtam0XSUwVCeyQ9pr5RN6cQDEgw2JHl1avj7vQua5ArMwtj20D7UD9ax02yHJ6qUsPyApZ6lZd6x/VHNI//+PyJ39Q26qLN/E4dOJgE/fdVXw55jBtt73WzXyfMzuuQmj/wKzrGZzCi9FqtbmluKFVA==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=pass; b=JYYPkJ56QNMLcERezwP2JtA3tdHf1ok6AH3faMaJzVuckOzhUrTONE/2zjL/TNcApm1RjmhlCclqaCqMVXfvmh1Q7ZOrwxVLuE2Zmd0zDuJ5l8NKD3HA84iYsfD0HhPlSKxMFe/NLC7rBF2kWRdTnKiSl5bGEFKdixkQur4CkWWDPTfEwIqZC3gwtprfv58Vgjnr3etEJKCh+MUFyQxF5IW3UHgh0z3g0XY8szANs2yiOPloZCSMbi2joPxBtLjNxWzUVkEwAu/Ji5UO3Af8Xf1dqoutO7osxFkHsLz1dgjSFnsD73M7fIwsX1besHMUVRaH4B3EyzrzV+YANZw2jw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=j9uX1iY20emHCCKI/5vIwVqPaqwfqx4jCSt5EI9n5E5Qhu6xlr9m96mmvVbU75v/mB2JfZI6dAf6jY9WMV8QTAEqn1UHj9Rdoo7vZ9SijtLAAwX8tkar/f+Hkm8rgt1c4RozcfnANLOJ1UYQJM6XpwrinOwAAM67sawy0ZSoXdcZF8xo/cPZ7oWiFlAAJQJSL/Gwy95sFc+e0kYvOH/Vid0i6AU6RZqEd/1nTp8Bgb623N6QCyNsT4jCGtvSyzBmuGErN6L8xx8mBP8HUWTjbmiin8TGSmwJX7eq3Hp2ZvhJhRj2KerlunnKmVKCMhDLZTLjjs/aDCPVNXMYniuPWQ==
  • Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
  • Cc: Julien Grall <julien@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>
  • Delivery-date: Thu, 04 Dec 2025 08:45:59 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Nodisclaimer: true
  • Thread-index: AQHcZIbKZWHMCLfhnk2g+3dibmJCCbUQaX2AgAAU4YCAAKzmgA==
  • Thread-topic: [PATCH V2] xen/dom0less: Calculate guest DTB size based on MAX_VIRT_CPUS

Hi Oleksandr,

> 
>> 
>>>    */
>>> -#define DOMU_DTB_SIZE 4096
>>> +#define DOMU_DTB_SIZE (2048 + (MAX_VIRT_CPUS * 128))
>> 
>> On Arm32, MAX_VIRT_CPUS is 8. This means the new DOMU_DTB_SIZE is going 
>> to be smaller than 4096. Why is it ok?
> 
> You are correct to question the impact on Arm32, where MAX_VIRT_CPUS is 
> smaller, leading to a calculated buffer size of 3072 bytes, which is 
> less than the original 4096 bytes.
> 
> Unfortunately, I have no possibility to test on Arm32. But, I do not see 
> much difference between Arm64 and Arm32 in the context of DomU device 
> tree generation by looking into the code.

Let me know what kind of test you need, we have some arm32 setup here (not HW, 
virtual platforms).

Cheers,
Luca




 


Rackspace

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