qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Regression caused by d2f39ad "exec.c: Ensure right alig


From: Haozhong Zhang
Subject: Re: [Qemu-devel] Regression caused by d2f39ad "exec.c: Ensure right alignment also for file backed ram"
Date: Fri, 21 Oct 2016 16:39:08 +0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0

On 10/21/2016 04:28 PM, Haozhong Zhang wrote:
> Hi,
>
> Commit d2f39ad "exec.c: Ensure right alignment also for file backed
> ram" added an additional alignment requirement besides to the previous
> page size for the size of the backend file. On x86, the alignment
> requirement for the size of the backend file is changed from 4KB in
> QEMU 2.6 to 2MB in QEMU 2.7.
>
> This change immediately breaks the usage of "-object
> memory-backend-file,...,size=$SIZE"

I forgot the frontend part, the broken usage should be
    -object memory-backend-file,id=mem1,mem-path=$FILE,size=$SIZE
    -device nvdimm,id=nv1,memdev=mem1
where $SIZE is multiple of 4KB but not 2MB.

It works on QEMU 2.6, but fails on 2.7 when pc_dimm_memory_plug() tries
to plug the nvdimm device.

Haozhong

> on x86, where $SIZE is multiple of 4KB but not 2MB. It works on QEMU 2.6.
> Could this be considered as a regression?
>
> The commit message shows it's for s390. I'm wondering whether the same
> regression happens on s390 and ARM. If not, could I fix the regression
> on x86 by keeping using the original alignment only on x86, e.g.
>
> modified   exec.c
> @@ -1254,7 +1254,11 @@ static void *file_ram_alloc(RAMBlock *block,
>     }
>
>     block->page_size = qemu_fd_getpagesize(fd);
> +#if defined(__x86_64__) || defined(__i386__)
> +    block->mr->align = block->page_size;
> +#else
>     block->mr->align = MAX(block->page_size, QEMU_VMALLOC_ALIGN);
> +#endif
>
>     if (memory < block->page_size) {
>         error_setg(errp, "memory size 0x" RAM_ADDR_FMT " must be equal
> to "
>
>
> Thanks,
> Haozhong
>




reply via email to

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