On Mon, Feb 02, 2026 at 12:29:12AM +0100, Philippe Mathieu-Daudé wrote:
> This series eliminates target specifics in hw/virtio and replace them
> with runtime functions where needed.


This is not bad at all. I feel we do need to have the performance impact
tested, however, just to be sure, since it's probably the hottest path
for I/O.


> v3:
> - include missing SPAPR_MAX_RAM_SLOTS patch
> v2:
> - Reduce runtime calls for performance
> v1:
> https://lore.kernel.org/qemu-devel/[email protected]/
> 
> Philippe Mathieu-Daudé (6):
>   hw/virtio: Constify virtio_is_big_endian() argument
>   hw/virtio: Introduce VirtIODevice::access_is_big_endian boolean field
>   hw/virtio: Use VirtIODevice::access_is_big_endian field
>   hw/virtio: Reduce virtio_access_is_big_endian() scope
>   hw/virtio: Check target supports legacy bi-endianness at runtime
>   hw/virtio: Replace TARGET_BIG_ENDIAN -> target_big_endian()
> 
> Pierrick Bouvier (5):
>   target-info: add target_base_ppc, target_ppc and target_ppc64
>   hw/ppc/spapr: extract SPAPR_MAX_RAM_SLOTS in a new header
>   hw/virtio/vhost-user: make compilation unit common
>   hw/virtio/virtio-qmp: make compilation unit common
>   hw/virtio: make all compilation units common
> 
>  include/hw/ppc/spapr.h            |  8 +---
>  include/hw/ppc/spapr_common.h     | 17 ++++++++
>  include/hw/virtio/virtio-access.h | 46 ++++++--------------
>  include/hw/virtio/virtio.h        |  7 +++-
>  include/qemu/target-info.h        | 21 ++++++++++
>  hw/virtio/vhost-user.c            | 11 ++---
>  hw/virtio/virtio-qmp.c            | 70 -------------------------------
>  hw/virtio/virtio.c                | 25 ++++++++++-
>  target-info.c                     | 21 ++++++++++
>  hw/virtio/meson.build             | 17 ++++----
>  10 files changed, 113 insertions(+), 130 deletions(-)
>  create mode 100644 include/hw/ppc/spapr_common.h
> 
> -- 
> 2.52.0


Reply via email to