The Usage: summary is missing several options, but rather than
having to maintain it, it's simpler to just state [OPTIONS],
since the options are spelled out below.
Commit 499afa2 added --image-opts, but forgot to document it in
--help. Likewise for commit 9e8f183 and -d/--discard.
Commit e3aff4
On 05/07/2016 09:16 PM, Eric Blake wrote:
> While working on NBD, I found myself cursing the qemu-io UI for
> not letting me test various scenarios, particularly after fixing
> NBD to serve at byte granularity [1]. And in the process of
> writing these qemu-io enhancements, I also managed to flush
Make it easier to test block drivers with BDRV_REQ_FUA in
.supported_write_flags, by adding the '-f' flag to qemu-io to
conditionally pass the flag through to specific writes ('write',
'write -z', 'writev', 'aio_write', 'aio_write -z'). You'll want
to use 'qemu-io -t none' to actually make -f usefu
We require a C99 compiler; let's use it to express what we
really mean.
(Yes, we now have an instance of 'if (bool + bool + bool > 1)',
which, although semantically valid C, looks ugly; it gets
cleaned up later.)
Signed-off-by: Eric Blake
Reviewed-by: Max Reitz
---
v5: tweak commit message
---
There's no reason to require the user to specify a flag just so
they can pass in unaligned numbers. Keep 'read -p' and 'write -p'
as no-ops so that I don't have to hunt down and update all users
of qemu-io, but otherwise make their behavior default as 'read' and
'write'. Also fix 'write -z', 'rea
While working on NBD, I found myself cursing the qemu-io UI for
not letting me test various scenarios, particularly after fixing
NBD to serve at byte granularity [1]. And in the process of
writing these qemu-io enhancements, I also managed to flush out
several other bugs in the block layer proper,
The command line defaults to BDRV_O_UNMAP, but can use
-d to reset it. Meanwhile, the 'open' subcommand was
defaulting to no discards, with no way to set it.
The command line has both -n and -tMODE to set a variety
of cache modes, but the 'open' subcommand had only -n.
The 'open' subcommand had
Make it easier to control whether the BDRV_REQ_MAY_UNMAP flag
can be passed through a write_zeroes command, by adding the '-u'
flag to qemu-io 'write -z' and 'aio_write -z'. To be useful,
the device has to be opened with BDRV_O_UNMAP (done by default
in qemu-io, but can be made explicit with '-d u
Hello,
I would like to read at a particular RAM target address from the QEMU
side, but I didn't find where I have to do.
Is someone could give me an example ?
Many thanks,
On 7 May 2016 at 20:01, Laurent Vivier wrote:
>
>
> Le 07/05/2016 à 00:00, Richard Henderson a écrit :
>> On 05/04/2016 11:21 AM, Laurent Vivier wrote:
>>> +reg = AREG(insn, 0);
>>> +src = gen_load(s, opsize, reg, 1);
>>> +tcg_gen_addi_i32(reg, reg, opsize_bytes(opsize));
>>> +
>>> +
Le 07/05/2016 à 00:00, Richard Henderson a écrit :
> On 05/04/2016 11:21 AM, Laurent Vivier wrote:
>> +reg = AREG(insn, 0);
>> +src = gen_load(s, opsize, reg, 1);
>> +tcg_gen_addi_i32(reg, reg, opsize_bytes(opsize));
>> +
>> +reg = AREG(insn, 9);
>> +dest = gen_load(s, opsize,
On 7 May 2016 at 09:08, embedded0n3 wrote:
> Public bug reported:
>
> Report based on:
> https://stackoverflow.com/questions/37068688/have-you-got-issues-with-running-u-boot-for-versatile-express-a9-platform-under
>
> I don't see any bug reports about vexpress boards emulation here, so I
> decided
Public bug reported:
Report based on:
https://stackoverflow.com/questions/37068688/have-you-got-issues-with-running-u-boot-for-versatile-express-a9-platform-under
I don't see any bug reports about vexpress boards emulation here, so I
decided to let you know:
version tested: qemu 2.0.0 on 32 bit
On 2016-05-06 22:53, Radim Krčmář wrote:
> The capability alows us to express x2APIC destinations.
"allows"
Will the possibility to create >254 CPUs be indirectly coupled to this
capability, or should userland check for it explicitly then?
Will the kernel handle the case gracefully that AMD CPUs
On 2016-05-06 22:53, Radim Krčmář wrote:
> The only way to send interrupts from outside of APIC devices is to use
> the MSI-inspired memory mapped interface. The interface is not
> sufficient because interrupt remapping in extended mode can exceed 8 bit
> destination ids.
>
> The proper way to de
On 01/14/2016 02:28 PM, Denis V. Lunev wrote:
This patch does 2 things:
- it merges all snapshot validity checks for load_vmstate into one function
- it now selects BDS to load VM state by availability of the state in the
snapshot
This commit is preparatory to allow to select BDS to save snap
23.03.2016 17:59, Stefan Weil wrote:
[...]
FINALLY! Applied to -trivial. With the additional fix
suggested by Peter, and without util/qemu-sockets.c
change which has been applied meanwhile.
Thank you!
/mjt
Le 06/05/2016 à 18:45, Richard Henderson a écrit :
> On 05/04/2016 10:11 AM, Laurent Vivier wrote:
>> Signed-off-by: Laurent Vivier
>> ---
>> target-m68k/cpu.h | 14 -
>> target-m68k/helper.c| 139
>> ++--
>> target-m68k/translate.c |
Le 06/05/2016 à 18:42, Richard Henderson a écrit :
> On 05/04/2016 10:11 AM, Laurent Vivier wrote:
>> +INSN(bkpt, 4848, fff8, M68000);
>
> Do we care that this comes in with 68010 not 68000?
Yes, you're right: I'm adding M68K_FEATURE_BKPT to enable it only on 68010+
> Otherwise,
>
>
19 matches
Mail list logo
