From: Igor Mammedov <imammedo@redhat.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>
Cc: qemu-devel@nongnu.org, chao.p.peng@intel.com,
Eduardo Habkost <ehabkost@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Dominik Dingel <dingel@linux.vnet.ibm.com>,
anthony.xu@intel.com, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Regression caused by d2f39ad "exec.c: Ensure right alignment also for file backed ram"
Date: Mon, 24 Oct 2016 13:44:55 +0200 [thread overview]
Message-ID: <20161024134455.64508943@nial.brq.redhat.com> (raw)
In-Reply-To: <20161021082801.dglwfsocljohquok@hz-desktop>
On Fri, 21 Oct 2016 16:28:01 +0800
Haozhong Zhang <haozhong.zhang@intel.com> 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"
> 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.
I don't see a nice way to work around this regression, so perhaps
we should tree 2.7 as broken (wrt migration when *dimm devices with file
backends with pagesize < 2Mb are used) and unbreak 2.8 and onwards.
Could you send a proper patch to list with commit message
explaining what is broken and how + CLI example.
>
> 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);
maybe it's worth to do other way around i.e. for special s390 case
do above and for the rest leave page_size alignment?
> +#endif
>
> if (memory < block->page_size) {
> error_setg(errp, "memory size 0x" RAM_ADDR_FMT " must be equal to "
>
>
> Thanks,
> Haozhong
>
next prev parent reply other threads:[~2016-10-24 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 8:28 [Qemu-devel] Regression caused by d2f39ad "exec.c: Ensure right alignment also for file backed ram" Haozhong Zhang
2016-10-21 8:39 ` Haozhong Zhang
2016-10-21 12:44 ` Igor Mammedov
2016-10-21 14:12 ` Igor Mammedov
2016-10-24 11:44 ` Igor Mammedov [this message]
2016-10-24 12:06 ` Haozhong Zhang
2016-10-24 12:33 ` Dominik Dingel
2016-10-24 12:57 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161024134455.64508943@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=anthony.xu@intel.com \
--cc=chao.p.peng@intel.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dingel@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).