qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Isaku Yamahata <yamahata@valinux.co.jp>
To: Tommy <thfbjyddx@hotmail.com>
Cc: "t.hirofuchi" <t.hirofuchi@aist.go.jp>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
	"satoshi.itoh" <satoshi.itoh@aist.go.jp>
Subject: Re: [Qemu-devel] 回??: [PATCH 2/2] umem: chardevice for kvm	postcopy
Date: Thu, 5 Jan 2012 21:18:38 +0900	[thread overview]
Message-ID: <20120105121837.GE6819@valinux.co.jp> (raw)
In-Reply-To: <BLU0-SMTP15295DFE06E9B7CE914B8CABC940@phx.gbl>

Hmm, this sounds like you haven't specified -postcopy option at the
incoming qemu.
How did you start incoming qemu?


On Thu, Jan 05, 2012 at 07:10:42PM +0800, Tommy wrote:
> After I use this series of patches, but the migration failed.
> 2, I start migrate -d -p -n tcp:xxx:4444 on the outgoing node
> 2, on the incoming part, the qemu get stuck and migration failed
> the  destnation can not typing any more
>  
> today I found it's just at qemu_loadvm_state, just after the while loop ,maybe
> in cpu_synchronize_all_post_init
> I think there is some problems with qemu side for it doesn't get to the umem
> part
> I'm not sure about the problem
> do you have some suggestion?
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> Tommy
>  
> From: Isaku Yamahata
> Date: 2012-01-05 18:48
> To: thfbjyddx
> CC: t.hirofuchi; qemu-devel; kvm; satoshi.itoh
> Subject: Re: [Qemu-devel]  ??: [PATCH 2/2] umem: chardevice for kvm postcopy
> On Thu, Jan 05, 2012 at 12:08:50PM +0800, thfbjyddx wrote:
> > hi,
> > I've tried to use this patch,
>  
> Oh great! Can we share your results?
>  
>  
> > but it doesn't work for compiling error on
> >  
> >  page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma, vmf->address);//vmf->
> > virtual_address?
> >  
> > I guess it's for the wrong kernel version?
> > can you give me some detail about this or any clue?
> > 3x 
>  
> Thank you for report. The following should fix.
> It depends on kernel configuration. My config didn't catch it.
>  
> diff --git a/drivers/char/umem.c b/drivers/char/umem.c
> index 4d031b5..853f1ce 100644
> --- a/drivers/char/umem.c
> +++ b/drivers/char/umem.c
> @@ -129,7 +129,7 @@ static int umem_minor_fault(struct umem *umem,
>    * vmf->page = fake_vmf->page;
>    */
>  
> - page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma, vmf->address);
> + page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma, vmf->virtual_address);
>   if (!page)
>   return VM_FAULT_OOM;
>   if (mem_cgroup_cache_charge(page, vma->vm_mm, GFP_KERNEL)) {
>  
>  
>  
> -- 
> yamahata
>  
>  

-- 
yamahata

  reply	other threads:[~2012-01-05 12:18 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  1:26 [Qemu-devel] [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy Isaku Yamahata
2011-12-29  1:26 ` [Qemu-devel] [PATCH 1/2] export necessary symbols Isaku Yamahata
2011-12-29  1:26 ` [Qemu-devel] [PATCH 2/2] umem: chardevice for kvm postcopy Isaku Yamahata
2011-12-29 11:17   ` Avi Kivity
2011-12-29 12:22     ` Isaku Yamahata
2011-12-29 12:47       ` Avi Kivity
2012-01-05  4:08   ` [Qemu-devel] 回复: " thfbjyddx
2012-01-05 10:48     ` [Qemu-devel] 回??: " Isaku Yamahata
2012-01-05 11:10       ` Tommy
2012-01-05 12:18         ` Isaku Yamahata [this message]
2012-01-05 15:02           ` Tommy Tang
     [not found]           ` <4F05BB68.9050302@hotmail.com>
2012-01-05 15:05             ` Tommy Tang
2012-01-06  7:02           ` thfbjyddx
2012-01-06 17:13             ` [Qemu-devel] 回??: [PATCH 2/2] umem: chardevice for kvm?postcopy Isaku Yamahata
2011-12-29  1:31 ` [Qemu-devel] [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy Isaku Yamahata
2011-12-29 11:24 ` Avi Kivity
2011-12-29 12:39   ` Isaku Yamahata
2011-12-29 12:55     ` Avi Kivity
2011-12-29 13:49       ` Isaku Yamahata
2011-12-29 13:52         ` Avi Kivity
2011-12-29 14:18           ` Isaku Yamahata
2011-12-29 14:35             ` Avi Kivity
2011-12-29 14:49               ` Isaku Yamahata
2011-12-29 14:55                 ` Avi Kivity
2011-12-29 15:53                   ` Isaku Yamahata
2011-12-29 16:00                     ` Avi Kivity
2011-12-29 16:01                       ` Avi Kivity
2012-01-02 17:05                         ` Andrea Arcangeli
2012-01-02 17:55                           ` Paolo Bonzini
2012-01-03 14:25                             ` Andrea Arcangeli
2012-01-12 13:57                               ` Avi Kivity
2012-01-13  2:06                                 ` Andrea Arcangeli
2012-01-04  3:03                           ` Isaku Yamahata
2012-01-12 13:59                             ` Avi Kivity
2012-01-13  1:09                               ` Benoit Hudzia
2012-01-13  1:31                                 ` Takuya Yoshikawa
2012-01-13  9:40                                   ` Benoit Hudzia
2012-01-13  2:03                                 ` Isaku Yamahata
2012-01-13  2:15                                   ` Isaku Yamahata
2012-01-13  9:55                                     ` Benoit Hudzia
2012-01-13  9:48                                   ` Benoit Hudzia
2012-01-13  2:09                               ` Andrea Arcangeli

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=20120105121837.GE6819@valinux.co.jp \
    --to=yamahata@valinux.co.jp \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=satoshi.itoh@aist.go.jp \
    --cc=t.hirofuchi@aist.go.jp \
    --cc=thfbjyddx@hotmail.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 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).