Re: [Qemu-devel] MemoryRegionOps access sizes

[Stefan Hajnoczi]

On Fri, Feb 15, 2019 at 10:55:59AM +0100, BALATON Zoltan wrote:
> 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.

CCing Paolo and Peter, who might know the answer.

Otherwise the easiest way to understand the behavior would be to create
the memory region and try it out using qtest to see what happens in
practice.

Stefan

signature.asc
Description: PGP signature