public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@kvack.org>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Alexander Graf <alex@csgraf.de>
Subject: Re: hugetlbfs not working
Date: Thu, 27 Mar 2008 18:55:10 -0300	[thread overview]
Message-ID: <20080327215510.GA11511@dmt> (raw)
In-Reply-To: <47EBC6D4.3070803@qumranet.com>

On Thu, Mar 27, 2008 at 06:09:56PM +0200, Avi Kivity wrote:
> Anthony Liguori wrote: 
> >
> > If you don't bail when ftruncate fails, does it work as expected for 
> > you?  Perhaps older versions of hugetlbfs didn't support truncate.
> 
> If you don't truncate, how can you change the file size?  hugetlbfs 
> doesn't support write().
> 
> I vaugely recall using ftruncate() on 2.4.

commit 7aa91e104028b87ff13f5eeb7a0d7ffe7b5a2348
Author: Ken Chen <kenchen@google.com>
Date:   Tue Oct 16 01:26:21 2007 -0700

    hugetlb: allow extending ftruncate on hugetlbfs

    For historical reason, expanding ftruncate that increases file size on
    hugetlbfs is not allowed due to pages were pre-faulted and lack of fault
    handler.  Now that we have demand faulting on hugetlb since 2.6.15, there
    is no reason to hold back that limitation.

    This will make hugetlbfs behave more like a normal fs.  I'm writing a user
    level code that uses hugetlbfs but will fall back to tmpfs if there are no
    hugetlb page available in the system.  Having hugetlbfs specific ftruncate
    behavior is a bit quirky and I would like to remove that artificial
    limitation.

    Signed-off-by: <kenchen@google.com>
    Acked-by: Wiliam Irwin <wli@holomorphy.com>
    Cc: Adam Litke <agl@us.ibm.com>
    Cc: David Gibson <david@gibson.dropbear.id.au>
    Cc: Nishanth Aravamudan <nacc@us.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

mmap() should fail if anything goes wrong with ftruncate and the file
length is not extented on tmpfs.

--- vl.c.orig   2008-03-27 18:51:31.000000000 -0300
+++ vl.c        2008-03-27 18:52:40.000000000 -0300
@@ -8749,11 +8749,7 @@

     memory = (memory+hpagesize-1) & ~(hpagesize-1);

-    if (ftruncate(fd, memory) == -1) {
-       perror("ftruncate");
-       close(fd);
-       return NULL;
-    }
+    ftruncate(fd, memory);

     area = mmap(0, memory, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd, 0);
     if (area == MAP_FAILED) {




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  parent reply	other threads:[~2008-03-27 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 15:10 hugetlbfs not working Alexander Graf
2008-03-27 15:19 ` Avi Kivity
2008-03-27 15:30   ` Alexander Graf
2008-03-27 16:07     ` Anthony Liguori
2008-03-27 16:09       ` Avi Kivity
2008-03-27 16:35         ` Marcelo Tosatti
2008-03-27 21:55         ` Marcelo Tosatti [this message]
     [not found]           ` <47EC9302.40103@qumranet.com>
2008-03-31 17:01             ` Marcelo Tosatti
2008-03-31 17:17               ` Avi Kivity

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=20080327215510.GA11511@dmt \
    --to=marcelo@kvack.org \
    --cc=alex@csgraf.de \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.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