Displaying 5 results from an estimated 5 matches for "tolopology".
2020 Mar 03
4
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...e neither.
> There are also systems looking to bypass ACPI e.g. for boot speed.
If there is no firmware layer between the hardware and the OS the
necessary information the OS needs to run on the hardware is probably
hard-coded into the kernel? In that case the same can be done with
virtio-iommu tolopology.
> That sentence doesn't really answer the question, does it?
To be more elaborate, putting this information into config space is a
layering violation. Hardware is never completly self-descriptive and
that is why there is the firmware which provides the information about
the hardware to th...
2020 Mar 03
4
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...e neither.
> There are also systems looking to bypass ACPI e.g. for boot speed.
If there is no firmware layer between the hardware and the OS the
necessary information the OS needs to run on the hardware is probably
hard-coded into the kernel? In that case the same can be done with
virtio-iommu tolopology.
> That sentence doesn't really answer the question, does it?
To be more elaborate, putting this information into config space is a
layering violation. Hardware is never completly self-descriptive and
that is why there is the firmware which provides the information about
the hardware to th...
2020 Mar 03
0
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...o run on the hardware is probably
> hard-coded into the kernel?
No. It's coded into the hardware. Which might even be practical
for bare-metal (e.g. on-board flash), but is very practical
when the device is part of a hypervisor.
> In that case the same can be done with
> virtio-iommu tolopology.
>
> > That sentence doesn't really answer the question, does it?
>
> To be more elaborate, putting this information into config space is a
> layering violation. Hardware is never completly self-descriptive
This "hardware" is actually part of hypervisor so there&...
2020 Mar 03
2
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
Hi Eric,
On Tue, Mar 03, 2020 at 11:19:20AM +0100, Auger Eric wrote:
> Michael has pushed this solution (putting the "configuration in the PCI
> config space"), I think for those main reasons:
> - ACPI may not be supported on some archs/hyps
But on those there is device-tree, right?
> - the virtio-iommu is a PCIe device so binding should not need ACPI
> description
The
2020 Mar 03
2
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
Hi Eric,
On Tue, Mar 03, 2020 at 11:19:20AM +0100, Auger Eric wrote:
> Michael has pushed this solution (putting the "configuration in the PCI
> config space"), I think for those main reasons:
> - ACPI may not be supported on some archs/hyps
But on those there is device-tree, right?
> - the virtio-iommu is a PCIe device so binding should not need ACPI
> description
The