Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Find a way to log meesages from cgo #859

Closed
devimc opened this issue Oct 25, 2018 · 1 comment
Closed

Find a way to log meesages from cgo #859

devimc opened this issue Oct 25, 2018 · 1 comment
Assignees

Comments

@devimc
Copy link

devimc commented Oct 25, 2018

Fix cgo logging system

@devimc devimc self-assigned this Oct 25, 2018
@devimc
Copy link
Author

devimc commented Feb 20, 2019

closing issue, we are not using cgo

@devimc devimc closed this as completed Feb 20, 2019
egernst pushed a commit to egernst/runtime that referenced this issue Feb 9, 2021
Currently, rootBusPath is set as a constant value. Bus this pcie bus path
is not alway static, eg. the rootBus on arm64 is
"/devices/platform/4010000000.pcie/pci0000:00". The address part of
"4010000000.pcie" may vary with the maxMem in qemu so it should not be a
fixed value.

For exmaple:
HIGH PCIE address reserved in qemu on virt is from 0 to 512G. The lower
part of address may be allocated to normal memory. In general, normal memory
is largely less than 256G, so the base address of HIGH PCIE can be 256G.
But, in case the maxmem is large enough, like around 256G, the base address
of HIGH PCIE must be increase, eg. 300G.
In the current implementation of kata-runtime, the maxmem in qemu is the host
memory size. So if the host memory size is large enough, the prefix of the
pci device path name will be different from rootBusPath set in kata-agent which
can lead to failure on device hotplug.

This patch offer a mechanism to create rootBusPath dynamically but only give
implemention for arm64 and return the default value of rootBusPath for other arch.

Fixes: kata-containers#859
Signed-off-by: Jianyong Wu <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant