All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCH unit-tests] Add async page fault test
Date: Wed, 9 May 2012 11:59:17 +0300	[thread overview]
Message-ID: <20120509085917.GR15960@redhat.com> (raw)
In-Reply-To: <4FAA3059.2040105@redhat.com>

On Wed, May 09, 2012 at 11:52:41AM +0300, Avi Kivity wrote:
> On 05/09/2012 11:41 AM, Gleb Natapov wrote:
> > > 
> > > >  void vfree(void *mem)
> > > >  {
> > > >      unsigned long size = ((unsigned long *)mem)[-1];
> > > > diff --git a/lib/x86/vm.h b/lib/x86/vm.h
> > > > index 71ab4a8..ff4842f 100644
> > > > --- a/lib/x86/vm.h
> > > > +++ b/lib/x86/vm.h
> > > > @@ -22,6 +22,7 @@ void vfree(void *mem);
> > > >  void *vmap(unsigned long long phys, unsigned long size);
> > > >  void *alloc_vpage(void);
> > > >  void *alloc_vpages(ulong nr);
> > > > +unsigned long virt_to_phys_cr3(void *mem);
> > > 
> > > uint64_t.
> > virt_to_phys() also unsigned long. And get_pte() that virt_to_phys_cr3()
> > uses also. I guess the code is not ready for more then 2^32 memory in
> > 32bit VM.
> 
> It's certainly not enterprise quality yet.  But let's not add more problems.
> 
Okay.

> > > Alterative ways of doing this:
> > > - file-backed memory using FUSE to control paging
> > Not sure how that can be done.
> >
> > > - add madvise(MADV_DONTNEED) support to testdev, and have the guest
> > > trigger page-in itself.
> > MADV_DONTNEED will drop page, not swap it out.
> 
> Right, but it will be have to be reloaded from disk (it has to be
> file-backed for this to work).  If it's dirty, sync it first.
> 
Hmm, yes if it is file backed it may work. Setting up qemu to use file
backed memory is one more complication while running the test though.
I haven't checked by I am not sure that MADV_DONTNEED will drop page
immediately though. It probably puts it on some list to be freed later.
Hmm actually looking at the comments it seems like this is what happens:

/*
 * Application no longer needs these pages.  If the pages are dirty,
 * it's OK to just throw them away.  The app will be more careful about
 * data it wants to keep.  Be sure to free swap resources too.  The
 * zap_page_range call sets things up for shrink_active_list to actually
 * free
 * these pages later if no one else has touched them in the meantime,
 * although we could add these pages to a global reuse list for
 * shrink_active_list to pick up before reclaiming other pages.
 */

--
			Gleb.

  reply	other threads:[~2012-05-09  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 11:24 [PATCH unit-tests] Add async page fault test Gleb Natapov
2012-05-09  8:29 ` Avi Kivity
2012-05-09  8:41   ` Gleb Natapov
2012-05-09  8:52     ` Avi Kivity
2012-05-09  8:59       ` Gleb Natapov [this message]
2012-05-09 13:18         ` Takuya Yoshikawa
2012-05-09 13:20           ` Avi Kivity
2012-05-09 13:31             ` Takuya Yoshikawa

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=20120509085917.GR15960@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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.