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

Re: [PATCH v2 1/2] docs: update hyperlaunch device tree


  • To: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Michal Orzel <michal.orzel@xxxxxxx>
  • Date: Fri, 4 Aug 2023 09:06:53 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=apertussolutions.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); 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=Rkze//lRjPx1EWbTulYsy736B+B6W8ahIeAajZdiYxA=; b=jDha9KlckQ1ob2ZXcSKGxMxRTyosrYWFIa66B+Wy3xVNr1QusycATJy+FBvwOEIp6qUMbKXYLTGAKNkHDKq4zef3gN9fG7HOfvvwnMQ/fWaLybRPRuG+pYO00Vi7zKQqRXjsCG/cQdbAPN6O1ljthfmzIGbC1dhbp/xWpi3ydFPOXC1aXYaUZ3+BG9HkLjmW0Tc/T6tnDHhmTwMGVDgDoSZiXl1tEvnFSmvvodoCMLHRaF1HljlknpwyvLEADPkBGMQDixfcBjlM06GYuj6XA5jpR+4sZ8YqwbUtm3nXXvDS5sJAeci5mJJvShX/YoKXuJzFnnK7Ut6wcN3b2ScK3w==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Eqh+4qcNyMAVPeMXeLDSjZ0djKRQipYX55/KGwb0Hc60t8vdCvjAlL1LLxKGmPj4r4BeMGgLYA7SdQQOperYqRoUUajcdMbH2Hj7PC2vp9np6GHcPY/9i2jQeKnuKBmxfqwPpF0DQnQVPIDBer9e5Wd08A+GHzmYp/rZKoV89YcNaMM3PRhNfWGnqI59mmGawslh03B9qKUJDzsz+Wp7uaNgJGgxw2q1qQxb7cT5hiv8EDr0vC0rWzrviWaFoUnABZQ5YFaH37hdyIrHPMpNU5F6sZ+cZKhTiOv3j+myndMO0ieEcBCvC39BfLOUYoN8plHjElhL+Bo6Nd8ylmOmug==
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>
  • Delivery-date: Fri, 04 Aug 2023 07:07:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi Daniel,

On 03/08/2023 18:57, Daniel P. Smith wrote:
> 
> 
> On 8/3/23 07:45, Michal Orzel wrote:
>> Hi Daniel,
>>
>> On 03/08/2023 12:44, Daniel P. Smith wrote:
>>>
>>>
>>> With on going development of hyperlaunch, changes to the device tree 
>>> definitions
>>> has been necessary. This commit updates the specification for all current 
>>> changes
>>> along with changes expected to be made in finalizing the capability.
>>>
>>> This commit also adds a HYPERLAUNCH section to the MAINTAINERS file and 
>>> places
>>> this documentation under its purview. It also reserves the path
>>> `xen/common/domain-builder` for the hyperlaunch domain builder code base.
>>>
>>> Signed-off-by: Daniel P. Smith <dpsmith@xxxxxxxxxxxxxxxxxxxx>

[...]
>>> +
>>>   memory
>>> -  The amount of memory to assign to the domain, in KBs.
>>> +  The amount of memory to assign to the domain, in KBs. This field uses a 
>>> DTB
>>> +  Reg which contains a start and size. For memory allocation start may or 
>>> may
>>> +  not have significance but size will always be used for the amount of 
>>> memory
>>>     Required.
>>>
>>> +  Format: String  min:<sz> | max:<sz> | <sz>, e.g. "256M"
>> There is a mismatch between the description and above format:
>> - KB vs MB
>> - string vs reg format
>> - the x86 example uses string and Arm uses reg format
> 
> Hmmm. I missed this in the hyperlaunch v1 update. In the original design
> that came from the working group it was going to use a reg as suggest by
> dom0less. During development of v1, we found it was not rich enough to
> express how Dom0 could be allocated memory and switched to a string to
> mirror the dom0 memory hypervisor command line parameter.
On Arm, dom0_mem cmdline parameter is used to specify only size (no min,max)

> 
> A question for those involved with dom0less, is what are the opinions
> about using this form for memory allocation. Is it required/possible to
> be able to instruct the hypervisor what physical address to use as the
> start of a domain's memory?
"memory" dt property is used to specify just amount of memory for domain in KBs 
using reg format.
It is not used to specify the static memory region (with start and size). For 
that, we have another property called "xen,static-mem".
Therefore, it would be possible to switch memory to string but it would not be 
compatible with the current use anymore.

~Michal



 


Rackspace

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