Re: [Qemu-devel] [RFC PATCH for 4.1?] target/ppc: move opcode decode tables to PowerPCCPU

2019-07-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190716121352.302-1-alex.ben...@linaro.org/ 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 ma

Re: [Qemu-devel] [RFC PATCH for 4.1?] target/ppc: move opcode decode tables to PowerPCCPU

2019-07-17 Thread Alex Bennée
David Gibson writes: > On Tue, Jul 16, 2019 at 01:13:52PM +0100, Alex Bennée wrote: >> The opcode decode tables aren't really part of the CPUPPCState but an >> internal implementation detail for the translator. This can cause >> problems with memcpy in cpu_copy as any table created during >> pp

Re: [Qemu-devel] [RFC PATCH for 4.1?] target/ppc: move opcode decode tables to PowerPCCPU

2019-07-16 Thread David Gibson
On Tue, Jul 16, 2019 at 01:13:52PM +0100, Alex Bennée wrote: > The opcode decode tables aren't really part of the CPUPPCState but an > internal implementation detail for the translator. This can cause > problems with memcpy in cpu_copy as any table created during > ppc_cpu_realize get written over

Re: [Qemu-devel] [RFC PATCH for 4.1?] target/ppc: move opcode decode tables to PowerPCCPU

2019-07-16 Thread Richard Henderson
On 7/16/19 12:13 PM, Alex Bennée wrote: > The opcode decode tables aren't really part of the CPUPPCState but an > internal implementation detail for the translator. This can cause > problems with memcpy in cpu_copy as any table created during > ppc_cpu_realize get written over causing a memory leak

[Qemu-devel] [RFC PATCH for 4.1?] target/ppc: move opcode decode tables to PowerPCCPU

2019-07-16 Thread Alex Bennée
The opcode decode tables aren't really part of the CPUPPCState but an internal implementation detail for the translator. This can cause problems with memcpy in cpu_copy as any table created during ppc_cpu_realize get written over causing a memory leak. To avoid this move the tables into PowerPCCPU