qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-block@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 3/8] fdc: Introduce fdctrl->phase
Date: Fri, 29 May 2015 11:57:26 +0100	[thread overview]
Message-ID: <20150529105725.GF2127@work-vm> (raw)
In-Reply-To: <CAFEAcA-_d+vGSF31e46rFUmVvRwA9m_v8ZMarPTGZX9+mu6u0A@mail.gmail.com>

* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 29 May 2015 at 11:34, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
> > It's the destination I'm worried about here, not the source; lets say
> > you have two devices, a & b.  'a' gets serialised, but then 'b' finds
> > it has to wait, so we return to running the source and sending pages
> > across.   However the destination has already loaded the 'a' device state;
> > so that when we serialise again we send a new 'a' device state'; I'm
> > worrying here that the destination 'a' state loader would get upset
> > trying to load the same state twice without somehow resetting it.
> 
> You would need to reset the system before resending device state,
> I think. Device implementations rely on knowing that migration happens
> into a freshly reset device, and we don't have any way of resetting
> a single device, only the whole system at once.

I don't think you can do a device (or certainly not a system) reset
without resending the contents of RAM which was the whole point of
not restarting the migration from the beginning.

Dave

> 
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2015-05-29 10:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 13:19 [Qemu-devel] [PATCH v2 0/8] fdc: Clean up and fix command processing Kevin Wolf
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 1/8] fdc: Rename fdctrl_reset_fifo() to fdctrl_to_command_phase() Kevin Wolf
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 2/8] fdc: Rename fdctrl_set_fifo() to fdctrl_to_result_phase() Kevin Wolf
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 3/8] fdc: Introduce fdctrl->phase Kevin Wolf
2015-05-21 21:55   ` John Snow
2015-05-28 17:29     ` Dr. David Alan Gilbert
2015-05-29  7:50       ` Markus Armbruster
2015-05-29  8:33         ` Dr. David Alan Gilbert
2015-05-29  9:11           ` Kevin Wolf
2015-05-29  9:38             ` Dr. David Alan Gilbert
2015-05-29 10:27               ` Kevin Wolf
2015-05-29 10:34                 ` Dr. David Alan Gilbert
2015-05-29 10:55                   ` Peter Maydell
2015-05-29 10:57                     ` Dr. David Alan Gilbert [this message]
2015-06-01 12:51                       ` Markus Armbruster
2015-05-29 10:59                   ` Kevin Wolf
2015-06-01 12:46           ` Markus Armbruster
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 4/8] fdc: Use phase in fdctrl_write_data() Kevin Wolf
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 5/8] fdc: Code cleanup " Kevin Wolf
2015-05-21 21:34   ` John Snow
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 6/8] fdc: Disentangle phases in fdctrl_read_data() Kevin Wolf
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 7/8] fdc: Fix MSR.RQM flag Kevin Wolf
2015-05-21 21:27   ` John Snow
2015-05-21 13:19 ` [Qemu-devel] [PATCH v2 8/8] fdc-test: Test state for existing cases more thoroughly Kevin Wolf
2015-06-02 17:37 ` [Qemu-devel] [PATCH v2 0/8] fdc: Clean up and fix command processing John Snow

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=20150529105725.GF2127@work-vm \
    --to=dgilbert@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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).