Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
On Thu, May 02, 2019 at 09:35:50AM +0100, Dr. David Alan Gilbert wrote: >* Wei Yang (richard.weiy...@gmail.com) wrote: >> On Wed, May 01, 2019 at 09:24:06PM -0700, no-re...@patchew.org wrote: >> >Patchew URL: >> >https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ >> > >> > >> > >> >Hi, >> > >> >This series failed the asan build test. Please find the testing commands and >> >their output below. If you have Docker installed, you can probably >> >reproduce it >> >locally. >> > >> >=== TEST SCRIPT BEGIN === >> >#!/bin/bash >> >time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 >> >=== TEST SCRIPT END === >> > >> > COPYRUNNER >> >RUN test-debug in qemu:fedora >> >container_linux.go:247: starting container process caused >> >"process_linux.go:258: applying cgroup configuration for process caused >> >\"The maximum number of active connections for UID 0 has been reached\"" >> >/usr/bin/docker-current: Error response from daemon: oci runtime error: The >> >maximum number of active connections for UID 0 has been reached. >> >Traceback (most recent call last): >> > File "./tests/docker/docker.py", line 615, in >> >sys.exit(main()) >> > >> >> May I ask how I can reproduce this? > >To me this just looks like patchew having a problem, I don't think it's >a real qemu bug. Ah, thanks. > >Dave > >> > >> >The full log is available at >> >http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.asan/?type=message. >> >--- >> >Email generated automatically by Patchew [https://patchew.org/]. >> >Please send your feedback to patchew-de...@redhat.com >> >> -- >> Wei Yang >> Help you, Help me >-- >Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK -- Wei Yang Help you, Help me
Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
* Wei Yang (richard.weiy...@gmail.com) wrote: > On Wed, May 01, 2019 at 09:24:06PM -0700, no-re...@patchew.org wrote: > >Patchew URL: > >https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ > > > > > > > >Hi, > > > >This series failed the asan build test. Please find the testing commands and > >their output below. If you have Docker installed, you can probably reproduce > >it > >locally. > > > >=== TEST SCRIPT BEGIN === > >#!/bin/bash > >time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 > >=== TEST SCRIPT END === > > > > COPYRUNNER > >RUN test-debug in qemu:fedora > >container_linux.go:247: starting container process caused > >"process_linux.go:258: applying cgroup configuration for process caused > >\"The maximum number of active connections for UID 0 has been reached\"" > >/usr/bin/docker-current: Error response from daemon: oci runtime error: The > >maximum number of active connections for UID 0 has been reached. > >Traceback (most recent call last): > > File "./tests/docker/docker.py", line 615, in > >sys.exit(main()) > > > > May I ask how I can reproduce this? To me this just looks like patchew having a problem, I don't think it's a real qemu bug. Dave > > > >The full log is available at > >http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.asan/?type=message. > >--- > >Email generated automatically by Patchew [https://patchew.org/]. > >Please send your feedback to patchew-de...@redhat.com > > -- > Wei Yang > Help you, Help me -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
On Wed, May 01, 2019 at 09:24:06PM -0700, no-re...@patchew.org wrote: >Patchew URL: >https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ > > > >Hi, > >This series failed the asan build test. Please find the testing commands and >their output below. If you have Docker installed, you can probably reproduce it >locally. > >=== TEST SCRIPT BEGIN === >#!/bin/bash >time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 >=== TEST SCRIPT END === > > COPYRUNNER >RUN test-debug in qemu:fedora >container_linux.go:247: starting container process caused >"process_linux.go:258: applying cgroup configuration for process caused \"The >maximum number of active connections for UID 0 has been reached\"" >/usr/bin/docker-current: Error response from daemon: oci runtime error: The >maximum number of active connections for UID 0 has been reached. >Traceback (most recent call last): > File "./tests/docker/docker.py", line 615, in >sys.exit(main()) > May I ask how I can reproduce this? > >The full log is available at >http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.asan/?type=message. >--- >Email generated automatically by Patchew [https://patchew.org/]. >Please send your feedback to patchew-de...@redhat.com -- Wei Yang Help you, Help me
Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
Patchew URL: https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ Hi, This series failed the asan build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN === #!/bin/bash time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 === TEST SCRIPT END === COPYRUNNER RUN test-debug in qemu:fedora container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"The maximum number of active connections for UID 0 has been reached\"" /usr/bin/docker-current: Error response from daemon: oci runtime error: The maximum number of active connections for UID 0 has been reached. Traceback (most recent call last): File "./tests/docker/docker.py", line 615, in sys.exit(main()) The full log is available at http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.asan/?type=message. --- Email generated automatically by Patchew [https://patchew.org/]. Please send your feedback to patchew-de...@redhat.com
Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
On Wed, May 01, 2019 at 03:53:01PM -0700, no-re...@patchew.org wrote: >Patchew URL: >https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ > > > >Hi, > >This series failed the docker-mingw@fedora build test. Please find the testing >commands and >their output below. If you have Docker installed, you can probably reproduce it >locally. > >=== TEST SCRIPT BEGIN === >#!/bin/bash >time make docker-test-mingw@fedora SHOW_ENV=1 J=14 NETWORK=1 >=== TEST SCRIPT END === > > > > >The full log is available at >http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.docker-mingw@fedora/?type=message. Where can I see the test case? >--- >Email generated automatically by Patchew [https://patchew.org/]. >Please send your feedback to patchew-de...@redhat.com -- Wei Yang Help you, Help me
Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
Patchew URL: https://patchew.org/QEMU/20190430034412.12935-1-richardw.y...@linux.intel.com/ Hi, This series failed the docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN === #!/bin/bash time make docker-test-mingw@fedora SHOW_ENV=1 J=14 NETWORK=1 === TEST SCRIPT END === The full log is available at http://patchew.org/logs/20190430034412.12935-1-richardw.y...@linux.intel.com/testing.docker-mingw@fedora/?type=message. --- Email generated automatically by Patchew [https://patchew.org/]. Please send your feedback to patchew-de...@redhat.com
[Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
The *start* of migration_bitmap_sync_range is always 0, we can remove this parameter. Since RAMBlock->offset is always *word* aligned, we can remove the check on offset and simplify the logic a little. Wei Yang (3): migration/ram.c: start of migration_bitmap_sync_range is always 0 migration/ram.c: start of cpu_physical_memory_sync_dirty_bitmap is always 0 ram: RAMBlock->offset is always aligned to a word include/exec/ram_addr.h | 24 migration/ram.c | 8 2 files changed, 16 insertions(+), 16 deletions(-) -- 2.19.1
