vdpa: stash memory region properties in vars
Next changes uses this variables, so avoid call repeatedly to memory region functions. No functional change intended. Signed-off-by: Eugenio Pérez <eperezma@redhat.com> Message-Id: <20240215103616.330518-2-eperezma@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
This commit is contained in:
parent
c08da86dc4
commit
a55834579a
@ -47,12 +47,14 @@ static bool vhost_vdpa_listener_skipped_section(MemoryRegionSection *section,
|
|||||||
int page_mask)
|
int page_mask)
|
||||||
{
|
{
|
||||||
Int128 llend;
|
Int128 llend;
|
||||||
|
bool is_ram = memory_region_is_ram(section->mr);
|
||||||
|
bool is_iommu = memory_region_is_iommu(section->mr);
|
||||||
|
bool is_protected = memory_region_is_protected(section->mr);
|
||||||
|
|
||||||
if ((!memory_region_is_ram(section->mr) &&
|
/* vhost-vDPA doesn't allow MMIO to be mapped */
|
||||||
!memory_region_is_iommu(section->mr)) ||
|
bool is_ram_device = memory_region_is_ram_device(section->mr);
|
||||||
memory_region_is_protected(section->mr) ||
|
|
||||||
/* vhost-vDPA doesn't allow MMIO to be mapped */
|
if ((!is_ram && !is_iommu) || is_protected || is_ram_device) {
|
||||||
memory_region_is_ram_device(section->mr)) {
|
|
||||||
return true;
|
return true;
|
||||||
}
|
}
|
||||||
|
|
||||||
@ -69,7 +71,7 @@ static bool vhost_vdpa_listener_skipped_section(MemoryRegionSection *section,
|
|||||||
* size that maps to the kernel
|
* size that maps to the kernel
|
||||||
*/
|
*/
|
||||||
|
|
||||||
if (!memory_region_is_iommu(section->mr)) {
|
if (!is_iommu) {
|
||||||
llend = vhost_vdpa_section_end(section, page_mask);
|
llend = vhost_vdpa_section_end(section, page_mask);
|
||||||
if (int128_gt(llend, int128_make64(iova_max))) {
|
if (int128_gt(llend, int128_make64(iova_max))) {
|
||||||
error_report("RAM section out of device range (max=0x%" PRIx64
|
error_report("RAM section out of device range (max=0x%" PRIx64
|
||||||
|
Loading…
x
Reference in New Issue
Block a user