Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
Greatly simplifies the code, now that we let the block layer
take care of alignment and read-modify-write on our behalf :)
In fact, we no longer need to include 'buf' in the migration
stream
2.7 material, depends on Kevin's block-next:
git://repo.or.cz/qemu/kevin.git block-next
Previously posted as part of a larger NBD series [1] and as v6 [3].
Mostly orthogonal to Kevin's recent work to also kill sector
interfaces from the driver.
[1]
qemu-io is the last user of several sector-based interfaces.
This patch upgrades to the new interfaces under the hood,
then deletes the resulting dead code. Note that for maximum
back-compat, while the -p option is no longer required to get
blk_pread(), it is still needed to allow for unaligned
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?
Otherwise,
Reviewed-by: Richard Henderson
r~
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/cpu.h | 8
target-m68k/translate.c | 46 ++
2 files changed, 22 insertions(+), 32 deletions(-)
Reviewed-by: Richard
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
From: Richard Henderson
Separate all ccr bits. Continue to batch updates via cc_op.
Signed-off-by: Richard Henderson
Fix gen_logic_cc() to really extend the size of the result.
Fix gen_get_ccr(): update cc_op
Richard Henderson writes:
> On 05/04/2016 10:12 AM, Laurent Vivier wrote:
>> +DEST_EA(env, insn, OS_BYTE, dest, NULL);
>> +tcg_temp_free(dest);
>> +}
>> +
>> +DISAS_INSN(dbcc)
>> +{
>> +TCGLabel *l1;
>> +TCGv reg;
>> +TCGv tmp;
>> +int16_t offset;
>> +
Right now if SDL2 is installed but not SDL1, default configure will
entirely disable SDL. Check upfront for SDL2 using pkg-config, but
still prefer SDL1 if both versions are installed.
Signed-off-by: Cole Robinson
---
configure | 12 +++-
1 file changed, 11
gtk and sdl2 are nearly unusable on Fedora 24 at the moment.
The first two patches fix the worst issues. The remaining patches
are just extra bits that came about while I was digging into this.
Thanks,
Cole
Cole Robinson (10):
ui: gtk: fix crash when terminal inner-border is NULL
ui: sdl2:
Simplifies printing library versions, dependent on if the library
was even found
Signed-off-by: Cole Robinson
---
configure | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/configure b/configure
index 8e25a24..76600f4 100755
---
Signed-off-by: Cole Robinson
---
configure | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/configure b/configure
index 55bd354..22cf55c 100755
--- a/configure
+++ b/configure
@@ -2448,10 +2448,10 @@ fi
if $pkg_config $sdlname --exists; then
On 05/06/2016 07:31 AM, Kevin Wolf wrote:
>>
>> Maybe I need to take that back. Using e.g. blockdev-backup, you can
>> indeed see the target in query-block.
>>
>> Where mnt is a file system and test.qcow2 is large enough such that an
>> ENOSPC will occur.
>
> Hm... Let's pretend we didn't
On 13.04.2016 10:33, Changlong Xie wrote:
> From: Wen Congyang
>
> Signed-off-by: Wen Congyang
> Signed-off-by: zhanghailiang
> Signed-off-by: Gonglei
> Signed-off-by: Changlong Xie
Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
Signed-off-by: Eric Blake
---
hw/block/pflash_cfi01.c | 12 ++--
hw/block/pflash_cfi02.c | 12 ++--
2 files changed, 12 insertions(+), 12 deletions(-)
Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
This file is doing some complex computations to map various
flash page sizes (256, 512, and 2048) atop generic uses of
512-byte sector operations. Perhaps someone will want to tidy
up the
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Richard Henderson
r~
Sector-based blk_aio_readv() and blk_aio_writev() should die; switch
to byte-based blk_aio_preadv() and blk_aio_pwritev() instead.
The patch had to touch multiple files at once, because dma_blk_io()
takes pointers to the functions, and ide_issue_trim() piggybacks on
the same interface (while
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
From: John Paul Adrian Glaubitz
Signed-off-by: John Paul Adrian Glaubitz
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 5 +
1 file changed, 5
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/cpu.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
Reviewed-by: Richard Henderson
r~
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Copied from target-i386
Signed-off-by: Laurent Vivier
---
target-m68k/cpu.h | 5 +-
target-m68k/translate.c | 121 +---
2 files changed, 86 insertions(+), 40 deletions(-)
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 34 +++---
1 file changed, 15 insertions(+), 19 deletions(-)
Reviewed-by: Richard Henderson
r~
Sector-based blk_read() should die; convert the one-off
variant blk_read_unthrottled().
Signed-off-by: Eric Blake
---
include/sysemu/block-backend.h | 4 ++--
block/block-backend.c | 8
hw/block/hd-geometry.c | 2 +-
3 files changed, 7 insertions(+),
sdl 2.0.4 currently has a bug which causes our UI shortcuts to fire
rapidly in succession:
https://bugzilla.libsdl.org/show_bug.cgi?id=3287
It's a toss up whether ctrl+alt+f or ctrl+alt+2 will fire an
odd or even number of times, thus determining whether the action
succeeds or fails.
Opening
All device manager APIs are deprecated now. Much of our usage is
just to get the current pointer, so centralize that logic and use
the new seat APIs
Signed-off-by: Cole Robinson
---
The remaining warnings look like they'll take a bit more effort
ui/gtk.c | 20
Signed-off-by: Cole Robinson
---
configure | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 76600f4..55bd354 100755
--- a/configure
+++ b/configure
@@ -2157,6 +2157,7 @@ if test "$gtk" != "no"; then
if $pkg_config
QOM instance_init functions are not supposed to have any side-effects,
as new objects may be created at any moment for querying property
information (see qmp_device_list_properties()).
Move TCG initialization to realize time so it won't be called when just
doing object_new() on a X86CPU subclass.
Instead of requiring cpu.c to check if TCG was already initialized,
simply let the function be called multiple times.
Suggested-by: Igor Mammedov
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 4 +---
target-i386/translate.c | 6 ++
2
Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
Signed-off-by: Eric Blake
---
hw/block/fdc.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --git a/hw/block/fdc.c
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Scaled index is not supported by 68000, 68008, and 68010.
EA = (bd + PC) + Xn.SIZE*SCALE + od
Ignore it:
M68000 FAMILY PROGRAMMER’S REFERENCE MANUAL
2.4 BRIEF EXTENSION WORD FORMAT COMPATIBILITY
"If the MC68000 were to execute an instruction
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
Reviewed-by: Richard Henderson
r~
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
From: Andreas Schwab
Signed-off-by: Andreas Schwab
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by:
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Copied from target-i386
Signed-off-by: Laurent Vivier
---
cpu-exec.c | 6 --
target-m68k/cpu-qom.h | 4
target-m68k/cpu.c | 2 --
target-m68k/cpu.h | 1 +
target-m68k/helper.c| 20
Sector-based blk_read() should die; switch to byte-based
blk_pread() instead.
Add new defines ATAPI_SECTOR_BITS and ATAPI_SECTOR_SIZE to
use anywhere we were previously scaling BDRV_SECTOR_* by 4,
for better legibility.
Signed-off-by: Eric Blake
---
v4: add new defines for
On 05/06/2016 06:00 AM, Alberto Garcia wrote:
> On Fri 29 Apr 2016 05:00:57 PM CEST, Kevin Wolf wrote:
>
>>> - Block jobs can now be identified by the node name of their
>>> BlockDriverState in addition to the device name. Since both device
>>> and node names live in the same namespace there's
Sector-based blk_write() should die; convert the one-off
variant blk_write_zeroes() to use an offset/count interface
instead. Likewise for blk_co_write_zeroes() and
blk_aio_write_zeroes().
Signed-off-by: Eric Blake
---
include/sysemu/block-backend.h | 12 ++--
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 | 82 ++--
3 files changed,
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 53 -
1 file changed, 22 insertions(+), 31 deletions(-)
Reviewed-by: Richard Henderson
r~
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/cpu.h | 1 -
target-m68k/helper.c| 28 ++--
target-m68k/helper.h| 2 +-
target-m68k/translate.c | 4 ++--
4 files changed, 17 insertions(+),
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
From: Richard Henderson
Signed-off-by: Richard Henderson
fix arithmetical/logical switch
Signed-off-by: Laurent Vivier
---
target-m68k/helper.c| 52 ---
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
+
+#define COMPUTE_CCR(op, x, n, z, v, c) { \
+switch (op) { \
+case CC_OP_FLAGS: \
Please do
QOM instance_init functions are not supposed to have any side-effects,
as new objects may be created at any moment for querying property
information (see qmp_device_list_properties()).
Calling cpu_exec_init() also affects QEMU's ability to handle errors
during CPU creation, as some actions done
This makes the feature name tables in feature_word_info all match
the actual QOM property names we use.
This will make the command-line interface more consistent,
allowing the QOM property names to be used as "-cpu" arguments
directly.
Add extra feat2prop() calls to x86_cpu_parse_featurestr() to
This series extends query-cpu-definitions to include two extra
fields: "runnable", and "unavailable-features".
This will return information based on the current machine and
accelerator only. In the future we may extend these mechanisms to
allow querying other machines and other accelerators
vte >= 0.37 expores API version 2.91, which is where all the active
development is. qemu builds and runs fine with that version, so use it
if it's available.
Signed-off-by: Cole Robinson
---
configure | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
Instead of using the builtin_x86_defs array, use the QOM subclass list
to list CPU models on "-cpu ?" and "query-cpu-definitions".
Signed-off-by: Andreas Färber
[ehabkost: copied code from a patch by Andreas:
"target-i386: QOM'ify CPU", from March 2012]
Signed-off-by: Eduardo
Enable EL2 by default for the A53s and A57s.
Signed-off-by: Alistair Francis
---
target-arm/cpu64.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target-arm/cpu64.c b/target-arm/cpu64.c
index 1635deb..59a2042 100644
--- a/target-arm/cpu64.c
+++
Fill the "runnable" and "unavailable-features" fields on the x86
implementation of query-cpu-definitions.
Example command output:
{
"return": [
{ "runnable": true, "name": "host"},
{ "runnable": true, "name": "qemu64"},
{ "runnable": true, "name": "qemu32"},
x86_cpu_filter_features() will be reused by code that shouldn't
print any warning. Move the warning code to a new
x86_cpu_report_filtered_features() function, and call it from
x86_cpu_realizefn().
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 28
blk_aio_readv() and blk_aio_writev() are annoying in that they
can't access sub-sector granularity, and cannot pass flags.
Also, they require the caller to pass redundant information
about the size of the I/O (qiov->size in bytes must match
nb_sectors in sectors).
Add new blk_aio_preadv() and
Sector-based blk_aio_readv() and blk_aio_writev() should die; switch
to byte-based blk_aio_preadv() and blk_aio_pwritev() instead.
Signed-off-by: Eric Blake
---
hw/block/xen_disk.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git
Sector-based blk_aio_readv() and blk_aio_writev() should die; switch
to byte-based blk_aio_preadv() and blk_aio_pwritev() instead.
As part of the cleanup, scsi_init_iovec() no longer needs to return
a value, and reword a comment.
Signed-off-by: Eric Blake
---
v7: remove more
On Fri, 6 May 2016 09:38:41 +0800
Chen Fan wrote:
> On 04/26/2016 10:48 PM, Alex Williamson wrote:
> > On Tue, 26 Apr 2016 11:39:02 +0800
> > Chen Fan wrote:
> >
> >> On 04/14/2016 09:02 AM, Chen Fan wrote:
> >>> On 04/12/2016
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/cpu.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
Reviewed-by: Richard Henderson
r~
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
-uint32_t cpu_m68k_flush_flags(CPUM68KState *env, int op)
+static uint32_t cpu_m68k_flush_flags(CPUM68KState *env, int op)
{
int flags;
uint32_t src;
@@ -271,6 +271,18 @@ set_x:
return flags;
}
+uint32_t
On Fri, May 06, 2016 at 06:34:33AM +0200, Ingo Krabbe wrote:
> > On Sun, May 01, 2016 at 02:31:57PM +0200, Ingo Krabbe wrote:
> >> Good Mayday Qemu Developers,
> >>
> >> today I tried to find a reference to a networking problem, that seems to
> >> be of quite general nature: TCP Segmentation
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
+tcg_gen_or_i32(QREG_CC_Z, QREG_CC_Z, QREG_CC_N); /* !Z is sticky */
+gen_ext(QREG_CC_Z, QREG_CC_Z, opsize, 0);
Extending Z after the OR is a bug.
The (old) high bits of Z might be set from a previous word operation (i.e. !Z)
which is
Laurent Vivier writes:
> From: Andreas Schwab
>
> Signed-off-by: Andreas Schwab
> Signed-off-by: Laurent Vivier
> ---
> target-m68k/translate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Now that there are no remaining clients, we can drop the
sector-based blk_read(), blk_write(), blk_aio_readv(), and
blk_aio_writev(). Sadly, there are still remaining
sector-based interfaces, such as blk_*discard(), or
blk_write_compressed(); those will have to wait for another
day.
Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
This particular device picks its size during onenand_initfn(),
and can be at most 0x8000 bytes; therefore, shifting an
'int sec' request to get back to a byte offset should never
overflow
Sector-based blk_write() should die; switch to byte-based
blk_pwrite() instead. Likewise for blk_read().
Signed-off-by: Eric Blake
---
qemu-img.c | 28 +++-
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index
Sector-based blk_aio_readv() and blk_aio_writev() should die; switch
to byte-based blk_aio_preadv() and blk_aio_pwritev() instead.
The trace is modified at the same time, and nb_sectors is now
unused. Fix a comment typo while in the vicinity.
Signed-off-by: Eric Blake
---
On Fri, May 06, 2016 at 10:44:41AM +0530, Vikhyat Umrao wrote:
> On Fri, May 6, 2016 at 6:14 AM, Fam Zheng wrote:
>
> > On Thu, 05/05 15:06, Jeff Cody wrote:
> > > On Thu, May 05, 2016 at 06:45:15PM +0100, Stefan Hajnoczi wrote:
> > > > On Mon, May 02, 2016 at 09:55:17PM +0530,
Sector-based blk_read() should die; switch to byte-based
blk_pread() instead.
Likewise for blk_aio_readv() and blk_aio_writev().
Signed-off-by: Eric Blake
---
hw/block/m25p80.c | 23 +++
1 file changed, 7 insertions(+), 16 deletions(-)
diff --git
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
This patch defines seven new features:
- M68K_FEATURE_SCALED_INDEX, scaled address index register
- M68K_FEATURE_LONG_MULDIV, 32bit multiply/divide
- M68K_FEATURE_QUAD_MULDIV, 64bit multiply/divide
- M68K_FEATURE_BCCL, long
We have several block drivers that understand BDRV_REQ_FUA,
and emulate it in the block layer for the rest by a full flush.
But without a way to actually request BDRV_REQ_FUA during a
pass-through blk_pwrite(), FUA-aware block drivers like NBD are
forced to repeat the emulation logic of a full
On 05/04/2016 10:11 AM, Laurent Vivier wrote:
Read a 8, 16 or 32bit immediat constant.
An immediate constant is stored in the instruction opcode and
can be in one or two extension words.
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 91
So here's my admittedly quick and dirty solution. This patch adds
support for evdev keycodes using translate_evdev_keycode when
GDK_WINDOWING_WAYLAND is defined.
Affected functions:
ui/gtk.c:gd_set_keycode_type
ui/gtk.c:gd_map_keycode
The caveat with this patch is that I don't see any good way
On 01.04.2016 19:49, Olaf Hering wrote:
> On Fri, Apr 01, Max Reitz wrote:
>
>> In any case, do you have a test case where a guest was able to submit a
>> request that led to the overflow error you described in the commit message?
>
> mkfs -t ext4 /dev/sdb1 in a xen guest with qcow2 as backing
On 05/06/2016 10:21 AM, Eric Blake wrote:
> On 05/06/2016 10:08 AM, Max Reitz wrote:
>> On 05.05.2016 05:42, Eric Blake wrote:
>>> When opening a file from the command line, qemu-io defaults
>>> to BDRV_O_UNMAP but allows -d to give full control to disable
>>> unmaps. But when opening via the
On 05/04/2016 10:12 AM, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
---
target-m68k/translate.c | 46 ++
1 file changed, 46 insertions(+)
diff --git a/target-m68k/translate.c b/target-m68k/translate.c
index
On Fri, May 6, 2016 at 2:05 PM, Kevin Wolf wrote:
>>
>> Reviewed-by: Fam Zheng
>
> Thanks, applied to block-next.
Great, thanks everyone!
--
Janne
VTE terminal inner-border can be NULL. The vte-0.36 (API 2.90)
code checks for the condition too so I assume it's not just a bug
Fixes a crash on Fedora 24 with gtk 3.20
Signed-off-by: Cole Robinson
---
ui/gtk.c | 10 ++
1 file changed, 6 insertions(+), 4
inner-border was dropped in vte API 2.91, in favor of the standard
padding style
Signed-off-by: Cole Robinson
---
ui/gtk.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index 9876d89..d156c8a 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@
I accidentally tried --with-sdlabi="1.0", and it failed much later in
a weird way. Instead, throw an error if the value isn't in our
whitelist.
Signed-off-by: Cole Robinson
---
configure | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure
Just move code to another place so the it can be reused by the
query-cpu-definitions code.
Signed-off-by: Eduardo Habkost
---
target-i386/cpu.c | 68 +++
1 file changed, 34 insertions(+), 34 deletions(-)
diff --git
Add the Hypervisor System Trap Register for EL2.
This register is used early in the Linux boot and without it the kernel
aborts with a "Synchronous Abort" error.
Signed-off-by: Alistair Francis
---
target-arm/helper.c | 7 +++
1 file changed, 7 insertions(+)
Extend query-cpu-definitions schema to allow it to return two new
optional fields: "runnable" and "unavailable-features".
"runnable" will tell if the CPU model can be run in the current
host. "unavailable-features" will contain a list of CPU
properties that are preventing the CPU model from
Now that EL3 is enabled by default for the A53s and A57s I see this
error when booting Linux on the ZynqMP board:
"Synchronous Abort" handler, esr 0x0200
By adding the HSTR_EL2 register (and EL2 support) the Linux boot
progresses much further.
Alistair Francis (2):
target-arm: Add the
On 05/06/2016 06:31 AM, Markus Armbruster wrote:
>> So all that's left are the two output functions. Can we get rid
>> of those, and make Visitor* the only public interface, rather than
>> making every caller have to do upcasts?
>
> The two output functions are
>
> QObject
On 05.05.2016 05:42, Eric Blake wrote:
> When opening a file from the command line, qemu-io defaults
> to BDRV_O_UNMAP but allows -d to give full control to disable
> unmaps. But when opening via the 'open' command, qemu-io did
> not set BDRV_O_UNMAP, and had no way to allow it.
>
> Make it at
On 5/6/2016 5:44 PM, Jike Song wrote:
> On 05/05/2016 05:06 PM, Tian, Kevin wrote:
>>> From: Kirti Wankhede
>>>
>>> >> + * @validate_map_request: Validate remap pfn request
>>> >> + * @vdev: vgpu device structure
>>> >> + *
Laurent Vivier writes:
> What is the version of gcc?
It doesn't matter, any version.
> what are your configure parameters?
Nothing special.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now
On Fri, Apr 15, 2016 at 04:10:37PM +0800, Changlong Xie wrote:
> +static void replication_close(BlockDriverState *bs)
> +{
> +BDRVReplicationState *s = bs->opaque;
> +
> +if (s->mode == REPLICATION_MODE_SECONDARY) {
> +g_free(s->top_id);
> +}
> +
> +if (s->replication_state
On 05/06/2016 06:31 AM, Kevin Wolf wrote:
>> +++ b/include/sysemu/block-backend.h
>> @@ -110,9 +110,15 @@ int64_t blk_nb_sectors(BlockBackend *blk);
>> BlockAIOCB *blk_aio_readv(BlockBackend *blk, int64_t sector_num,
>>QEMUIOVector *iov, int nb_sectors,
>>
Am 06.05.2016 um 15:40 hat Max Reitz geschrieben:
> On 06.05.2016 15:31, Kevin Wolf wrote:
> > Am 06.05.2016 um 14:32 hat Max Reitz geschrieben:
> >> On 06.05.2016 14:01, Max Reitz wrote:
> >>> On 27.04.2016 15:20, Kevin Wolf wrote:
> When block job errors were introduced, we assigned the
When running fstrim on a filesystem mounted through qemu-nbd with
--discard=on, fstrim would fail with I/O errors:
$ fstrim /k/spl/ice/
fstrim: /k/spl/ice/: FITRIM ioctl failed: Input/output error
and qemu-nbd was spitting these:
nbd.c:nbd_co_receive_request():L1232: len (94621696) is
On 05/06/2016 07:11 AM, Kevin Wolf wrote:
> Am 05.05.2016 um 01:55 hat Eric Blake geschrieben:
>> 2.7 material, depends on Kevin's block-next:
>> git://repo.or.cz/qemu/kevin.git block-next
>>
>> Previously posted as part of a larger NBD series [1] and as v5 [2].
>> Mostly orthogonal to Kevin's
On 05.05.2016 05:42, Eric Blake wrote:
> We require a C99 compiler; let's use it to express what we
> really mean.
>
> Signed-off-by: Eric Blake
> ---
> qemu-io-cmds.c | 94
> +-
> 1 file changed, 47 insertions(+), 47
On 05.05.2016 05:42, Eric Blake wrote:
> Commit 499afa2 added --image-opts, but forgot to document it in
> --help. Likewise for commit 9e8f183 and -d/--discard.
>
> Finally, commit 10d9d75 removed -g/--growable, but forgot to
> cull it from the valid short options.
>
> Signed-off-by: Eric Blake
On 05.05.2016 05:42, Eric Blake wrote:
> 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
>
On 05/06/2016 10:05 AM, Max Reitz wrote:
> On 05.05.2016 05:42, Eric Blake wrote:
>> 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',
On Fri 22 Apr 2016 07:42:37 PM CEST, Kevin Wolf wrote:
> BlockBackends use it to get a back pointer from BdrvChild to
> BlockBackend in any BdrvChildRole callbacks.
>
> Signed-off-by: Kevin Wolf
Reviewed-by: Alberto Garcia
Berto
On Fri 22 Apr 2016 07:42:38 PM CEST, Kevin Wolf wrote:
> This removes the last part of I/O throttling from block/io.c and moves
> it to the BlockBackend.
>
> Instead of having knowledge about throttling inside io.c, we can call a
> BdrvChild callback .drained_begin/end, which happens to drain the
Here is a testcase:
when compiling tlink.c from the gcc sources with gcc-6 r234449 (which
was bootstrapped in aranym):
$ g++ -fno-PIE -c -fomit-frame-pointer -O2 -DIN_GCC -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual
Am 06.05.2016 um 16:18 hat Eric Blake geschrieben:
> On 05/06/2016 06:50 AM, Kevin Wolf wrote:
> > Am 05.05.2016 um 01:55 hat Eric Blake geschrieben:
> >> @@ -1730,13 +1730,11 @@ static void scsi_write_same_complete(void *opaque,
> >> int ret)
> >> if (data->iov.iov_len) {
> >>
On Fri, Apr 15, 2016 at 04:10:30PM +0800, Changlong Xie wrote:
> Block replication is a very important feature which is used for
> continuous checkpoints(for example: COLO).
>
> You can get the detailed information about block replication from here:
>
On 05.05.2016 05:42, Eric Blake wrote:
> 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 'qemu-io -d unmap' (or the
>
On 05/06/2016 09:59 AM, Max Reitz wrote:
> On 05.05.2016 05:42, Eric Blake wrote:
>> 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
Andreas Schwab writes:
> Here is a testcase:
>
> when compiling tlink.c from the gcc sources with gcc-6 r234449 (which
> was bootstrapped in aranym):
>
> $ g++ -fno-PIE -c -fomit-frame-pointer -O2 -DIN_GCC -fno-exceptions
> -fno-rtti -fasynchronous-unwind-tables -W
23.02.2016 11:44, Alberto Garcia wrote:
> I'm not really using the old one anymore.
>
> Signed-off-by: Alberto Garcia
Applied to -trivial, finally. I'm sorry this took so long.
Thank you for the patience!
/mjt
1 - 100 of 239 matches
Mail list logo