Re: [Qemu-block] [PATCH 4/4] block: drop bs->job

2019-06-17 Thread Vladimir Sementsov-Ogievskiy
17.06.2019 19:58, Kevin Wolf wrote: > Am 06.06.2019 um 17:41 hat Vladimir Sementsov-Ogievskiy geschrieben: >> Drop remaining users of bs->job: >> 1. assertions actually duplicated by assert(!bs->refcnt) >> 2. trace-point seems not enough reason to change stream_start to return >> BlockJob point

Re: [Qemu-block] [PATCH 4/4] block: drop bs->job

2019-06-17 Thread Kevin Wolf
Am 06.06.2019 um 17:41 hat Vladimir Sementsov-Ogievskiy geschrieben: > Drop remaining users of bs->job: > 1. assertions actually duplicated by assert(!bs->refcnt) > 2. trace-point seems not enough reason to change stream_start to return >BlockJob pointer > 3. Restricting creation of two jobs ba

Re: [Qemu-block] [SeaBIOS] [QEMU] [PATCH v3 0/8] Add Qemu to SeaBIOS LCHS interface

2019-06-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190617150950.5264-1-shmuel.eider...@oracle.com/ Hi, This series seems to have some coding style problems. See output below for more information: Message-id: 20190617150950.5264-1-shmuel.eider...@oracle.com Type: series Subject: [SeaBIOS] [QEMU] [PATCH v

Re: [Qemu-block] [PATCH v8 4/7] block: introduce backup-top filter driver

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 18:01 hat Max Reitz geschrieben: > >>> Should new implicit/explicit > >>> filters be created above or under them? > >> > >> That was always the most difficult question we had when we introduced > >> filters. > >> > >> The problem is that we never answered it in our code base. > >>

Re: [Qemu-block] [SeaBIOS] [QEMU] [PATCH v3 0/8] Add Qemu to SeaBIOS LCHS interface

2019-06-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190617150950.5264-1-shmuel.eider...@oracle.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/ba

Re: [Qemu-block] [PATCH v8 4/7] block: introduce backup-top filter driver

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 16:56 hat Max Reitz geschrieben: > On 17.06.19 12:36, Vladimir Sementsov-Ogievskiy wrote: > > 14.06.2019 23:03, Max Reitz wrote: > >> On 14.06.19 18:22, Vladimir Sementsov-Ogievskiy wrote: > >>> 14.06.2019 15:57, Max Reitz wrote: > On 14.06.19 11:04, Vladimir Sementsov-Ogievsk

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Sam Eiderman
> On 17 Jun 2019, at 17:48, Kevin O'Connor wrote: > > On Mon, Jun 17, 2019 at 10:36:54AM +0300, Sam Eiderman wrote: >> So overall, WDYT? >> Keep it extendible for a low price of ABI + “bootdevices” name. >> Or go strict and rename to “bios-geometries”? > > If we add another qemu to firmware i

Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 13:37 hat Vladimir Sementsov-Ogievskiy geschrieben: > 08.06.2019 1:26, John Snow wrote: > > > > > > On 6/3/19 8:00 AM, Vladimir Sementsov-Ogievskiy wrote: > >> Hi all! > >> > >> Here is block-dirty-bitmap-remove transaction action. > >> > >> It is used to do transactional movemen

[Qemu-block] [QEMU] [PATCH v3 3/8] bootdevice: Add interface to gather LCHS

2019-06-17 Thread Sam Eiderman
Add an interface to provide direct logical CHS values for boot devices. We will use this interface in the next commits. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- bootdevice.c| 55 + include/sys

Re: [Qemu-block] [PATCH v8 4/7] block: introduce backup-top filter driver

2019-06-17 Thread Max Reitz
On 17.06.19 17:53, Kevin Wolf wrote: > Am 17.06.2019 um 16:56 hat Max Reitz geschrieben: >> On 17.06.19 12:36, Vladimir Sementsov-Ogievskiy wrote: >>> 14.06.2019 23:03, Max Reitz wrote: On 14.06.19 18:22, Vladimir Sementsov-Ogievskiy wrote: > 14.06.2019 15:57, Max Reitz wrote: >> On 14

[Qemu-block] [SeaBIOS] [PATCH v2 0/5] Add Qemu to SeaBIOS LCHS interface

2019-06-17 Thread Sam Eiderman
v1: Non-standard logical geometries break under QEMU. A virtual disk which contains an operating system which depends on logical geometries (consistent values being reported from BIOS INT13 AH=08) will most likely break under QEMU/SeaBIOS if it has non-standard logical geometries - for example 56

[Qemu-block] [QEMU] [PATCH v3 2/8] block: Support providing LCHS from user

2019-06-17 Thread Sam Eiderman
Add logical geometry variables to BlockConf. A user can now supply "lcyls", "lheads" & "lsecs" for any HD device that supports CHS ("cyls", "heads", "secs"). These devices include: * ide-hd * scsi-hd * virtio-blk-pci In future commits we will use the provided LCHS and pass it to the

[Qemu-block] [QEMU] [PATCH v3 0/8] Add Qemu to SeaBIOS LCHS interface

2019-06-17 Thread Sam Eiderman
v1: Non-standard logical geometries break under QEMU. A virtual disk which contains an operating system which depends on logical geometries (consistent values being reported from BIOS INT13 AH=08) will most likely break under QEMU/SeaBIOS if it has non-standard logical geometries - for example 56

[Qemu-block] [QEMU] [PATCH v3 1/8] block: Refactor macros - fix tabbing

2019-06-17 Thread Sam Eiderman
Fixing tabbing in block related macros. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- hw/ide/qdev.c| 2 +- include/hw/block/block.h | 16 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/hw/ide/qdev.c b/hw/ide/qde

[Qemu-block] [QEMU] [PATCH v3 5/8] bootdevice: Gather LCHS from all relevant devices

2019-06-17 Thread Sam Eiderman
Relevant devices are: * ide-hd (and ide-cd, ide-drive) * scsi-hd (and scsi-cd, scsi-disk, scsi-block) * virtio-blk-pci We do not call del_boot_device_lchs() for ide-* since we don't need to - IDE block devices do not support unplugging. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Mo

[Qemu-block] [QEMU] [PATCH v3 6/8] bootdevice: Refactor get_boot_devices_list

2019-06-17 Thread Sam Eiderman
Move device name construction to a separate function. We will reuse this function in the following commit to pass logical CHS parameters through fw_cfg much like we currently pass bootindex. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- bootdevice.c | 61 +

[Qemu-block] [QEMU] [PATCH v3 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Sam Eiderman
Using fw_cfg, supply logical CHS values directly from QEMU to the BIOS. Non-standard logical geometries break under QEMU. A virtual disk which contains an operating system which depends on logical geometries (consistent values being reported from BIOS INT13 AH=08) will most likely break under QEM

[Qemu-block] [SeaBIOS] [PATCH v2 5/5] geometry: Apply LCHS values for boot devices

2019-06-17 Thread Sam Eiderman
Boot devices which use overriden LCHS values are: * ata * ahci * scsi * esp * lsi * megasas * mpt * pvscsi * virtio * virtio-blk We use these values in get_translation() and setup_translation() by introducing a new translation type:

[Qemu-block] [SeaBIOS] [PATCH v2 3/5] geometry: Add boot_lchs_find_*() utility functions

2019-06-17 Thread Sam Eiderman
Adding the following utility functions: * boot_lchs_find_pci_device * boot_lchs_find_scsi_device * boot_lchs_find_ata_device These will be used to apply LCHS values received through fw_cfg. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- src/boo

[Qemu-block] [SeaBIOS] [PATCH v2 1/5] geometry: Read LCHS from fw_cfg

2019-06-17 Thread Sam Eiderman
Read bios geometry for boot devices from fw_cfg. By receiving LCHS values directly from QEMU through fw_cfg we will be able to support logical geometries which can not be inferred by SeaBIOS itself. (For instance: A 8GB virtio-blk hard drive which was originally created as an IDE and must report L

[Qemu-block] [SeaBIOS] [PATCH v2 4/5] config: Add toggle for bootdevice information

2019-06-17 Thread Sam Eiderman
Add the "BIOS_GEOMETRY" toggle to remove boot device information received through fw_cfg. We will use this toggle in QEMU to reduce the size of the 128k SeaBIOS rom, which is only used in old compat versions, where this boot device information does not exist. Reviewed-by: Karl Heubaum Reviewed-b

[Qemu-block] [SeaBIOS] [PATCH v2 2/5] boot: Reorder functions in boot.c

2019-06-17 Thread Sam Eiderman
Currently glob_prefix() and build_pci_path() are under the "Boot priority ordering" section. Move them to a new "Helper search functions" section since we will reuse them in the next commit. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- src/boot.c | 94

Re: [Qemu-block] [PATCH v8 4/7] block: introduce backup-top filter driver

2019-06-17 Thread Max Reitz
On 17.06.19 12:36, Vladimir Sementsov-Ogievskiy wrote: > 14.06.2019 23:03, Max Reitz wrote: >> On 14.06.19 18:22, Vladimir Sementsov-Ogievskiy wrote: >>> 14.06.2019 15:57, Max Reitz wrote: On 14.06.19 11:04, Vladimir Sementsov-Ogievskiy wrote: > 13.06.2019 18:57, Max Reitz wrote: >> On

[Qemu-block] [QEMU] [PATCH v3 8/8] hd-geo-test: Add tests for lchs override

2019-06-17 Thread Sam Eiderman
Add QTest tests to check the logical geometry override option. The tests in hd-geo-test are out of date - they only test IDE and do not test interesting MBRs. I added a few helper functions which will make adding more tests easier. QTest's fw_cfg helper functions support only legacy fw_cfg, so I

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Kevin O'Connor
On Mon, Jun 17, 2019 at 10:36:54AM +0300, Sam Eiderman wrote: > So overall, WDYT? > Keep it extendible for a low price of ABI + “bootdevices” name. > Or go strict and rename to “bios-geometries”? If we add another qemu to firmware interface I think the interface should be documented. I also think

[Qemu-block] [QEMU] [PATCH v3 4/8] scsi: Propagate unrealize() callback to scsi-hd

2019-06-17 Thread Sam Eiderman
We will need to add LCHS removal logic to scsi-hd's unrealize() in the next commit. Reviewed-by: Karl Heubaum Reviewed-by: Arbel Moshe Signed-off-by: Sam Eiderman --- hw/scsi/scsi-bus.c | 15 +++ include/hw/scsi/scsi.h | 1 + 2 files changed, 16 insertions(+) diff --git a/hw/

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 15:20 hat Roman Kagan geschrieben: > On Mon, Jun 17, 2019 at 02:53:55PM +0200, Kevin Wolf wrote: > > Am 17.06.2019 um 14:18 hat Roman Kagan geschrieben: > > > On Mon, Jun 17, 2019 at 01:15:04PM +0200, Kevin Wolf wrote: > > > > Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschriebe

Re: [Qemu-block] [PATCH v5 12/12] qemu-iotests/087: checks for io_uring

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:19 +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta > --- > tests/qemu-iotests/087 | 26 ++ > tests/qemu-iotests/087.out | 10 ++ > 2 files changed, 36 insertions(+) > > diff --git a/tests/qemu-iotests/087 b/tests/qemu-iotest

Re: [Qemu-block] [PATCH v5 08/12] block/file-posix.c: extend to use io_uring

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:19 +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta > --- > block/file-posix.c | 85 +- > 1 file changed, 69 insertions(+), 16 deletions(-) > > diff --git a/block/file-posix.c b/block/file-posix.c > index d018429672..

Re: [Qemu-block] [PATCH v5 10/12] block/io_uring: adds userspace completion polling

2019-06-17 Thread Maxim Levitsky
On Tue, 2019-06-11 at 10:51 +0100, Stefan Hajnoczi wrote: > On Mon, Jun 10, 2019 at 07:19:03PM +0530, Aarushi Mehta wrote: > > +static bool qemu_luring_poll_cb(void *opaque) > > +{ > > +LuringState *s = opaque; > > +struct io_uring_cqe *cqes; > > + > > +if (io_uring_peek_cqe(&s->ring, &

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Roman Kagan
On Mon, Jun 17, 2019 at 02:53:55PM +0200, Kevin Wolf wrote: > Am 17.06.2019 um 14:18 hat Roman Kagan geschrieben: > > On Mon, Jun 17, 2019 at 01:15:04PM +0200, Kevin Wolf wrote: > > > Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschrieben: > > > > The Valgrind tool fails to manage its termination

Re: [Qemu-block] [PATCH 0/3] block: blk_co_pcache

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 15:09 hat Eric Blake geschrieben: > On 6/17/19 7:09 AM, Kevin Wolf wrote: > > >>> > >>> Hmm, don't you think that blk_co_pcache sends NBD_CMD_CACHE if called on > >>> nbd driver? > >>> I didn't implement it. But may be I should.. > >>> > >>> May aim was only to avoid extra alloca

Re: [Qemu-block] [PATCH 0/3] block: blk_co_pcache

2019-06-17 Thread Eric Blake
On 6/17/19 7:09 AM, Kevin Wolf wrote: >>> >>> Hmm, don't you think that blk_co_pcache sends NBD_CMD_CACHE if called on >>> nbd driver? >>> I didn't implement it. But may be I should.. >>> >>> May aim was only to avoid extra allocation and unnecessary reads. But if we >>> implement >>> full-featu

Re: [Qemu-block] [PATCH v5 07/12] blockdev: accept io_uring as option

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:19 +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta > Reviewed-by: Stefan Hajnoczi > --- > blockdev.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/blockdev.c b/blockdev.c > index 3f44b891eb..a2a5b32604 100644 > --- a/blockdev.c >

Re: [Qemu-block] [PATCH v5 06/12] util/async: add aio interfaces for io_uring

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:18 +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta > Reviewed-by: Stefan Hajnoczi > --- > util/async.c | 36 > 1 file changed, 36 insertions(+) > > diff --git a/util/async.c b/util/async.c > index c10642a385..2709f0edc3 10

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 14:18 hat Roman Kagan geschrieben: > On Mon, Jun 17, 2019 at 01:15:04PM +0200, Kevin Wolf wrote: > > Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschrieben: > > > The Valgrind tool fails to manage its termination when QEMU raises the > > > signal SIGKILL. Lets exclude such test c

Re: [Qemu-block] [PATCH v2 6/7] iotests: amend QEMU NBD process synchronization

2019-06-17 Thread Roman Kagan
On Thu, Jun 13, 2019 at 12:59:53PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 11.06.2019 21:02, Andrey Shinkevich wrote: > > Processes are dying harder under the Valgring. It results in counting > > the dying process as a newborn one. Make it sure that old NBD job get > > finished before starting

Re: [Qemu-block] [PATCH v5 05/12] stubs: add stubs for io_uring interface

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:18 +0530, Aarushi Mehta wrote: > Signed-off-by: Aarushi Mehta > Reviewed-by: Stefan Hajnoczi > --- > MAINTAINERS | 1 + > stubs/Makefile.objs | 1 + > stubs/io_uring.c| 32 > 3 files changed, 34 insertions(+) > create mode

Re: [Qemu-block] [PATCH v2 6/7] iotests: amend QEMU NBD process synchronization

2019-06-17 Thread Roman Kagan
On Tue, Jun 11, 2019 at 09:02:10PM +0300, Andrey Shinkevich wrote: > Processes are dying harder under the Valgring. It results in counting > the dying process as a newborn one. Make it sure that old NBD job get > finished before starting a new one. I think this log message is confusing. The probl

Re: [Qemu-block] [PATCH 0/3] block: blk_co_pcache

2019-06-17 Thread Vladimir Sementsov-Ogievskiy
17.06.2019 15:09, Kevin Wolf wrote: > Am 17.06.2019 um 13:20 hat Vladimir Sementsov-Ogievskiy geschrieben: >> 06.06.2019 17:07, Vladimir Sementsov-Ogievskiy wrote: >>> 06.06.2019 16:55, Eric Blake wrote: On 6/6/19 8:48 AM, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > Here is s

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Roman Kagan
On Mon, Jun 17, 2019 at 01:15:04PM +0200, Kevin Wolf wrote: > Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschrieben: > > The Valgrind tool fails to manage its termination when QEMU raises the > > signal SIGKILL. Lets exclude such test cases from running under the > > Valgrind because there is no

Re: [Qemu-block] [PATCH] block/null: Expose read-zeroes option in QAPI schema

2019-06-17 Thread Max Reitz
On 17.06.19 13:57, Kevin Wolf wrote: > Commit cd219eb1e55 added the read-zeroes option for the null-co and > null-aio block driver, but forgot to add them to the QAPI schema. > Therefore, this option wasn't available in -blockdev and blockdev-add > until now. > > Add the missing option in the sche

Re: [Qemu-block] [PATCH 0/3] block: blk_co_pcache

2019-06-17 Thread Kevin Wolf
Am 17.06.2019 um 13:20 hat Vladimir Sementsov-Ogievskiy geschrieben: > 06.06.2019 17:07, Vladimir Sementsov-Ogievskiy wrote: > > 06.06.2019 16:55, Eric Blake wrote: > >> On 6/6/19 8:48 AM, Vladimir Sementsov-Ogievskiy wrote: > >>> Hi all! > >>> > >>> Here is small new io API: blk_co_pcache, which d

Re: [Qemu-block] [PATCH v5 04/12] block/io_uring: implements interfaces for io_uring

2019-06-17 Thread Maxim Levitsky
On Mon, 2019-06-10 at 19:18 +0530, Aarushi Mehta wrote: > Aborts when sqe fails to be set as sqes cannot be returned to the ring. > > Signed-off-by: Aarushi Mehta > --- > MAINTAINERS | 7 + > block/Makefile.objs | 3 + > block/io_uring.c| 314 +

Re: [Qemu-block] [PATCH] nvme: do not advertise support for unsupported arbitration mechanism

2019-06-17 Thread Max Reitz
On 17.06.19 08:54, Klaus Birkelund wrote: > On Fri, Jun 14, 2019 at 10:39:27PM +0200, Max Reitz wrote: >> On 06.06.19 11:25, Klaus Birkelund Jensen wrote: >>> The device mistakenly reports that the Weighted Round Robin with Urgent >>> Priority Class arbitration mechanism is supported. >>> >>> It is

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Roman Kagan
On Thu, Jun 13, 2019 at 12:47:21PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 11.06.2019 21:02, Andrey Shinkevich wrote: > > The Valgrind tool fails to manage its termination when QEMU raises the > > signal SIGKILL. Lets exclude such test cases from running under the > > Valgrind because there is

Re: [Qemu-block] [PATCH v2 7/7] iotests: new file to suppress Valgrind errors

2019-06-17 Thread Kevin Wolf
Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschrieben: > The Valgrind tool reports about an uninitialised memory usage when the > initialization is actually not needed. For example, the buffer 'buf' > instantiated on a stack of the function guess_disk_lchs(). I would be careful with calling ini

[Qemu-block] [PATCH] block/null: Expose read-zeroes option in QAPI schema

2019-06-17 Thread Kevin Wolf
Commit cd219eb1e55 added the read-zeroes option for the null-co and null-aio block driver, but forgot to add them to the QAPI schema. Therefore, this option wasn't available in -blockdev and blockdev-add until now. Add the missing option in the schema to make it available there, too. Signed-off-b

Re: [Qemu-block] [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action

2019-06-17 Thread Vladimir Sementsov-Ogievskiy
08.06.2019 1:26, John Snow wrote: > > > On 6/3/19 8:00 AM, Vladimir Sementsov-Ogievskiy wrote: >> Hi all! >> >> Here is block-dirty-bitmap-remove transaction action. >> >> It is used to do transactional movement of the bitmap (which is >> possible in conjunction with merge command). Transactional

Re: [Qemu-block] [PATCH v2 3/7] iotests: Valgrind fails to work with nonexistent directory

2019-06-17 Thread Kevin Wolf
Am 13.06.2019 um 11:52 hat Vladimir Sementsov-Ogievskiy geschrieben: > 11.06.2019 21:02, Andrey Shinkevich wrote: > > The Valgrind uses the exported variable TMPDIR and fails if the > > directory does not exist. Let us exclude such a test case from > > being run under the Valgrind. > > > > Signed-

Re: [Qemu-block] [PATCH 0/3] block: blk_co_pcache

2019-06-17 Thread Vladimir Sementsov-Ogievskiy
06.06.2019 17:07, Vladimir Sementsov-Ogievskiy wrote: > 06.06.2019 16:55, Eric Blake wrote: >> On 6/6/19 8:48 AM, Vladimir Sementsov-Ogievskiy wrote: >>> Hi all! >>> >>> Here is small new io API: blk_co_pcache, which does copy-on-read without >>> extra buffer for read data. This means that only par

Re: [Qemu-block] [PATCH v2 2/7] iotests: exclude killed processes from running under Valgrind

2019-06-17 Thread Kevin Wolf
Am 11.06.2019 um 20:02 hat Andrey Shinkevich geschrieben: > The Valgrind tool fails to manage its termination when QEMU raises the > signal SIGKILL. Lets exclude such test cases from running under the > Valgrind because there is no sense to check memory issues that way. > > Signed-off-by: Andrey S

Re: [Qemu-block] [PATCH v8 4/7] block: introduce backup-top filter driver

2019-06-17 Thread Vladimir Sementsov-Ogievskiy
14.06.2019 23:03, Max Reitz wrote: > On 14.06.19 18:22, Vladimir Sementsov-Ogievskiy wrote: >> 14.06.2019 15:57, Max Reitz wrote: >>> On 14.06.19 11:04, Vladimir Sementsov-Ogievskiy wrote: 13.06.2019 18:57, Max Reitz wrote: > On 29.05.19 17:46, Vladimir Sementsov-Ogievskiy wrote: >> Ba

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Sam Eiderman
Ok, I’ll resubmit this patch series in v3, as well as v2 for SeaBIOS soon enough. * Change “bootdevices” to “bios-geometry”, and remove the struct size * Add cpu_to_le32 fix as Laszlo suggested or big endian hosts * Fix last qtest commit - automatic docker tester for some reason does not have qe

Re: [Qemu-block] [Qemu-devel] [PATCH v3 00/15] monitor: Split monitor.c in core/HMP/QMP/misc

2019-06-17 Thread Kevin Wolf
Am 15.06.2019 um 22:31 hat Markus Armbruster geschrieben: > Kevin Wolf writes: > > > Am 14.06.2019 um 11:06 hat Markus Armbruster geschrieben: > >> Kevin Wolf writes: > >> > >> > monitor.c mixes a lot of different things in a single file: The core > >> > monitor infrastructure, HMP infrastrctur

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Gerd Hoffmann
Hi, > Keep it extendible for a low price of ABI + “bootdevices” name. > Or go strict and rename to “bios-geometries”? The name should reflect what is in there, so "bios-geometries" looks better to me. I'd also keep it strict, unless we have at least a vague idea what might be a useful future e

[Qemu-block] [RFC] nvme: how to support multiple namespaces

2019-06-17 Thread Klaus Birkelund
Hi all, I'm thinking about how to support multiple namespaces in the NVMe device. My first idea was to add a "namespaces" property array to the device that references blockdevs, but as Laszlo writes below, this might not be the best idea. It also makes it troublesome to add per-namespace parameter

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 0/8] Add Qemu to SeaBIOS LCHS interface

2019-06-17 Thread Sam Eiderman
> On 17 Jun 2019, at 9:50, Gerd Hoffmann wrote: > > Hi, > >>> Ok, given that seabios has no setup any manual configuration needs to be >>> done via qemu. >>> >>> But why do we need a new interface for that? IDE can pass the geometry >>> to the guest. virtio-blk has support too (VIRTIO_BLK

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Sam Eiderman
> On 17 Jun 2019, at 10:20, Gerd Hoffmann wrote: > > Hi, > >> We serialize this information in a similar way to the "bootorder" >> interface. >> The fw_cfg entry is "bootdevices" and it serializes a struct. > > Why "bootdevices"? I'd suggest to use "geometry" or "lchs" instead. True, if w

Re: [Qemu-block] [Qemu-devel] [QEMU] [PATCH v2 7/8] bootdevice: FW_CFG interface for LCHS values

2019-06-17 Thread Gerd Hoffmann
Hi, > We serialize this information in a similar way to the "bootorder" > interface. > The fw_cfg entry is "bootdevices" and it serializes a struct. Why "bootdevices"? I'd suggest to use "geometry" or "lchs" instead. > At the moment the struct holds the values of logical CHS values but it > c