All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Dominik Dingel <dingel@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Halil Pasic <pasic@linux.vnet.ibm.com>,
	Richard Henderson <rth@twiddle.net>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] exec.c: Ensure right alignment also for file backed ram
Date: Tue, 3 May 2016 08:57:33 +0800	[thread overview]
Message-ID: <20160503005733.GS1421@ad.usersys.redhat.com> (raw)
In-Reply-To: <20160429102603.29310efa@BR9TG4T3.de.ibm.com>

On Fri, 04/29 10:26, Dominik Dingel wrote:
> On Fri, 29 Apr 2016 15:32:22 +0800
> Fam Zheng <famz@redhat.com> wrote:
> 
> > On Mon, 04/25 13:55, Dominik Dingel wrote:
> > > While in the anonymous ram case we already take care of the right alignment
> > > such an alignment gurantee does not exist for file backed ram allocation.
> > 
> > s/gurantee/guarantee/
> > 
> > Otherwise looks good to me,
> > 
> > Reviewed-by: Fam Zheng <famz@redhat.com>
> 
> Thank you very much!
> 
> Paolo do you want me to fix the typo, add the r-b and resend the patch?

Paolo is still travelling this week, you can do that if you feel like to, or I
guess he can fix it himself when applying later.

Fam

> 
> > > 
> > > Instead, pagesize is used for alignment. On s390 this is not enough for gmap,
> > > as we need to satisfy an alignment up to segments.
> > > 
> > > Reported-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> > > Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
> > > 
> > > ---
> > > 
> > > v2 -> v3:
> > > Skipping additional variable and just use alignment of memory region.
> > > As memory will not be backpropagated it is enough to round up to page_sizes.
> > > 
> > > v1 -> v2:
> > > While enforcing alignments we allow memory sizes on page_size.
> > > On mmap the memory size will be round up to alignments.
> > > 
> > > I thought about moving this alignment into qemu_ram_mmap but the result
> > > was a lot of code churn, the other possibility was to create an additional
> > > define ending up with two defines with the same semantics.
> > > ---
> > >  exec.c               |  5 +++--
> > >  include/qemu/osdep.h | 13 +++++++++++++
> > >  util/oslib-posix.c   | 13 -------------
> > >  3 files changed, 16 insertions(+), 15 deletions(-)
> > > 
> > > diff --git a/exec.c b/exec.c
> > > index c4f9036..fc75266 100644
> > > --- a/exec.c
> > > +++ b/exec.c
> > > @@ -1296,7 +1296,7 @@ static void *file_ram_alloc(RAMBlock *block,
> > >      }
> > >  
> > >      page_size = qemu_fd_getpagesize(fd);
> > > -    block->mr->align = page_size;
> > > +    block->mr->align = MAX(page_size, QEMU_VMALLOC_ALIGN);
> > >  
> > >      if (memory < page_size) {
> > >          error_setg(errp, "memory size 0x" RAM_ADDR_FMT " must be equal to "
> > > @@ -1317,7 +1317,8 @@ static void *file_ram_alloc(RAMBlock *block,
> > >          perror("ftruncate");
> > >      }
> > >  
> > > -    area = qemu_ram_mmap(fd, memory, page_size, block->flags & RAM_SHARED);
> > > +    area = qemu_ram_mmap(fd, memory, block->mr->align,
> > > +                         block->flags & RAM_SHARED);
> > >      if (area == MAP_FAILED) {
> > >          error_setg_errno(errp, errno,
> > >                           "unable to map backing store for guest RAM");
> > > diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> > > index 408783f..783270f 100644
> > > --- a/include/qemu/osdep.h
> > > +++ b/include/qemu/osdep.h
> > > @@ -247,6 +247,19 @@ void qemu_anon_ram_free(void *ptr, size_t size);
> > >  
> > >  #endif
> > >  
> > > +#if defined(__linux__) && \
> > > +    (defined(__x86_64__) || defined(__arm__) || defined(__aarch64__))
> > > +   /* Use 2 MiB alignment so transparent hugepages can be used by KVM.
> > > +      Valgrind does not support alignments larger than 1 MiB,
> > > +      therefore we need special code which handles running on Valgrind. */
> > > +#  define QEMU_VMALLOC_ALIGN (512 * 4096)
> > > +#elif defined(__linux__) && defined(__s390x__)
> > > +   /* Use 1 MiB (segment size) alignment so gmap can be used by KVM. */
> > > +#  define QEMU_VMALLOC_ALIGN (256 * 4096)
> > > +#else
> > > +#  define QEMU_VMALLOC_ALIGN getpagesize()
> > > +#endif
> > > +
> > >  int qemu_madvise(void *addr, size_t len, int advice);
> > >  
> > >  int qemu_open(const char *name, int flags, ...);
> > > diff --git a/util/oslib-posix.c b/util/oslib-posix.c
> > > index 6cc4b8f..4adde93 100644
> > > --- a/util/oslib-posix.c
> > > +++ b/util/oslib-posix.c
> > > @@ -26,19 +26,6 @@
> > >   * THE SOFTWARE.
> > >   */
> > >  
> > > -#if defined(__linux__) && \
> > > -    (defined(__x86_64__) || defined(__arm__) || defined(__aarch64__))
> > > -   /* Use 2 MiB alignment so transparent hugepages can be used by KVM.
> > > -      Valgrind does not support alignments larger than 1 MiB,
> > > -      therefore we need special code which handles running on Valgrind. */
> > > -#  define QEMU_VMALLOC_ALIGN (512 * 4096)
> > > -#elif defined(__linux__) && defined(__s390x__)
> > > -   /* Use 1 MiB (segment size) alignment so gmap can be used by KVM. */
> > > -#  define QEMU_VMALLOC_ALIGN (256 * 4096)
> > > -#else
> > > -#  define QEMU_VMALLOC_ALIGN getpagesize()
> > > -#endif
> > > -
> > >  #include "qemu/osdep.h"
> > >  #include <termios.h>
> > >  #include <termios.h>
> > > -- 
> > > 2.6.6
> > > 
> > > 
> > 
> 

  reply	other threads:[~2016-05-03  0:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 11:55 [Qemu-devel] [PATCH] exec.c: Ensure right alignment also for file backed ram Dominik Dingel
2016-04-29  7:32 ` Fam Zheng
2016-04-29  8:26   ` Dominik Dingel
2016-05-03  0:57     ` Fam Zheng [this message]
2016-05-10 13:16 ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2016-03-23 21:32 Dominik Dingel
2016-03-24 11:35 ` Paolo Bonzini
2016-03-29  9:29   ` Dominik Dingel
2016-03-29  9:51     ` 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=20160503005733.GS1421@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=dingel@linux.vnet.ibm.com \
    --cc=pasic@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.