acpi/crs: Prevent bad ranges for host bridges
Prevent _CRS resources being quietly chopped off and instead throw an assertion. _CRS is used by host bridges to declare regions of io and/or memory that they consume. On some (all?) platforms the host bridge doesn't have PCI header space and so they need some way to convey the information. Signed-off-by: Ben Widawsky <ben.widawsky@intel.com> Message-Id: <20201026193924.985014-1-ben.widawsky@intel.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Acked-by: Igor Mammedov <imammedo@redhat.com>
This commit is contained in:
parent
384c2561bd
commit
acab9d8a9e
|
@ -866,6 +866,8 @@ static Aml *build_crs(PCIHostState *host, CrsRangeSet *range_set)
|
|||
crs_range_merge(temp_range_set.mem_ranges);
|
||||
for (i = 0; i < temp_range_set.mem_ranges->len; i++) {
|
||||
entry = g_ptr_array_index(temp_range_set.mem_ranges, i);
|
||||
assert(entry->limit <= UINT32_MAX &&
|
||||
(entry->limit - entry->base + 1) <= UINT32_MAX);
|
||||
aml_append(crs,
|
||||
aml_dword_memory(AML_POS_DECODE, AML_MIN_FIXED,
|
||||
AML_MAX_FIXED, AML_NON_CACHEABLE,
|
||||
|
|
Loading…
Reference in a new issue