qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] MemoryRegionOps access sizes


From: BALATON Zoltan
Subject: [Qemu-devel] MemoryRegionOps access sizes
Date: Fri, 15 Feb 2019 10:55:59 +0100 (CET)
User-agent: Alpine 2.21.9999 (BSF 287 2018-06-16)

Hello,

Could someone please explain how the MemoryRegionOps valid.{min,max}_access_size and unaligned and corresponding impl constraints work and where are these implemented? And in particular if this would work:

static const MemoryRegionOps ops = {
    .read = readfn,
    .write = writefn,
    .valid.min_access_size = 1,
    .valid.max_access_size = 4,
    .impl.min_access_size = 4,
    .impl.max_access_size = 4,
    .endianness = DEVICE_LITTLE_ENDIAN,
};

This is related to this question:
http://lists.nongnu.org/archive/html/qemu-devel/2019-02/msg03157.html
but that's probably ignored in the middle of a thread so I ask separately.

Thank you,
BALATON Zoltan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]