diff options
author | Bernhard Beschow <shentey@gmail.com> | 2024-01-14 13:39:04 +0100 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2024-02-14 06:09:32 -0500 |
commit | 4edee342f81397e8938ba7a80d1908c5103b66c8 (patch) | |
tree | 6fb37a63661f5be6c62eb5c308086829bd7dde88 /docs/devel | |
parent | ee3d1f1b46e0c304ee4065b3099734158f322860 (diff) | |
download | qemu-4edee342f81397e8938ba7a80d1908c5103b66c8.zip qemu-4edee342f81397e8938ba7a80d1908c5103b66c8.tar.gz qemu-4edee342f81397e8938ba7a80d1908c5103b66c8.tar.bz2 |
exec/ioport: Resolve redundant .base attribute in struct MemoryRegionPortio
portio_list_add_1() creates a MemoryRegionPortioList instance which holds a
MemoryRegion `mr` and an array of MemoryRegionPortio elements named `ports`.
Each element in the array gets assigned the same value for its .base attribute.
The same value also ends up as the .addr attribute of `mr` due to the
memory_region_add_subregion() call. This means that all .base attributes are
the same as `mr.addr`.
The only usages of MemoryRegionPortio::base were in portio_read() and
portio_write(). Both functions get above MemoryRegionPortioList as their
opaque parameter. In both cases find_portio() can only return one of the
MemoryRegionPortio elements of the `ports` array. Due to above observation any
element will have the same .base value equal to `mr.addr` which is also
accessible.
Hence, `mrpio->mr.addr` is equivalent to `mrp->base` and
MemoryRegionPortio::base is redundant and can be removed.
Signed-off-by: Bernhard Beschow <shentey@gmail.com>
Message-Id: <20240114123911.4877-5-shentey@gmail.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'docs/devel')
0 files changed, 0 insertions, 0 deletions