xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jaeyong Yoo <jaeyong.yoo@samsung.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH RFC 0/4] arm: regarding live migration
Date: Thu, 13 Jun 2013 01:15:48 +0000 (GMT)	[thread overview]
Message-ID: <30392061.196241371086148236.JavaMail.weblogic@epml12> (raw)

Hello Ian,
I got some more questions while implementing live migration in arm.

> > (3) Regarding split drivers, come to think of it, we have to store 
> >    both side (front/back) states, in-flight event channels, IRQs, etc.
> >    And those look like quite a work (although evtchn is migrated within vcpu)
> >    I appreciate  if you guys could share any hints from the experience of 
> >    migrating split drivers in x86.
> 
> There is no need to save any of this state, the devices are effectively
> reconnected from scratch on the destination and the frontend devices are
> responsible for replaying any inflight state on resume.
> 

I'm trying to find the suspending part of PV driver, but can not locate it.
(And, looks like there is no function like suspend in xen-blkfront.c)
One guess is by deleting vbd in xenstore, maybe hot-plug-out can suspend.
Could you give me some advice?

And, about grant table, if we effectively suspend and resume PV driver, I 
think we don't need to migrate grant table entires. Is this right?

Thanks,
Jaeyong

             reply	other threads:[~2013-06-13  1:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  1:15 Jaeyong Yoo [this message]
2013-06-13  8:21 ` [PATCH RFC 0/4] arm: regarding live migration Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2013-06-05 10:30 Jaeyong Yoo
2013-06-05  5:46 Jaeyong Yoo
2013-06-05  9:13 ` Ian Campbell
2013-06-05  9:23   ` Ian Campbell
2013-06-05  9:26 ` Ian Campbell

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=30392061.196241371086148236.JavaMail.weblogic@epml12 \
    --to=jaeyong.yoo@samsung.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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).