Searched hist:"89 a80e7400f7225d9401b35ef32454b4ab29dc67" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/qemu/include/exec/ |
| H A D | ioport.h | diff 89a80e7400f7225d9401b35ef32454b4ab29dc67 Wed Mar 16 04:20:34 CDT 2016 Paolo Bonzini <pbonzini@redhat.com> hw: remove pio_addr_t
pio_addr_t is almost unused, because these days I/O ports are simply
accessed through the address space. cpu_{in,out}[bwl] themselves are
almost unused; monitor.c and xen-hvm.c could use address_space_read/write
directly, since they have an integer size at hand. This leaves qtest as
the only user of those functions.
On the other hand even portio_* functions use this type; the only
interesting use of pio_addr_t thus is include/hw/sysbus.h. I guess I
could move it there, but I don't see much benefit in that either. Using
uint32_t is enough and avoids the need to include ioport.h everywhere.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
| /openbmc/qemu/include/hw/ |
| H A D | sysbus.h | diff 89a80e7400f7225d9401b35ef32454b4ab29dc67 Wed Mar 16 04:20:34 CDT 2016 Paolo Bonzini <pbonzini@redhat.com> hw: remove pio_addr_t
pio_addr_t is almost unused, because these days I/O ports are simply
accessed through the address space. cpu_{in,out}[bwl] themselves are
almost unused; monitor.c and xen-hvm.c could use address_space_read/write
directly, since they have an integer size at hand. This leaves qtest as
the only user of those functions.
On the other hand even portio_* functions use this type; the only
interesting use of pio_addr_t thus is include/hw/sysbus.h. I guess I
could move it there, but I don't see much benefit in that either. Using
uint32_t is enough and avoids the need to include ioport.h everywhere.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|
| /openbmc/qemu/hw/core/ |
| H A D | sysbus.c | diff 89a80e7400f7225d9401b35ef32454b4ab29dc67 Wed Mar 16 04:20:34 CDT 2016 Paolo Bonzini <pbonzini@redhat.com> hw: remove pio_addr_t
pio_addr_t is almost unused, because these days I/O ports are simply
accessed through the address space. cpu_{in,out}[bwl] themselves are
almost unused; monitor.c and xen-hvm.c could use address_space_read/write
directly, since they have an integer size at hand. This leaves qtest as
the only user of those functions.
On the other hand even portio_* functions use this type; the only
interesting use of pio_addr_t thus is include/hw/sysbus.h. I guess I
could move it there, but I don't see much benefit in that either. Using
uint32_t is enough and avoids the need to include ioport.h everywhere.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
|