On Thu, Nov 21, 2019 at 11:00:12AM +0100, Cédric Le Goater wrote:
> On 21/11/2019 10:11, Balamuruhan S wrote:
> > On Wed, Nov 20, 2019 at 08:46:30AM +0100, Cédric Le Goater wrote:
> >> Hello,
> >>
> >> On 19/11/2019 18:50, Balamuruhan S wrote:
> >>&
On Wed, Nov 20, 2019 at 08:46:30AM +0100, Cédric Le Goater wrote:
> Hello,
>
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > Hi All,
> >
> > PowerNV fails to boot in multichip systems due to some misinterpretation
> > and mapping in Homer/Occ device models, this
On Wed, Nov 20, 2019 at 08:31:50AM +0100, Cédric Le Goater wrote:
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > slw base and size mask are accessed during boot in homer_init_chip(),
> > so include BAR2 and BARMASK2 for Power8.
> >
> > Signed-off-by: Balamur
On Wed, Nov 20, 2019 at 08:30:03AM +0100, Cédric Le Goater wrote:
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > occ common area should be mapped once
>
> It's the same address on each chip.
>
> the question is how the HW knows from which chip the OCC access is
On Wed, Nov 20, 2019 at 08:20:35AM +0100, Cédric Le Goater wrote:
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > Fix incorrect PBA BAR and BARMASK value for Power8 occ common area
> > region where skiboot enum declaration have it in BAR 3 and BARMASK
> > is calc
On Wed, Nov 20, 2019 at 08:18:38AM +0100, Cédric Le Goater wrote:
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > homer/occ sizes are calculated in skiboot with `(mask | 0xf) + 1`,
> > and from xscom access should return correct mask values instead of actual
> > sizes.
&
On Wed, Nov 20, 2019 at 08:59:40AM +0100, Greg Kurz wrote:
> On Wed, 20 Nov 2019 08:46:51 +0530
> Balamuruhan S wrote:
>
> > On Wed, Nov 20, 2019 at 08:31:03AM +0530, Balamuruhan S wrote:
> > > On Wed, Nov 20, 2019 at 09:02:26AM +1100, David Gibson wrote:
> > >
On Wed, Nov 20, 2019 at 08:13:50AM +0100, Cédric Le Goater wrote:
> On 19/11/2019 18:50, Balamuruhan S wrote:
> > Homer size is 4MB and OCC common area size is 8MB, but currently
> > it is assigned with bar mask value. Also pass on the occ sram
> > size 3 bits right shifted t
On Wed, Nov 20, 2019 at 08:31:03AM +0530, Balamuruhan S wrote:
> On Wed, Nov 20, 2019 at 09:02:26AM +1100, David Gibson wrote:
> > On Wed, Nov 20, 2019 at 09:00:32AM +1100, David Gibson wrote:
> > > On Wed, Nov 20, 2019 at 08:56:18AM +1100, David Gibson wrote:
> > > >
On Wed, Nov 20, 2019 at 09:02:26AM +1100, David Gibson wrote:
> On Wed, Nov 20, 2019 at 09:00:32AM +1100, David Gibson wrote:
> > On Wed, Nov 20, 2019 at 08:56:18AM +1100, David Gibson wrote:
> > > On Tue, Nov 19, 2019 at 11:20:53PM +0530, Balamuruhan S wrote:
> >
-off-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/ppc/pnv_xscom.c b/hw/ppc/pnv_xscom.c
index cdd5fa356e..cb6d6bbcfc 100644
--- a/hw/ppc/pnv_xscom.c
+++ b/hw/ppc/pnv_xscom.c
@@ -38,9
Homer size is 4MB and OCC common area size is 8MB, but currently
it is assigned with bar mask value. Also pass on the occ sram
size 3 bits right shifted to initialize the size appropriately.
Signed-off-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_occ.c | 2 +-
include
occ common area should be mapped once and disable it for every
other chip.
Signed-off-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/hw/ppc/pnv_xscom.c b/hw/ppc/pnv_xscom.c
index
homer/occ sizes are calculated in skiboot with `(mask | 0xf) + 1`,
and from xscom access should return correct mask values instead of actual
sizes.
Signed-off-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 10 ++
1 file changed, 6 insertions(+), 4
slw base and size mask are accessed during boot in homer_init_chip(),
so include BAR2 and BARMASK2 for Power8.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 10 --
include/hw/ppc/pnv.h | 4
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/hw/ppc
and help to figure out the issues.
Balamuruhan S (5):
hw/ppc/pnv: incorrect homer and occ common area size
hw/ppc/pnv_xscom: PBA bar mask values are incorrect with homer/occ
sizes
hw/ppc/pnv_xscom: Power8 occ common area is in PBA BAR 3
hw/ppc/pnv_xscom: occ common area to be mapped
On Mon, Sep 16, 2019 at 07:50:44PM +0100, Dr. David Alan Gilbert wrote:
> * Balamuruhan S (bal...@linux.ibm.com) wrote:
> > assert `query-migrate` in target doesn't give migration
> > status and test errors even if migration succeeds.
> >
> > In target
On Mon, Sep 16, 2019 at 03:50:06PM +0100, Dr. David Alan Gilbert wrote:
> * Balamuruhan S (bal...@linux.ibm.com) wrote:
> > add migration test to query machine types supported by qemu binary
> > and migrate vm will all supported type.
> >
> > Signed-off-by: Balamuruh
assert `query-migrate` in target doesn't give migration
status and test errors even if migration succeeds.
In target:
{'execute': 'query-migrate'}
{"return": {}}
Signed-off-by: Balamuruhan S
---
tests/acceptance/migration.py | 7 ---
1 file changed, 4
add migration test to query machine types supported by qemu binary
and migrate vm will all supported type.
Signed-off-by: Balamuruhan S
---
tests/acceptance/migration.py | 26 ++
1 file changed, 26 insertions(+)
diff --git a/tests/acceptance/migration.py b/tests
add `get_machine_types()` to return list of supported machine types
by the qemu binary.
Signed-off-by: Balamuruhan S
---
tests/acceptance/avocado_qemu/__init__.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/acceptance/avocado_qemu/__init__.py
b/tests/acceptance/avocado_qemu
TIME : 5.86 s
Currently acceptance test for migration error out as we check
`query-migrate` in target after migration which is not appropriate.
Balamuruhan S (3):
tests/acceptance/migration: fix post migration check
tests/acceptance/avocado_qemu: add method to get supported machine
On Thu, Sep 12, 2019 at 11:54:00AM +0200, Cédric Le Goater wrote:
> On 12/09/2019 11:30, Balamuruhan S wrote:
> > Hi All,
> >
> > This is follow-up patch that implements HOMER and OCC SRAM device
> > models to emulate homer memory and occ common area access for ps
add PnvHomer device model to emulate homer memory access
for pstate table, occ-sensors, slw, occ static and dynamic
values for Power8 and Power9 chips.
Signed-off-by: Balamuruhan S
---
hw/ppc/Makefile.objs | 1 +
hw/ppc/pnv.c | 30 +
hw/ppc/pnv_homer.c | 272
emulate occ common area region with occ sram device model which
occ and skiboot uses it to communicate regarding sensors, slw
and HWMON in PowerNV emulated host.
Reviewed-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 8 +
hw/ppc/pnv_occ.c | 78
There were few trailing comments after `/*` instead in
new line and line more than 80 character, these fixes are
trivial and doesn't change any logic in code.
Reviewed-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 49 ---
`chip_num`.
* define all the memory ops access address as macros.
* few coding style warnings given by checkpatch.pl.
rfc patchset:
https://lists.gnu.org/archive/html/qemu-devel/2019-08/msg00979.html
I request for review, comments and suggestions for the changes.
Balamuruhan S (4):
hw/ppc
During PowerNV boot skiboot populates the device tree by
retrieving base address of homer/occ common area from
PBA BARs and prd ipoll mask by accessing xscom read/write
accesses.
Reviewed-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 34
On Wed, Sep 11, 2019 at 04:53:37PM +0200, Cédric Le Goater wrote:
> On 11/09/2019 16:29, Balamuruhan S wrote:
> > add PnvHomer device model to emulate homer memory access
> > for pstate table, occ-sensors, slw, occ static and dynamic
> > values for Power8 and Power9 chips.
&
add PnvHomer device model to emulate homer memory access
for pstate table, occ-sensors, slw, occ static and dynamic
values for Power8 and Power9 chips.
Signed-off-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/Makefile.objs | 1 +
hw/ppc/pnv.c | 30
emulate occ common area region with occ sram device model which
occ and skiboot uses it to communicate regarding sensors, slw
and HWMON in PowerNV emulated host.
Reviewed-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 8 +
hw/ppc/pnv_occ.c | 78
There were few trailing comments after `/*` instead in
new line and line more than 80 character, these fixes are
trivial and doesn't change any logic in code.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 49 -
1 file changed, 32 inser
During PowerNV boot skiboot populates the device tree by
retrieving base address of homer/occ common area from
PBA BARs and prd ipoll mask by accessing xscom read/write
accesses.
Reviewed-by: Cédric Le Goater
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 34
-devel/2019-08/msg00979.html
I request for review, comments and suggestions for the changes.
Balamuruhan S (4):
hw/ppc/pnv_xscom: retrieve homer/occ base address from PBA BARs
hw/ppc/pnv_occ: add sram device model for occ common area
hw/ppc/pnv_homer: add PowerNV homer device model
hw/ppc
On Wed, Sep 11, 2019 at 10:34:05AM +1000, David Gibson wrote:
> On Tue, Sep 10, 2019 at 12:40:19PM +0530, Balamuruhan S wrote:
> > add PnvHOMER device model to emulate homer memory access
>
> Please use PnvHomer as the identifier instead. I'm guessing that
> messes with t
On Tue, Sep 10, 2019 at 01:00:54PM +0200, Cédric Le Goater wrote:
> >>> +
> >>> +object_initialize_child(obj, "homer", &chip9->homer,
> >>> sizeof(chip9->homer),
> >>> +TYPE_PNV9_HOMER, &error_abort, NULL);
> >>> +object_property_add_const_link(OBJECT(&chip9->h
On Tue, Sep 10, 2019 at 01:45:55PM +0200, Cédric Le Goater wrote:
> On 10/09/2019 09:10, Balamuruhan S wrote:
> > Hi All,
> >
> > This is follow-up patch that implements HOMER and OCC SRAM device
> > models to emulate homer memory and occ common area access for ps
On Tue, Sep 10, 2019 at 09:46:16AM +0200, Cédric Le Goater wrote:
> On 10/09/2019 09:10, Balamuruhan S wrote:
> > add PnvHOMER device model to emulate homer memory access
> > for pstate table, occ-sensors, slw, occ static and dynamic
> > values for Power8 and Power9 chips.
On Tue, Sep 10, 2019 at 09:19:11AM +0200, Cédric Le Goater wrote:
> On 10/09/2019 09:10, Balamuruhan S wrote:
> > emulate occ common area region with occ sram device model which
> > occ and skiboot uses it to communicate regarding sensors, slw
> > and HWMON in
add PnvHOMER device model to emulate homer memory access
for pstate table, occ-sensors, slw, occ static and dynamic
values for Power8 and Power9 chips. Fix few coding style
warnings given by checkpatch.pl.
Signed-off-by: Balamuruhan S
---
hw/ppc/Makefile.objs | 1 +
hw/ppc/pnv.c
During PowerNV boot skiboot populates the device tree by
retrieving base address of homer/occ common area from
PBA BARs and prd ipoll mask by accessing xscom read/write
accesses.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 34 ++
include/hw/ppc/pnv.h
emulate occ common area region with occ sram device model which
occ and skiboot uses it to communicate regarding sensors, slw
and HWMON in PowerNV emulated host.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 8 +
hw/ppc/pnv_occ.c | 78
checkpatch.pl.
I request for review, comments and suggestions for the changes.
Balamuruhan S (3):
hw/ppc/pnv_xscom: retrieve homer/occ base address from PBA BARs
hw/ppc/pnv_occ: add sram device model for occ common area
hw/ppc/pnv_homer: add PowerNV homer device model
hw/ppc/Makefile.objs
On 8/8/19 3:55 PM, Stefan Hajnoczi wrote:
> On Wed, Aug 07, 2019 at 12:44:39PM +0530, Balamuruhan S wrote:
>> This is a proposal to extend mmio callbacks in Qemu with scripting interface
>> that is prototyped with python in this implementation. It gives ability to
>> feed
On 8/9/19 10:19 AM, David Gibson wrote:
> On Wed, Aug 07, 2019 at 10:15:48AM +0200, Cédric Le Goater wrote:
>> On 07/08/2019 09:14, Balamuruhan S wrote:
>>> Hi All,
>>>
>>> This is a proposal to extend mmio callbacks in Qemu with scripting interface
>&g
On 8/9/19 2:16 PM, Stefan Hajnoczi wrote:
> On Thu, Aug 08, 2019 at 11:53:07AM +0100, Daniel P. Berrangé wrote:
>> On Thu, Aug 08, 2019 at 11:10:13AM +0100, Stefan Hajnoczi wrote:
>>> On Wed, Aug 07, 2019 at 12:20:47PM +0200, Philippe Mathieu-Daudé wrote:
> +void python_args_clean(char *args
On 8/8/19 6:15 PM, Philippe Mathieu-Daudé wrote:
> On 8/8/19 12:49 PM, Daniel P. Berrangé wrote:
>> On Wed, Aug 07, 2019 at 12:44:40PM +0530, Balamuruhan S wrote:
>>> Adds scripting interface with python library to call functions in
>>> python modules from Qemu tha
On 8/8/19 3:39 PM, Stefan Hajnoczi wrote:
> On Wed, Aug 07, 2019 at 12:44:40PM +0530, Balamuruhan S wrote:
>> +void python_args_init_cast_int(char *args[], int arg, int pos)
>> +{
>> +args[pos]= malloc(sizeof(int));
>> +sprintf(args[pos], "%d", arg);
On 8/9/19 10:14 AM, David Gibson wrote:
> On Wed, Aug 07, 2019 at 09:54:55AM +0200, Cédric Le Goater wrote:
>> On 07/08/2019 09:14, Balamuruhan S wrote:
>>> Add mmio callback functions to enable homer/occ common area
>>> to emulate pstate table, occ-sensors, slw, occ st
On 8/9/19 10:16 AM, David Gibson wrote:
> On Wed, Aug 07, 2019 at 12:44:45PM +0530, Balamuruhan S wrote:
>> use python interface APIs in homer/occ common area emulation to
>> interact with scripts if provided else fallback to normal flow,
>> it shows how simple to use the int
On 8/7/19 3:57 PM, Philippe Mathieu-Daudé wrote:
> On 8/7/19 9:14 AM, Balamuruhan S wrote:
>> use python interface APIs in homer/occ common area emulation to
>> interact with scripts if provided else fallback to normal flow,
>> it shows how simple to use the interface t
On Wed, Aug 07, 2019 at 10:01:58AM +0200, Cédric Le Goater wrote:
> On 07/08/2019 09:14, Balamuruhan S wrote:
> > During PowerNV boot skiboot populates the device tree by retrieving
> > base address of homer/occ common area from PBA BARs and prd ipoll
> > mask by acces
On Wed, Aug 07, 2019 at 10:15:48AM +0200, Cédric Le Goater wrote:
> On 07/08/2019 09:14, Balamuruhan S wrote:
> > Hi All,
> >
> > This is a proposal to extend mmio callbacks in Qemu with scripting interface
> > that is prototyped with python in this implementation. I
On Wed, Aug 07, 2019 at 09:59:26AM +0200, Cédric Le Goater wrote:
> On 07/08/2019 09:14, Balamuruhan S wrote:
> > homer and occ common area region base address are initialized
> > to create device tree and realized to map the address with
> > mmio callbacks dur
On Wed, Aug 07, 2019 at 09:54:55AM +0200, Cédric Le Goater wrote:
> On 07/08/2019 09:14, Balamuruhan S wrote:
> > Add mmio callback functions to enable homer/occ common area
> > to emulate pstate table, occ-sensors, slw, occ static and
> > dynamic values for Power8 and Power9
During PowerNV boot skiboot populates the device tree by retrieving
base address of homer/occ common area from PBA BARs and prd ipoll
mask by accessing xscom read/write accesses.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 27 +++
1 file changed, 23 insertions
tree.
currently skiboot disables the homer/occ code path with
`QUIRK_NO_PBA`, this quirk have to be removed in skiboot
for it to use this infrastructure.
Signed-off-by: Hariharan T.S
Signed-off-by: Balamuruhan S
---
hw/ppc/Makefile.objs | 2 +-
hw/ppc/pnv_homer.c | 185
.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_homer.c | 20
hw/ppc/pnv_xscom.c | 9 +
include/sysemu/sysemu.h | 4
vl.c| 24
4 files changed, 53 insertions(+), 4 deletions(-)
diff --git a/hw/ppc/pnv_homer.c b
base address + size contiguously on a PowerNV with
multichip boot.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv.c | 49 +
include/hw/ppc/pnv.h | 1 +
2 files changed, 46 insertions(+), 4 deletions(-)
diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
xscom to adopt this python interface
Patch 3 - 6: emulate uncore/core shared memory region with mmio callbacks and
add support with this infrastructure.
I request for comments, suggestions, ideas on getting a scripting interface
like python added in qemu.
Balamuruhan S (6):
utils/python_api: add
Existing xscom access emulation for read/write can be
extended with the python interface to support feeding
data externally.
Signed-off-by: Balamuruhan S
---
hw/ppc/pnv_xscom.c | 31 ---
include/sysemu/sysemu.h | 4
qemu-options.hx | 14
maintenance.
Signed-off-by: Balamuruhan S
---
configure | 10 +
include/sysemu/python_api.h | 30 +
util/Makefile.objs | 1 +
util/python_api.c | 100
4 files changed, 141 insertions(+)
create mode
add `get_machine_types()` to return list of supported machine types
by the qemu binary.
Signed-off-by: Balamuruhan S
---
tests/acceptance/avocado_qemu/__init__.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/acceptance/avocado_qemu/__init__.py
b/tests/acceptance/avocado_qemu
assert `query-migrate` in target doesn't give migration
status and test errors even if migration succeeds.
In target:
{'execute': 'query-migrate'}
{"return": {}}
Signed-off-by: Balamuruhan S
---
tests/acceptance/migration.py | 1 -
1 file changed, 1 deletio
add migration test to query machine types supported by qemu binary
and migrate vm will all supported type.
Signed-off-by: Balamuruhan S
---
tests/acceptance/migration.py | 26 ++
1 file changed, 26 insertions(+)
diff --git a/tests/acceptance/migration.py b/tests
TIME : 5.86 s
Currently acceptance test for migration error out as we check `query-migrate`
in target after migration which is not appropriate.
Balamuruhan S (3):
tests/acceptance/migration: fix post migration check
tests/acceptance/avocado_qemu: add method to get supported machine
ve ptr and ptr1 meaningful names:
> ptr -> guardptr : pointer to the PROT_NONE guard region
> ptr1 -> ptr : pointer to the mapped memory returned to caller
>
> Signed-off-by: Murilo Opsfelder Araujo
Reported-by: Balamuruhan S
Tested-by: Balamuruhan S
the underlying page size on ppc64.
>
> After this patch, memory hot-unplug releases huge pages back to the
> pool.
>
> Fixes: 7197fb4058bcb68986bae2bb2c04d6370f3e7218
> Signed-off-by: Murilo Opsfelder Araujo
Reported-by: Balamuruhan S
Tested-by: Balamuruhan S
I tried
On Thu, Jan 24, 2019 at 03:18:22PM +0800, Peter Xu wrote:
> On Wed, Jan 23, 2019 at 05:35:03PM +0100, Juan Quintela wrote:
> > bal...@linux.vnet.ibm.com wrote:
> > > From: Balamuruhan S
> > >
> > > currently we calculate expected_downtime by time taken to tran
ranch and stop patching, run "git am --abort".
I have manually reverted it to apply and test your patchset.
This Patchset is working without any issues.
Tested-by: Balamuruhan S
>
> Peter Xu (9):
> migration: simplify check to use qemu file buffer
> mig
On Fri, Jul 06, 2018 at 11:56:59AM +0100, Dr. David Alan Gilbert wrote:
> * Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > Based-on: <20180627132246.5576-1-pet...@redhat.com>
> > >
> > > Based on the series to unbreak postcopy:
> > > Subject:
On Fri, Jul 06, 2018 at 11:56:59AM +0100, Dr. David Alan Gilbert wrote:
> * Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > Based-on: <20180627132246.5576-1-pet...@redhat.com>
> > >
> > > Based on the series to unbreak postcopy:
> > > Subject:
On Thu, Jul 05, 2018 at 11:17:53AM +0800, Peter Xu wrote:
> It's generalized from wait_for_migration_complete() to allow us to wait
> for any migration status besides failure.
>
> Signed-off-by: Peter Xu
> ---
Reviewed-by: Balamuruhan S
> tests/migration-test.c |
On Thu, Jul 05, 2018 at 11:17:51AM +0800, Peter Xu wrote:
> For example, we can pass in '"resume": true' to resume a migration.
>
> Signed-off-by: Peter Xu
> ---
Reviewed-by: Balamuruhan S
> tests/migration-test.c | 12 ++--
> 1 file changed, 6 i
On Fri, Jul 06, 2018 at 10:19:51AM +0800, Peter Xu wrote:
> On Thu, Jul 05, 2018 at 03:01:44PM +0530, Balamuruhan S wrote:
> > On Thu, Jul 05, 2018 at 11:17:50AM +0800, Peter Xu wrote:
> > > Separate the old postcopy UNIX socket test into three steps, provide a
> > >
On Fri, Jul 06, 2018 at 12:37:40PM +0800, Peter Xu wrote:
> On Thu, Jul 05, 2018 at 06:22:31PM +0530, Balamuruhan S wrote:
> > On Thu, Jul 05, 2018 at 05:26:09PM +0800, Peter Xu wrote:
> > > On Thu, Jul 05, 2018 at 01:30:17PM +0530, Balamuruhan S wrote:
> > > > Th
On Thu, Jul 05, 2018 at 05:26:09PM +0800, Peter Xu wrote:
> On Thu, Jul 05, 2018 at 01:30:17PM +0530, Balamuruhan S wrote:
> > This patch adds test for multifd migration feature with fd protocol.
> >
> > Signed-off-by: Balamuruhan S
> > ---
>
On Thu, Jul 05, 2018 at 11:17:52AM +0800, Peter Xu wrote:
> Introduce helpers to query migration states and use it.
>
> Signed-off-by: Peter Xu
Looks good to me.
Reviewed-by: Balamuruhan S
> ---
> tests/migration-test.c | 64 --
>
On Thu, Jul 05, 2018 at 11:17:50AM +0800, Peter Xu wrote:
> Separate the old postcopy UNIX socket test into three steps, provide a
> helper for each step. With these helpers, we can do more compliated
> tests like postcopy recovery, while keep the codes shared.
>
> Signed-off-by: Peter Xu
> ---
This patch adds test for multifd migration feature with fd protocol.
Signed-off-by: Balamuruhan S
---
tests/migration-test.c | 57 ++
1 file changed, 57 insertions(+)
diff --git a/tests/migration-test.c b/tests/migration-test.c
index e2434e70ea
multifd migration feature is in with commit: 35374cbdff, this patch
adds test for it using unix socket.
Signed-off-by: Balamuruhan S
---
tests/migration-test.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/tests/migration-test.c b/tests/migration-test.c
/multifd/fd: OK
PASS: tests/migration-test
Please help review,
-- Bala
Balamuruhan S (2):
tests: add precopy multifd migration test
tests: add precopy multifd migration with fd protocol
tests/migration-test.c | 88 ++
1 file changed, 88
On Mon, Jul 02, 2018 at 04:46:18PM +0800, Peter Xu wrote:
> On Mon, Jul 02, 2018 at 01:34:45PM +0530, Balamuruhan S wrote:
> > On Wed, Jun 27, 2018 at 09:22:42PM +0800, Peter Xu wrote:
> > > v3:
> > > - keep the recovery logic even for RDMA by dropping the 3rd pat
On Wed, Jun 27, 2018 at 09:22:42PM +0800, Peter Xu wrote:
> v3:
> - keep the recovery logic even for RDMA by dropping the 3rd patch and
> touch up the original 4th patch (current 3rd patch) to suite that [Dave]
>
> v2:
> - break the first patch into several
> - fix a QEMUFile leak
>
> Please re
On Thu, Jun 28, 2018 at 01:06:25PM +0200, Juan Quintela wrote:
> Balamuruhan S wrote:
> > On Wed, Jun 27, 2018 at 02:56:04PM +0200, Juan Quintela wrote:
> >> From: Daniel P. Berrangé
>
>
>
> > Hi Juan,
> >
> > I tried to perform multifd enable
On Wed, Jun 27, 2018 at 02:56:04PM +0200, Juan Quintela wrote:
> From: Daniel P. Berrangé
>
> The way we determine if we can start the incoming migration was
> changed to use migration_has_all_channels() in:
>
> commit 428d89084c709e568f9cd301c2f6416a54c53d6d
> Author: Juan Quintela
> Dat
`remaining` field in ram_counters to hold ram_bytes_remaining()
for calculating expected_downtime.
Reported-by: Michael Roth
Signed-off-by: Balamuruhan S
Signed-off-by: Laurent Vivier
---
migration/migration.c | 3 +--
migration/ram.c | 1 +
2 files changed, 2 insertions(+), 2 deletions(-)
diff
actual value = 1054 milliseconds
since v1:
use ram_bytes_remaining() instead of dirty_pages_rate * page_size to
calculate expected_downtime to be more accurate.
Regards,
Bala
Balamuruhan S (1):
migration: calculate expected_downtime with ram_bytes_remaining()
migration/migration.c | 3 +--
migra
485 pages
normal bytes: 1333940 kbytes
dirty sync count: 6
page size: 4 kbytes
> "transferred ram" continues to increase.
If we do not set the downtime-limit, the remaining ram and transferred
ram gets bumped up and migration continues infinitely.
-- Bala
>
> so think there is a
ditional state (subsections etc)
> into the order we prefer.
> * Add a note about firmware
>
> Signed-off-by: Dr. David Alan Gilbert
> Reviewed-by: Peter Xu
> ---
> docs/devel/migration.rst | 532 +++
> 1 file changed, 376 insert
Hi,
Dave, David and Juan if you guys are okay with the patch, please
help to merge it.
Thanks,
Bala
On Wed, Apr 25, 2018 at 12:40:40PM +0530, Balamuruhan S wrote:
> expected_downtime value is not accurate with dirty_pages_rate * page_size,
> using ram_bytes_remaining would yeild it corre
On Fri, Apr 27, 2018 at 06:34:16PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Update the migration docs:
>
> Among other changes:
> * Added a general list of advice for device authors
> * Reordered the section on conditional state (subsections etc)
>
On Fri, Apr 20, 2018 at 06:57:21PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> Update the migration docs:
>
> Among other changes:
> * Added a general list of advice for device authors
> * Reordered the section on conditional state (subsections etc)
>
on:
calculated value = (14016 * 8 ) / 108.92 = 1029.452809401 milliseconds
actual value = 1054 milliseconds
since v1:
use ram_bytes_remaining() instead of dirty_pages_rate * page_size to
calculate expected_downtime to be more accurate.
Regards,
Bala
Balamuruhan S (1):
migration: calculate ex
this patch bandwidth, expected_downtime and remaining ram are
calculated in migration_update_counters(), retrieve the same value during
"info migrate". By this approach we get almost close enough value.
Reported-by: Michael Roth
Signed-off-by: Balamuruhan S
---
migrat
On Fri, Apr 20, 2018 at 11:28:04AM +0100, Dr. David Alan Gilbert wrote:
> * David Gibson (da...@gibson.dropbear.id.au) wrote:
> > On Thu, Apr 19, 2018 at 12:24:04PM +0100, Dr. David Alan Gilbert wrote:
> > > * Balamuruhan S (bal...@linux.vnet.ibm.com) wrote:
> > > >
On Thu, Apr 19, 2018 at 09:48:17PM +1000, David Gibson wrote:
> On Thu, Apr 19, 2018 at 10:14:52AM +0530, Balamuruhan S wrote:
> > On Wed, Apr 18, 2018 at 09:36:33AM +0100, Dr. David Alan Gilbert wrote:
> > > * Balamuruhan S (bal...@linux.vnet.ibm.com) wrote:
> > > >
On Wed, Apr 18, 2018 at 09:36:33AM +0100, Dr. David Alan Gilbert wrote:
> * Balamuruhan S (bal...@linux.vnet.ibm.com) wrote:
> > On Wed, Apr 18, 2018 at 10:57:26AM +1000, David Gibson wrote:
> > > On Wed, Apr 18, 2018 at 10:55:50AM +1000, David Gibson wrote:
> > > >
On Wed, Apr 18, 2018 at 10:55:50AM +1000, David Gibson wrote:
> On Tue, Apr 17, 2018 at 06:53:17PM +0530, Balamuruhan S wrote:
> > expected_downtime value is not accurate with dirty_pages_rate * page_size,
> > using ram_bytes_remaining would yeild it correct.
>
> This commi
On Wed, Apr 18, 2018 at 10:57:26AM +1000, David Gibson wrote:
> On Wed, Apr 18, 2018 at 10:55:50AM +1000, David Gibson wrote:
> > On Tue, Apr 17, 2018 at 06:53:17PM +0530, Balamuruhan S wrote:
> > > expected_downtime value is not accurate with dirty_pages_rate * page
1 - 100 of 108 matches
Mail list logo
