qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: KONRAD Frederic <frederic.konrad@adacore.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Alistair Francis <alistair.francis@xilinx.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.10 2/2] xilinx-spips: add a migration blocker when using mmio_execution
Date: Thu, 10 Aug 2017 11:22:41 +0200	[thread overview]
Message-ID: <20170810092241.GK4859@toto> (raw)
In-Reply-To: <CAFEAcA-uR+KK9RfTQm8=E6SCeWh-CkY+fua-ByPUHoYQVw=TGQ@mail.gmail.com>

On Thu, Aug 10, 2017 at 10:11:13AM +0100, Peter Maydell wrote:
> On 1 August 2017 at 10:41, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 1 August 2017 at 10:35, KONRAD Frederic <frederic.konrad@adacore.com> wrote:
> >>
> >>
> >> On 08/01/2017 11:30 AM, Edgar E. Iglesias wrote:
> >>> At this stage, perhaps we should just register the blocker when this dev
> >>> realizes.
> >>>
> >>> If a request_ptr comes in during migration, the VM will fail either way...
> >
> >> Yes but this will breaks migration for the spips device everytime
> >> and not only when mmio-execution is used?
> >
> > This line of thought is why I ended up suggesting just disabling
> > the exec-in-place feature -- that way we just don't introduce
> > what would be a new-in-2.10 feature, rather than breaking something
> > that used to work in 2.9.
> 
> OK, so what's the plan here? We have several options:
>  * just disable exec-from-spips for 2.10 (I sent a patch for that)
>  * disable exec-from-spips for 2.10 but with a device x-property
>    to allow the user to turn it on again if they really want it
>  * this patch or variants on it which try to only disable
>    migration if exec-from-spips is actually used by the guest
>    (I don't like these because of the awkward corner cases if
>    migration and the guest using exec-from-spips happen at the
>    same time)
> 
> So my current view remains "we should just disable this feature
> for 2.10 and we can implement it properly with handling of
> migration for 2.11", unless somebody cares enough to implement
> the x-property thing within the next day or so.

Hi Peter,

I think the x-property sounds good.
Fred, would you like to send a patch for that?
Otherwise, I can do it later today.

Cheers,
Edgar

  reply	other threads:[~2017-08-10  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  8:10 [Qemu-devel] [PATCH for-2.10 0/2] mmio-execution and migration KONRAD Frederic
2017-08-01  8:10 ` [Qemu-devel] [PATCH for-2.10 1/2] mmio-execution: warn the potential developer about migration KONRAD Frederic
2017-08-01  8:10 ` [Qemu-devel] [PATCH for-2.10 2/2] xilinx-spips: add a migration blocker when using mmio_execution KONRAD Frederic
2017-08-01  9:00   ` Peter Maydell
2017-08-01  9:13     ` KONRAD Frederic
2017-08-01  9:30       ` Edgar E. Iglesias
2017-08-01  9:35         ` KONRAD Frederic
2017-08-01  9:41           ` Peter Maydell
2017-08-10  9:11             ` Peter Maydell
2017-08-10  9:22               ` Edgar E. Iglesias [this message]
2017-08-10  9:28                 ` KONRAD Frederic

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=20170810092241.GK4859@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=alistair.francis@xilinx.com \
    --cc=dgilbert@redhat.com \
    --cc=frederic.konrad@adacore.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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).