On Wed, Jan 28, 2015 at 4:39 PM, Peter Maydell wrote:
> On 28 January 2015 at 15:10, Laurent Desnogues
> wrote:
>> - environment variables which are parsed by the runtime
>> at process start; to get around that issue you'll have
>> to reintroduce -ignore-environment which was removed
>> so
On 28 January 2015 at 15:10, Laurent Desnogues
wrote:
> - environment variables which are parsed by the runtime
> at process start; to get around that issue you'll have
> to reintroduce -ignore-environment which was removed
> some time ago (see commit
> fc9c54124d134dbd76338a92a91804dab2d
On Mon, Jan 26, 2015 at 9:54 PM, Javier Picorel wrote:
> Hi,
>
> We are trying to make QEMU deterministic for
> architectural simulation. In the absence of I/O,
> let’s say only executing user code or exceptions,
> is there any source of indeterminism (e.g., non
> deterministic compiler optimizati
On 26/01/2015 21:54, Javier Picorel wrote:
> Hi,
>
> We are trying to make QEMU deterministic for
> architectural simulation. In the absence of I/O,
> let’s say only executing user code or exceptions,
> is there any source of indeterminism (e.g., non
> deterministic compiler optimizations, T
Hi,
We are trying to make QEMU deterministic for
architectural simulation. In the absence of I/O,
let’s say only executing user code or exceptions,
is there any source of indeterminism (e.g., non
deterministic compiler optimizations, TB indeterminism)
of QEMU’s DBT versus a canonical interpre
