Re: [Qemu-devel] [PULL v1 0/7] MMIO Exec pull request

From: KONRAD Frederic <frederic.konrad@adacore.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PULL v1 0/7] MMIO Exec pull request
Date: Thu, 20 Jul 2017 09:55:07 +0200	[thread overview]
Message-ID: <8feb72ef-243c-fc45-ad16-6af92796e54f@adacore.com> (raw)
In-Reply-To: <CAFEAcA83H+9b2t2MhE0wDCDK_-DuPSuBZrzbQrevhjCh1SEBDA@mail.gmail.com>

On 07/19/2017 06:25 PM, Peter Maydell wrote:
> On 19 July 2017 at 17:22, KONRAD Frederic <frederic.konrad@adacore.com> wrote:
>> Scary.. Yes your right. I still think it doesn't need to be
>> migrated.. But how..
>>
>> BTW taking a look at this I found the comment below which seems
>> to implies that the content won't be migrated?
> 
> That's a comment that I added just recently under a
> slight misapprehension. Once we've figured out what
> the right thing is we can fix it, or make the code do
> what the comment says.
> 
> The actual current situation is "this function does nothing
> to ensure the RAMBlock is correctly migrated, so if you
> do nothing then you'll wind up with migration being silently
> broken, if more than one thing is doing this at once in
> the system, but if one and only one RAMblock is in this
> situation then it'll work by luck". Which is definitely not
> behaviour we are doing on purpose :-)
> 

Ok thanks!
Fred

> thanks
> -- PMM
> 