From: Daniel P. Berrangé
Modify load_snapshot/save_snapshot to accept the device list and vmstate
node name parameters previously added to the block layer.
Reviewed-by: Eric Blake
Signed-off-by: Daniel P. Berrangé
Message-Id: <20210204124834.774401-9-berra...@redhat.com>
Signed-off-by: Dr. Dav
From: Andrey Gruzdev
Add new capability to 'qapi/migration.json' schema.
Update migrate_caps_check() to validate enabled capability set
against introduced one. Perform checks for required kernel features
and compatibility with guest memory backends.
Signed-off-by: Andrey Gruzdev
Reviewed-by: Pe
From: Andrey Gruzdev
In this particular implementation the same single migration
thread is responsible for both normal linear dirty page
migration and procesing UFFD page fault events.
Processing write faults includes reading UFFD file descriptor,
finding respective RAM block and saving faulting
From: Jinhao Gao
When VM migrate VMState of configuration, the fields(name and capabilities)
of configuration having a flag of VMS_ALLOC need to allocate memory. If the
src doesn't free memory of capabilities in SaveState after save VMState of
configuration, or the dst doesn't free memory of name
Postcopy may also be advised for dirty-bitmap migration only, in which
case the remote page size will not be available and we'll instead read
bogus data, blocking migration with a mismatch error if the VM uses
hugepages.
Fixes: 58110f0acb ("migration: split common postcopy out of ram postcopy")
Si
From: Andrey Gruzdev
Glue code to the userfaultfd kernel implementation.
Querying feature support, createing file descriptor, feature control,
memory region registration, IOCTLs on registered registered regions.
Signed-off-by: Andrey Gruzdev
Reviewed-by: Peter Xu
Message-Id: <20210129101407.10
From: Markus Armbruster
cache_init() attempts to handle allocation failure. The two error
messages are garbage, as untested error messages commonly are:
Parameter 'cache size' expects Failed to allocate cache
Parameter 'cache size' expects Failed to allocate page cache
Fix them to just
On 2/4/21 10:04 AM, Philippe Mathieu-Daudé wrote:
>>> Isn't it kind of weird that this would only affect an s390 host? I
>>> don't understand why the host would make a difference if we're doing
>>> TCG.
>>
>> I assume an existing BUG in the s390x TCG backend ... which makes it
>> harder to debug
From: Andrey Gruzdev
Introducing implementation of 'background' snapshot thread
which in overall follows the logic of precopy migration
while internally utilizes completely different mechanism
to 'freeze' vmstate at the start of snapshot creation.
This mechanism is based on userfault_fd with wr-
From: Markus Armbruster
73af8dd8d7 "migration: Make xbzrle_cache_size a migration
parameter" (v2.11.0) made the new parameter unsigned (QAPI type
'size', uint64_t in C). It neglected to update existing code, which
continues to use int64_t.
migrate_xbzrle_cache_size() returns the new parameter.
From: Markus Armbruster
migrate_params_check() has a number of error messages of the form
Parameter 'NAME' expects is invalid, it should be ...
Fix them to something like
Parameter 'NAME' expects a ...
Signed-off-by: Markus Armbruster
Reviewed-by: Dr. David Alan Gilbert
Message-Id:
From: Markus Armbruster
Commit 741d4086c8 "migration: Use proper types in json" (v2.12.0)
switched MigrationParameters to narrower integer types, and removed
the simplified qmp_migrate_set_parameters()'s argument checking
accordingly.
Good idea, except qmp_migrate_set_parameters() takes
MigrateS
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
> * Andrey Gruzdev (andrey.gruz...@virtuozzo.com) wrote:
> > This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
> > implemented in his series '[PATCH v0 0/4] migration: add background
> > snapshot'.
> >
> > Currently t
From: "Dr. David Alan Gilbert"
Modify query-migrate so that it has a flag indicating if outbound
migration is blocked, and if it is a list of reasons.
Signed-off-by: Dr. David Alan Gilbert
Message-Id: <20210202135522.127380-2-dgilb...@redhat.com>
Reviewed-by: Eric Blake
Reviewed-by: Peter Xu
From: Daniel P. Berrangé
None of the callers care about the errno value since there is a full
Error object populated. This gives consistency with save_snapshot()
which already just returns a boolean value.
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Daniel P. Berrangé
[PMD: Return false
Hi,
On Thu, Feb 4, 2021 at 3:38 AM dje--- via wrote:
>
> This commit is intended to only contain the slirp submodule change
> that adds ipv6 hostfwd support.
> ---
> slirp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
It's generally recommended to include the shortlog of some sort i
* Stefan Reiter (s.rei...@proxmox.com) wrote:
> Postcopy may also be advised for dirty-bitmap migration only, in which
> case the remote page size will not be available and we'll instead read
> bogus data, blocking migration with a mismatch error if the VM uses
> hugepages.
>
> Fixes: 58110f0acb (
According to the "ELF-64 Object File Format" specification:
"The first word in the entry, namesz, identifies the length, in
bytes, of a name identifying the entry’s owner or originator. The name field
contains a null-terminated string, with padding as necessary to ensure 8-
byte alignment for t
From: Daniel P. Berrangé
When running snapshot operations, there are various rules for which
blockdevs are included/excluded. While this provides reasonable default
behaviour, there are scenarios that are not well handled by the default
logic. Some of the conditions do not have a single correct a
From: Daniel P. Berrangé
The traditional HMP "savevm" command will overwrite an existing snapshot
if it already exists with the requested name. This new flag allows this
to be controlled allowing for safer behaviour with a future QMP command.
Reviewed-by: Eric Blake
Signed-off-by: Daniel P. Ber
From: Daniel P. Berrangé
The bdrv_all_*_snapshot functions return a BlockDriverState pointer
for the invalid backend, which the callers then use to report an
error message. In some cases multiple callers are reporting the
same error message, but with slightly different text. In the future
there w
From: Daniel P. Berrangé
When using the _launch_qemu and _send_qemu_cmd functions from
common.qemu, any QMP events get mixed in with the output from
the commands and responses.
This makes it difficult to write a test case as the ordering
of events in the output is not stable.
This introduces a
From: Daniel P. Berrangé
Currently the vmstate will be stored in the first block device that
supports snapshots. Historically this would have usually been the
root device, but with UEFI it might be the variable store. There
needs to be a way to override the choice of block device to store
the sta
On Thu, 4 Feb 2021 15:02:06 +
Stefan Hajnoczi wrote:
> Both lo_open() and lo_create() have similar code to open a file. Extract
> a common lo_do_open() function from lo_open() that will be used by
> lo_create() in a later commit.
>
> Since lo_do_open() does not otherwise need fuse_req_t req
From: Daniel P. Berrangé
Currently bdrv_all_find_snapshot() will return 0 if it finds
a snapshot, -1 if an error occurs, or if it fails to find a
snapshot. New callers to be added want to distinguish between
the error scenario and failing to find a snapshot.
Rename it to bdrv_all_has_snapshot an
From: Daniel P. Berrangé
Make snapshot deletion consistent with the snapshot save
and load commands by using a wrapper around the blockdev
layer. The main difference is that we get upfront validation
of the passed in device list (if any).
Reviewed-by: Eric Blake
Signed-off-by: Daniel P. Berrang
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/colo.c | 3 +--
migration/savevm.c | 4 ++--
migration/savevm.h | 2 +-
3 files changed, 4 insertions(
From: Daniel P. Berrangé
common.rc assumes it is being sourced from the same directory and
so also tries to source common.config from the current working
directory. With the ability to now have named tests in the tests/
subdir we need to check two locations for common.config.
Reviewed-by: Vladim
Hi,
Based on commit 1ed9228f63e (ericb/tags/pull-nbd-2021-02-02-v2)
I got:
TEST iotest-qcow2: 030 [fail]
--- /builds/philmd/qemu/tests/qemu-iotests/030.out
+++ 030.out.bad
@@ -1,5 +1,47 @@
-...
+WARNING:qemu.machine:qemu received signal 11; command:
"/builds/philmd/qem
From: Daniel P. Berrangé
savevm, loadvm and delvm are some of the few HMP commands that have never
been converted to use QMP. The reasons for the lack of conversion are
that they blocked execution of the event thread, and the semantics
around choice of disks were ill-defined.
Despite this downsi
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/migrati
On Thu, Feb 04, 2021 at 05:04:22PM +0100, Philippe Mathieu-Daudé wrote:
> On 2/4/21 10:37 AM, David Hildenbrand wrote:
> > On 04.02.21 10:29, Richard W.M. Jones wrote:
> commit 8f17a975e60b773d7c366a81c0d9bbe304f30859
> Author: Richard Henderson
> Date: Mon Mar 30 19:52:02 2020 -0
From: Phillip Tennen
Although we already have CONFIG_BSD, I added this flag to be sure that we could
rely on various macOS-specific subsystems, such as vmnet.framework.
Signed-off-by: Phillip Tennen
---
configure | 4
1 file changed, 4 insertions(+)
diff --git a/configure b/configure
in
On 04.02.21 17:41, Thomas Huth wrote:
> According to the "ELF-64 Object File Format" specification:
>
> "The first word in the entry, namesz, identifies the length, in
> bytes, of a name identifying the entry’s owner or originator. The name field
> contains a null-terminated string, with padding
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/postcopy-ram.c | 8 ++--
migration/postcopy-ram.h | 2 +-
migration/ram.c | 6 +++---
migra
From: Phillip Tennen
This patch implements a new netdev device, reachable via -netdev
vmnet-macos, that’s backed by macOS’s vmnet framework.
The vmnet framework provides native bridging support, and its usage in
this patch is intended as a replacement for attempts to use a tap device
via the tun
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/migration/savev
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/colo.c | 3 +-
migration/savevm.c | 73 +++---
migration/save
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 26 --
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
This is particularly useful for loading snapshots as this is a likely
error scenario to hit when the source and dest VM configs do not
match. This is illu
On 2/4/21 10:29 AM, David Hildenbrand wrote:
>> +++ b/tcg/s390/tcg-target.c.inc
>> @@ -1094,10 +1094,16 @@ static int tgen_cmp(TCGContext *s, TCGType type,
>> TCGCond c, TCGReg r1,
>> op = (is_unsigned ? RIL_CLFI : RIL_CFI);
>> tcg_out_insn_RIL(s, op, r1, c2);
>
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
include/migration/colo.h | 2 +-
migration/migration.c| 6 +++---
migration/savevm.c | 25 +++-
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 87 ++
1 file changed, 64 insertions(+), 23 delet
Patchew URL: https://patchew.org/QEMU/20210204170951.91805-1-and...@daynix.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210204170951.91805-1-and...@daynix.com
Subject: [RFC PATCH v4 0/7] eBPF RSS support for vi
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/migration/save
On Thu, 4 Feb 2021 15:02:08 +
Stefan Hajnoczi wrote:
> A well-behaved FUSE client does not attempt to open special files with
> FUSE_OPEN because they are handled on the client side (e.g. device nodes
> are handled by client-side device drivers).
>
> The check to prevent virtiofsd from open
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff --git a/m
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 8 +++-
migration/savevm.c| 47 ++-
migra
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 4 ++--
migration/savevm.c| 36
migration/savevm
Due to its long term heritage most of the migration code just invokes
'error_report' when problems hit. This was fine for HMP, since the
messages get redirected from stderr, into the HMP console. It is not
OK for QMP because the errors will not be fed back to the QMP client.
This wasn't a terrible
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/migration/s
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/colo.c | 4 +++-
migration/savevm.c | 8
migration/savevm.h | 2 +-
3 files changed, 8 insert
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/migration/savevm.c b
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 31 +--
1 file changed, 17 insertions(+), 14 deletions(-)
diff -
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/ram.c| 11 ++-
migration/ram.h| 2 +-
migration/savevm.c | 8 +++-
3 files changed
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 14 +++---
migration/savevm.c| 18 +++---
migration/savevm.h|
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 43 +--
1 file changed, 21 insertions(+), 22 deletion
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
include/migration/global_state.h | 2 +-
migration/global_state.c | 6 +++---
migration/migration.c
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/migrati
This method cannot fail since it merely allocates a single struct, so
the only possible failure (ENOMEM) will cause an abort() already.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/migration/savevm.c b/migrat
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
diff -
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
In doing this the callers now actually honour the failures that can
be reported instead of carrying on as if everything was normal.
Signed-off-by: Daniel
From: Phillip Tennen
This patch series implements a new netdev device, reachable via -netdev
vmnet-macos, that’s backed by macOS’s vmnet framework.
The vmnet framework provides native bridging support, and its usage in
this patch is intended as a replacement for attempts to use a tap device
via
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --git a/mi
Re-arrange code to remove need for a separate 'ret2' variable, accepting
the duplicated qemu_fclose() call as resulting in clearer code to follow
the flow of.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 4 +++-
migration/savevm.c| 9 +
migration/savevm.h| 3 ++-
3 files change
On 04.02.2021 18:01, Dr. David Alan Gilbert wrote:
* Andrey Gruzdev (andrey.gruz...@virtuozzo.com) wrote:
This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
implemented in his series '[PATCH v0 0/4] migration: add background snapshot'.
Currently the only way to make (ex
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 9 -
migration/savevm.c| 5 +++--
migration/savevm.h| 2 +-
3 files change
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/migration.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/migration/m
Public bug reported:
== Reproducer (build with --enable-sanitizers) ==
cat << EOF | ./qemu-system-i386 -machine q35 -nodefaults \
-device megasas -device scsi-cd,drive=null0 \
-blockdev driver=null-co,read-zeroes=on,node-name=null0 \
-nographic -qtest stdio
outl 0xcf8 0x8818
outl 0xcfc 0xc000
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/savevm.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a
This is an incremental step in converting vmstate loading code to report
via Error objects instead of printing directly to the console/monitor.
Signed-off-by: Daniel P. Berrangé
---
migration/colo.c | 2 +-
migration/savevm.c | 51 --
migration/save
On 2/4/21 6:29 AM, David Hildenbrand wrote:
> On 04.02.21 17:04, Philippe Mathieu-Daudé wrote:
>> On 2/4/21 10:37 AM, David Hildenbrand wrote:
>>> On 04.02.21 10:29, Richard W.M. Jones wrote:
>> commit 8f17a975e60b773d7c366a81c0d9bbe304f30859
>> Author: Richard Henderson
>> Date: Mon
On 2/4/21 3:40 PM, Paolo Bonzini wrote:
> On 04/02/21 15:22, Wainer dos Santos Moschetta wrote:
-F: docs/interop/virtfs-proxy-helper.rst
+F: docs/tools/virtfs-proxy-helper.rst
>>>
>>> Unrelated, but Paolo once said helpers are not tools.
>
> I think helpers is not a good word. However,
On 04.02.2021 19:53, Dr. David Alan Gilbert wrote:
* Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
* Andrey Gruzdev (andrey.gruz...@virtuozzo.com) wrote:
This patch series is a kind of 'rethinking' of Denis Plotnikov's ideas he's
implemented in his series '[PATCH v0 0/4] migration: add ba
On Thu, 4 Feb 2021 at 15:43, Stefan Hajnoczi wrote:
>
> The following changes since commit db754f8ccaf2f073c9aed46a4389e9c0c2080399:
>
> Merge remote-tracking branch 'remotes/rth-gitlab/tags/pull-tcg-20210202'
> into staging (2021-02-03 19:35:57 +)
>
> are available in the Git repository at
On Thu, Feb 04, 2021 at 07:36:19AM -1000, Richard Henderson wrote:
> On 2/4/21 12:00 AM, Daniel P. Berrangé wrote:
> >>> Hmm. Is there any way to get the full output of the container build? At
> >>> present it's being truncated:
> >>>
> >>> #7 [4/5] RUN yum install -y bzip2 bzip2-devel cc
On 2/4/21 12:00 AM, Daniel P. Berrangé wrote:
>>> Hmm. Is there any way to get the full output of the container build? At
>>> present it's being truncated:
>>>
>>> #7 [4/5] RUN yum install -y bzip2 bzip2-devel ccache
>>> csnappy-de...
>>>
>>>
>>> In particular, I'm trying to add a ne
* no-re...@patchew.org (no-re...@patchew.org) wrote:
> Patchew URL:
> https://patchew.org/QEMU/20210204150208.367837-1-stefa...@redhat.com/
>
>
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Type: series
> Message-id: 20210204150
On 04/02/21 18:37, Philippe Mathieu-Daudé wrote:
- elf2dmp and rdmacm-mux should be in tools/, probably it's in contrib/
because nobody uses it and there's no tests so it might bitrot.
Why keep something nobody uses?
Well, not really nobody but no maintainer.
Paolo
On 2/4/21 5:01 AM, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> The use in tcg_tb_lookup is given a random pc that comes from the pc
>> of a signal handler. Do not assert that the pointer is already within
>> the code gen buffer at all, much less the writable mirror of it.
>
> Surely
On 2/4/21 4:06 PM, Daniel P. Berrangé wrote:
> On Thu, Feb 04, 2021 at 04:02:01PM +0100, Paolo Bonzini wrote:
>> On 04/02/21 15:50, Peter Maydell wrote:
>>> On Thu, 4 Feb 2021 at 14:47, Daniel P. Berrangé wrote:
The distinction of contrib/ vs tools/ is supposed to be more a
reflection on
On 04/02/21 18:42, Philippe Mathieu-Daudé wrote:
On 2/4/21 3:40 PM, Paolo Bonzini wrote:
On 04/02/21 15:22, Wainer dos Santos Moschetta wrote:
-F: docs/interop/virtfs-proxy-helper.rst
+F: docs/tools/virtfs-proxy-helper.rst
Unrelated, but Paolo once said helpers are not tools.
I think helper
On Thu, 4 Feb 2021 at 17:48, Philippe Mathieu-Daudé wrote:
>
> Hi,
>
> Based on commit 1ed9228f63e (ericb/tags/pull-nbd-2021-02-02-v2)
> I got:
>
> TEST iotest-qcow2: 030 [fail]
Yes; see also this thread:
https://lore.kernel.org/qemu-devel/9e71568c-ce4a-f844-fbd3-a4a59f850...@redhat.com/
Can
On 2/4/21 5:39 AM, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> Only allow registers or constants, but not both, in any
>> given position.
>
> Aren't we switching to all registers (there are no more _i functions
> after this)? I guess you mean the registers can have constants in them?
On 04/02/21 16:42, Peter Maydell wrote:
On Thu, 4 Feb 2021 at 15:39, Programmingkid wrote:
On Feb 4, 2021, at 3:54 AM, Paolo Bonzini wrote:
On 02/02/21 14:44, John Arbuckle wrote:
Before switching the build system over to Meson, an icon was
added to the QEMU binary on Mac OS. This patch
On 2/4/21 4:54 AM, Alex Bennée wrote:
>
> Richard Henderson writes:
>
>> Signed-off-by: Richard Henderson
>> ---
>> tcg/tci/tcg-target.c.inc | 70
>> ++--
>
> Hmm duplicate patch tripped up my mail tools, did send-email have a
> brain fart at 79/93?
>
Send
"exec/cpu-defs.h" contains common CPU definitions for
accelerators, which is not related to the TCG backends.
See tcg/README description:
4) Backend
tcg-target.h contains the target specific definitions. tcg-target.c.inc
contains the target specific code; it is #included by tcg/tcg.c, rathe
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> v4:
> * Patch 1: Return positive errno if openat(2) fails in lo_do_open() [Greg]
> * Patch 3: Return -fd instead or -errno after lo_inode_open() in
> lo_do_open() [Greg]
> * Patch 3: Use De Morgan's Law to simplify the boolean expression in
> lo
On 2/4/21 8:22 AM, Wainer dos Santos Moschetta wrote:
> Unrelated too, but allow me to ask:
>
> Should we move the tools (qemu-img, qemu-io, qemu-nbd...etc) to the
> tools directory (virtiofsd seems to feel alone there)?
No complaint by me for qemu-nbd (I had floated the idea before the meson
co
On 04/02/21 19:03, Philippe Mathieu-Daudé wrote:
"exec/cpu-defs.h" contains common CPU definitions for
accelerators, which is not related to the TCG backends.
See tcg/README description:
Most of the definitions are actually for TCG, not for all accelerators
(the TLB mostly).
However, they're
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> Due to its long term heritage most of the migration code just invokes
> 'error_report' when problems hit. This was fine for HMP, since the
> messages get redirected from stderr, into the HMP console. It is not
> OK for QMP because the errors will
The code is currently comparing c2 to the type promotion of
uint32_t and int32_t. That is, the conversion rules are as:
(common_type) c2 == (common_type) (uint32_t)
(is_unsigned
? (uint32_t)c2
: (uint32_t)(int32_t)c2)
In th
On Thu, Feb 4, 2021 at 2:03 AM Daniel P. Berrangé
wrote:
> On Wed, Feb 03, 2021 at 03:35:36PM -0800, dje--- via wrote:
> > Add support for ipv6 host forwarding
> >
> > This patchset takes the original patch from Maxim,
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg569573.html
> > and
On Jan 24 11:54, Minwoo Im wrote:
>
> Minwoo Im (6):
> hw/block/nvme: introduce nvme-subsys device
> hw/block/nvme: support to map controller to a subsystem
> hw/block/nvme: add CMIC enum value for Identify Controller
> hw/block/nvme: support for multi-controller in subsystem
> hw/block/
On Feb 4 19:31, Klaus Jensen wrote:
> On Jan 24 11:54, Minwoo Im wrote:
> >
> > Minwoo Im (6):
> > hw/block/nvme: introduce nvme-subsys device
> > hw/block/nvme: support to map controller to a subsystem
> > hw/block/nvme: add CMIC enum value for Identify Controller
> > hw/block/nvme: supp
On 2/4/21 7:37 AM, Daniel P. Berrangé wrote:
> On Thu, Feb 04, 2021 at 07:36:19AM -1000, Richard Henderson wrote:
>> On 2/4/21 12:00 AM, Daniel P. Berrangé wrote:
> Hmm. Is there any way to get the full output of the container build? At
> present it's being truncated:
>
> #7 [4/5]
From: Stefan Hajnoczi
lo_do_lookup() finds an existing inode or allocates a new one. It
increments nlookup so that the inode stays alive until the client
releases it.
Existing callers don't need the struct lo_inode so the function doesn't
return it. Extend the function to optionally return the i
s://gitlab.com/dagrh/qemu.git tags/pull-virtiofs-20210204
for you to fetch changes up to cf269ff8032392bbdd700e7bfd21823ad9eee3a9:
virtiofsd: Add restart_syscall to the seccomp whitelist (2021-02-04 17:50:08
+)
virtiofs: Secu
301 - 400 of 520 matches
Mail list logo
