On 07/28/2017 12:13 PM, Peter Maydell wrote:
On 28 July 2017 at 10:18, Peter Maydell wrote:
Talking to David about this on IRC, even "don't allow
migration" is a bit tricky, because you can't register
a migration-blocker if a migration is already in progress.
Two further options:
* disable
On 28 July 2017 at 10:18, Peter Maydell wrote:
> Talking to David about this on IRC, even "don't allow
> migration" is a bit tricky, because you can't register
> a migration-blocker if a migration is already in progress.
> Two further options:
> * disable this mmio-exec-in-place entirely for 2.10
On 20 July 2017 at 10:42, Peter Maydell wrote:
> OK, so what should we do for 2.10 ?
>
> We could:
> * implement the changes you suggest above, and mark only
>vmstate_register_ram'd blocks as migratable
>(would probably need to fix some places which buggily
>don't call vmstate_registe
Peter Maydell wrote:
> On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
>> I don't fully understand the way memory_region_do_invalidate_mmio_ptr
>> works; I see it dropping the memory region; if that's also dropping
>> the RAMBlock then it will upset migration. Even if the CPU is stopped
"Dr. David Alan Gilbert" wrote:
> * KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>>
>>
>>
>> Let's imagine somebody (eg: u-boot guest) wants to execute code
>> from the LQSPI area.
>>
>> memory_region_request_mmio_ptr is called (the guest is not
>> running yet) it will create a mmio-i
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
> > I don't fully understand the way memory_region_do_invalidate_mmio_ptr
> > works; I see it dropping the memory region; if that's also dropping
> > the RAMBlock then it will upset migratio
On 07/21/2017 11:29 AM, Peter Maydell wrote:
On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
I don't fully understand the way memory_region_do_invalidate_mmio_ptr
works; I see it dropping the memory region; if that's also dropping
the RAMBlock then it will upset migration. Even if t
On 07/21/2017 11:27 AM, Dr. David Alan Gilbert wrote:
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
* Peter Maydell (peter.mayd...@linaro.org) wrote:
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
* Edgar E. Iglesias
On 21 July 2017 at 10:13, Dr. David Alan Gilbert wrote:
> I don't fully understand the way memory_region_do_invalidate_mmio_ptr
> works; I see it dropping the memory region; if that's also dropping
> the RAMBlock then it will upset migration. Even if the CPU is stopped
> I dont think that stops
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> > > On 17 July 2017 at 19:58, Dr. David Alan Gilbert
> > > wrote:
> > > > * Edgar E. Iglesias (edgar.igles...@gmail.com) wro
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
> > * Peter Maydell (peter.mayd...@linaro.org) wrote:
> > > On 17 July 2017 at 19:58, Dr. David Alan Gilbert
> > > wrote:
> > > > * Edgar E. Iglesias (edgar.igles...@gmail.com) wro
On 07/20/2017 12:02 PM, Dr. David Alan Gilbert wrote:
* Peter Maydell (peter.mayd...@linaro.org) wrote:
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
* Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
Is there a way we can prevent migration of the RAMBlock?
Not yet, I think w
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
> > * Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
> >> Is there a way we can prevent migration of the RAMBlock?
> >
> > Not yet, I think we'd have to:
> >a) Add a flag to the RAM
On 07/20/2017 11:42 AM, Peter Maydell wrote:
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
* Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
Is there a way we can prevent migration of the RAMBlock?
Not yet, I think we'd have to:
a) Add a flag to the RAMBlock
b) Set it
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
> * Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
>> Is there a way we can prevent migration of the RAMBlock?
>
> Not yet, I think we'd have to:
>a) Add a flag to the RAMBlock
>b) Set it/clear it on registration
>c) Have a R
On 07/19/2017 06:46 PM, Dr. David Alan Gilbert wrote:
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
On 07/19/2017 02:29 PM, Dr. David Alan Gilbert wrote:
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
On 07/17/2017 07:27 PM, Edgar E. Iglesias wrote:
On Mon, Jul 17, 2017
On 07/19/2017 06:25 PM, Peter Maydell wrote:
On 19 July 2017 at 17:22, KONRAD Frederic 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
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/19/2017 02:29 PM, Dr. David Alan Gilbert wrote:
> > * KONRAD Frederic (frederic.kon...@adacore.com) wrote:
> > >
> > >
> > > On 07/17/2017 07:27 PM, Edgar E. Iglesias wrote:
> > > > On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydel
On 19 July 2017 at 17:22, KONRAD Frederic 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 un
On 07/19/2017 02:29 PM, Dr. David Alan Gilbert wrote:
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
On 07/17/2017 07:27 PM, Edgar E. Iglesias wrote:
On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydell
wrote:
On 14 June 2017 at 18:45, Edgar E. Iglesias
wrote:
From: "Edgar E. Iglesi
* KONRAD Frederic (frederic.kon...@adacore.com) wrote:
>
>
> On 07/17/2017 07:27 PM, Edgar E. Iglesias wrote:
> > On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydell
> > wrote:
> >
> > > On 14 June 2017 at 18:45, Edgar E. Iglesias
> > > wrote:
> > > > From: "Edgar E. Iglesias"
> > > > Paolo sugge
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
> > * Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
> >> Is there a way we can prevent migration of the RAMBlock?
> >
> > Not yet, I think we'd have to:
> >a) Add a flag to the RAM
On 07/17/2017 07:27 PM, Edgar E. Iglesias wrote:
On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydell
wrote:
On 14 June 2017 at 18:45, Edgar E. Iglesias
wrote:
From: "Edgar E. Iglesias"
Paolo suggested offline that we send a pull request for this series.
Here it is, I've run it through my test
On 17 July 2017 at 19:58, Dr. David Alan Gilbert wrote:
> * Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
>> Is there a way we can prevent migration of the RAMBlock?
>
> Not yet, I think we'd have to:
>a) Add a flag to the RAMBlock
>b) Set it/clear it on registration
>c) Have a R
* Edgar E. Iglesias (edgar.igles...@gmail.com) wrote:
> On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydell
> wrote:
>
> > On 14 June 2017 at 18:45, Edgar E. Iglesias
> > wrote:
> > > From: "Edgar E. Iglesias"
> > > Paolo suggested offline that we send a pull request for this series.
> > > Here it
On Mon, Jul 17, 2017 at 11:33 PM, Peter Maydell
wrote:
> On 14 June 2017 at 18:45, Edgar E. Iglesias
> wrote:
> > From: "Edgar E. Iglesias"
> > Paolo suggested offline that we send a pull request for this series.
> > Here it is, I've run it through my testsuite + tested the LQSPI testcase
> > o
On 14 June 2017 at 18:45, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias"
> Paolo suggested offline that we send a pull request for this series.
> Here it is, I've run it through my testsuite + tested the LQSPI testcase
> on Zynq.
> --
On Fri, Jun 23, 2017 at 11:54:52AM +0100, Peter Maydell wrote:
> On 14 June 2017 at 18:45, Edgar E. Iglesias wrote:
> > From: "Edgar E. Iglesias"
> >
> > Hi,
> >
> > Paolo suggested offline that we send a pull request for this series.
> > Here it is, I've run it through my testsuite + tested the
Le 06/23/2017 à 12:54 PM, Peter Maydell a écrit :
On 14 June 2017 at 18:45, Edgar E. Iglesias wrote:
From: "Edgar E. Iglesias"
Hi,
Paolo suggested offline that we send a pull request for this series.
Here it is, I've run it through my testsuite + tested the LQSPI testcase
on Zynq.
Cheers,
On 14 June 2017 at 18:45, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias"
>
> Hi,
>
> Paolo suggested offline that we send a pull request for this series.
> Here it is, I've run it through my testsuite + tested the LQSPI testcase
> on Zynq.
>
> Cheers,
> Edgar
>
> The following changes since
From: "Edgar E. Iglesias"
Hi,
Paolo suggested offline that we send a pull request for this series.
Here it is, I've run it through my testsuite + tested the LQSPI testcase
on Zynq.
Cheers,
Edgar
The following changes since commit 3f0602927b120a480b35dcf58cf6f95435b3ae91:
Merge remote-tracki
31 matches
Mail list logo
