Date: Thu, 14 Jan 2021 22:58:53 +1000 From: Peter Grehan <grehan@freebsd.org> To: Andrei Martin <andrei.cos.martin@gmail.com> Cc: freebsd-arm@freebsd.org, freebsd-virtualization@freebsd.org, Elena Mihailescu <elenamihailescu22@gmail.com>, Darius Mihai <dariusmihaim@gmail.com>, Mihai Carabas <mihai.carabas@gmail.com> Subject: Re: [bhyve][arm64] Number of allowed vcpus Message-ID: <6270e79e-f442-9509-94c7-840779a99cb2@freebsd.org> In-Reply-To: <CAC%2BC28QevGZZhb5trdA=UN-yZp_rLF1pkA8CPhzE3WUuhRv0pw@mail.gmail.com> References: <CAC%2BC28QevGZZhb5trdA=UN-yZp_rLF1pkA8CPhzE3WUuhRv0pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andrei, > While working on enabling multiple virtual cpus for the arm64 virtual > machine > I used the bhyve's "-c N" parameter to create N cpus (it gets only the > cpus, in contrast to the amd64). If N is smaller than the number of cores > described in the device tree it will enable only N and if it's larger it > will enable only the number of cores from the device tree. > > I don't know if it is the best approach. Another way would be to enable all > the cpus from the device tree, no more, no less. > > Do you have any suggestions? My suggestion to generate the device tree based on VM configuration. bhyve on amd64 already does this for ACPI tables. (I do understand that this is more difficult for bhyveload on ARM64 since the device tree has to be known at load time, and bhyveload is only given a subset of parameters: however it may be possible to reserve space at a fixed location and then have bhyve copy a generated table into that region). later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6270e79e-f442-9509-94c7-840779a99cb2>