qemu_rdma_poll()'s return type is uint64_t, even though it returns 0,
-1, or @ret, which is int. Its callers assign the return value to int
variables, then check whether it's negative. Unclean.
Return int instead.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 4 ++--
1 file
When a function returns 0 on success, negative value on error,
checking for non-zero suffices, but checking for negative is clearer.
So do that.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 82
1 file changed, 41 insertions(+), 41
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 35 ++-
1 file changed, 10 insertions(+), 25 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 85f6b274bf..62d95b7d2c 100644
--- a/migration/rdma.c
+++ b/migration/rdma.c
@@ -1514,7 +1514,7
When migration capability @rdma-pin-all is true, but the server cannot
honor it, qemu_rdma_connect() calls macro ERROR(), then returns
success.
ERROR() sets an error. Since qemu_rdma_connect() returns success, its
caller rdma_start_outgoing_migration() duly assumes @errp is still
clear. The
qemu_rdma_resolve_host() and qemu_rdma_dest_init() try addresses until
they find on that works. If none works, they return the first Error
set by qemu_rdma_broken_ipv6_kernel(), or else return a generic one.
qemu_rdma_broken_ipv6_kernel() neglects to set an Error when
ibv_open_device() fails.
Hiding return statements in macros is a bad idea. Use a function
instead, and open code the return part.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 43 +++
1 file changed, 27 insertions(+), 16 deletions(-)
diff --git a/migration/rdma.c
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
ERROR() has become "error_setg() unless an error has been set
already". Hiding the conditional in the macro is in the way of
further work. Replace the macro uses by their expansion, and delete
the macro.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 168
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
Oh dear, where to start. There's so much wrong, and in pretty obvious
ways. This code should never have passed review. I'm refraining from
saying more; see the commit messages instead.
Issues remaining after this series include:
* Terrible error messages
* Some error message cascades remain
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
@error_reported and @received_error are flags. The latter is even
assigned bool true. Change them from int to bool.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index
qemu_rdma_data_init() return type is void *. It actually returns
RDMAContext *, and all its callers assign the value to an
RDMAContext *. Unclean.
Return RDMAContext * instead.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
qemu_rdma_data_init() neglects to set an Error when it fails because
@host_port is null. Fortunately, no caller passes null, so this is
merely a latent bug. Drop the flawed code handling null argument.
Signed-off-by: Markus Armbruster
---
migration/rdma.c | 29 +
1
When qemu_rdma_wait_comp_channel() receives an event from the
completion channel, it reports an error "receive cm event while wait
comp channel,cm event is T", where T is the numeric event type.
However, the function fails only when T is a disconnect or device
removal. Events other than these two
Functions that use an Error **errp parameter to return errors should
not also report them to the user, because reporting is the caller's
job. When the caller does, the error is reported twice. When it
doesn't (because it recovered from the error), there is no error to
report, i.e. the report is
Peter Xu writes:
> On Fri, Sep 15, 2023 at 12:28:36PM -0400, Peter Xu wrote:
>> On Thu, Sep 14, 2023 at 10:56:23PM -0300, Fabiano Rosas wrote:
>> > Peter Xu writes:
>> >
>> > > On Thu, Sep 14, 2023 at 07:54:17PM -0300, Fabiano Rosas wrote:
>> > >> Fabiano Rosas writes:
>> > >>
>> > >> >
On Mon, Sep 18, 2023 at 7:31 PM Michael S. Tsirkin wrote:
>
> On Mon, Sep 18, 2023 at 07:24:48PM +0530, Ani Sinha wrote:
> > 32-bit systems do not have a reserved memory for hole64 but they may have a
> > reserved memory space for memory hotplug. Since, hole64 starts after the
> > reserved
On 9/12/23 12:34, Michael Tokarev wrote:
12.09.2023 12:45, Helge Deller:
/usr/bin/ld:
/usr/lib/gcc/x86_64-redhat-linux/13/../../../../lib64/libc.a(abort.o): in
function `abort':
(.text.unlikely+0x0): multiple definition of `abort';
On 9/18/23 15:57, Alexander Ivanov wrote:
On 9/15/23 20:41, Denis V. Lunev wrote:
* Discarding with backing stores is not supported by the format.
* There is no buffering/queueing of the discard operation.
* Only operations aligned to the cluster are supported.
Signed-off-by: Denis V. Lunev
On Mon, Sep 18, 2023 at 07:24:48PM +0530, Ani Sinha wrote:
> 32-bit systems do not have a reserved memory for hole64 but they may have a
> reserved memory space for memory hotplug. Since, hole64 starts after the
> reserved hotplug memory, the unaligned hole64 start address gives us the
> end
On 9/15/23 20:41, Denis V. Lunev wrote:
* Discarding with backing stores is not supported by the format.
* There is no buffering/queueing of the discard operation.
* Only operations aligned to the cluster are supported.
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 47
From: Marc-André Lureau
The Display Port has some strong PIXMAN dependency.
Signed-off-by: Marc-André Lureau
---
hw/arm/Kconfig | 3 ++-
hw/display/Kconfig | 5 +
hw/display/meson.build | 2 +-
3 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/hw/arm/Kconfig
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
meson.build| 6 +-
ui/meson.build | 4 ++--
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/meson.build b/meson.build
index e870b039cc..8106ab39ac 100644
--- a/meson.build
+++ b/meson.build
@@ -1545,7 +1545,11
From: Marc-André Lureau
If a display is backed by a specialized VC, allow to override the
default "vc:80Cx24C". For that, set the dpy.type just before creating
the default serial/parallel/monitor.
(the next patch makes it create a "null" backend by default if !PIXMAN)
Signed-off-by: Marc-André
32-bit systems do not have a reserved memory for hole64 but they may have a
reserved memory space for memory hotplug. Since, hole64 starts after the
reserved hotplug memory, the unaligned hole64 start address gives us the
end address for this memory hotplug region that the processor may use.
Fix
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
meson.build | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meson.build b/meson.build
index 74bdfa92b7..bcf7424440 100644
--- a/meson.build
+++ b/meson.build
@@ -832,9 +832,6 @@ if not get_option('pixman').auto() or have_system
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
configs/devices/mips64el-softmmu/default.mak | 2 +-
hw/display/Kconfig | 2 +-
hw/display/meson.build | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Marc-André Lureau
Drop the "x-pixman" property and use fallback path in such case.
Signed-off-by: Marc-André Lureau
---
hw/display/sm501.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/hw/display/sm501.c b/hw/display/sm501.c
index
From: Marc-André Lureau
Implement a fallback path for region 2D update.
Signed-off-by: Marc-André Lureau
---
ui/dbus-listener.c | 88 --
ui/meson.build | 2 +-
2 files changed, 62 insertions(+), 28 deletions(-)
diff --git a/ui/dbus-listener.c
From: Marc-André Lureau
Hi,
QEMU system emulators can be made to compile and work without Pixman.
Only a few devices and options actually require it (VNC, Gtk, Spice for ex) and
will have to be compiled out.
However, most of QEMU graphics-related code is based on pixman_image_t and
format. If
From: Marc-André Lureau
This is a tiny subset of PIXMAN API that is used pervasively in QEMU
codebase to manage images and identify the underlying format.
It doesn't seems worth to wrap this in a QEMU-specific API.
Signed-off-by: Marc-André Lureau
---
include/ui/pixman-compat.h | 190
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
meson.build| 6 +-
hw/display/Kconfig | 2 +-
ui/meson.build | 10 +-
3 files changed, 11 insertions(+), 7 deletions(-)
diff --git a/meson.build b/meson.build
index 8106ab39ac..1ef57ebda2 100644
---
From: Marc-André Lureau
Use a simpler implementation for rectangle geometry & intersect, drop
the need for (more complex) PIXMAN functions.
Signed-off-by: Marc-André Lureau
---
include/ui/rect.h | 55 +
hw/display/virtio-gpu.c | 30
From: Marc-André Lureau
The QEMU fallback covers the requirements. We still need the flags of
header inclusion with CONFIG_PIXMAN.
Signed-off-by: Marc-André Lureau
---
ui/meson.build | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ui/meson.build b/ui/meson.build
index
From: Marc-André Lureau
The command requires color conversion and line-by-line feeding. We could
have a simple fallback for simple formats though.
Signed-off-by: Marc-André Lureau
Reviewed-by: Philippe Mathieu-Daudé
---
qapi/ui.json | 3 ++-
ui/ui-hmp-cmds.c | 2 ++
ui/ui-qmp-cmds.c | 2
From: Marc-André Lureau
For now, pixman is mandatory, but we set config_host.h and Kconfig.
Once compilation is fixed, "pixman" will become actually optional.
Signed-off-by: Marc-André Lureau
---
meson.build | 10 --
include/ui/qemu-pixman.h | 2 ++
From: Marc-André Lureau
When we can't draw text, simply show a blank display.
Signed-off-by: Marc-André Lureau
---
ui/console.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ui/console.c b/ui/console.c
index 8b5c40ddd7..1c710a6d5e 100644
--- a/ui/console.c
+++ b/ui/console.c
@@ -584,6
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
meson.build | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 1ef57ebda2..74bdfa92b7 100644
--- a/meson.build
+++ b/meson.build
@@ -1516,7 +1516,11 @@ gtkx11 = not_found
vte =
From: Marc-André Lureau
This simply means that 2d drawing updates won't be handled, but 3d
should work.
Signed-off-by: Marc-André Lureau
---
hw/display/vhost-user-gpu.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/display/vhost-user-gpu.c b/hw/display/vhost-user-gpu.c
index
From: Marc-André Lureau
Add stubs for the fallback paths.
Signed-off-by: Marc-André Lureau
---
ui/console-vc-stubs.c | 32
ui/console.c | 4
ui/meson.build| 2 +-
3 files changed, 37 insertions(+), 1 deletion(-)
create mode 100644
From: Marc-André Lureau
Those functions require the PIXMAN library.
Signed-off-by: Marc-André Lureau
---
include/ui/qemu-pixman.h | 7 +--
ui/qemu-pixman.c | 6 ++
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/include/ui/qemu-pixman.h
On Fri, 15 Sept 2023 at 11:10, Alex Bennée wrote:
>
> The following changes since commit 005ad32358f12fe9313a4a01918a55e60d4f39e5:
>
> Merge tag 'pull-tpm-2023-09-12-3' of
> https://github.com/stefanberger/qemu-tpm into staging (2023-09-13 13:41:57
> -0400)
>
> are available in the Git
Hi,
> > I'm still seeing a CI failure:
> >
> > 3/61 qemu:qtest+qtest-x86_64 / qtest-x86_64/bios-tables-test ERROR
> > 19.18s killed by signal 6 SIGABRT
^^
> Hmm, that's rather unhelpful - we need to get iasl added to the build
> env by default.
That is a
"Nicholas Piggin" writes:
> On Mon Sep 18, 2023 at 5:59 PM AEST, Alex Bennée wrote:
>>
>> "Nicholas Piggin" writes:
>>
>> > On Sat Sep 16, 2023 at 1:29 PM AEST, Richard Henderson wrote:
>> >> From: Nicholas Piggin
>> >>
>> >> mttcg asserts that an execution ending with EXCP_HALTED must have
The edk2 update caused an address change:
DefinitionBlock ("", "SSDT", 1, "BOCHS ", "NVDIMM", 0x0001)
{
Scope (\_SB)
{
Device (NVDR)
{
Name (_HID, "ACPI0012" /* NVDIMM Root Device */) // _HID:
Hardware ID
[ ... ]
}
}
-
Signed-off-by: Gerd Hoffmann
---
tests/qtest/bios-tables-test-allowed-diff.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index e569098abddc..dfb8523c8bf4 100644
---
The following changes since commit c5ea91da443b458352c1b629b490ee6631775cb4:
Merge tag 'pull-trivial-patches' of https://gitlab.com/mjt0k/qemu into
staging (2023-09-08 10:06:25 -0400)
are available in the Git repository at:
https://gitlab.com/kraxel/qemu.git tags/firmware/edk2-20230918
New stable release was tagged in August 2023,
update the edk2 submodule to it.
Signed-off-by: Gerd Hoffmann
---
roms/edk2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roms/edk2 b/roms/edk2
index f80f052277c8..819cfc6b42a6 16
--- a/roms/edk2
+++ b/roms/edk2
@@ -1 +1 @@
Set PCD to workaround two fixes missing the release.
https://github.com/tianocore/edk2/commit/8b66f9df1bb0fd5ebb743944d41cb33178cf2fdd
https://github.com/tianocore/edk2/commit/020cc9e2e7053bb62247b0babbbe80cb855592e5
Signed-off-by: Gerd Hoffmann
---
roms/edk2-build.config | 6 ++
1 file
Signed-off-by: Gerd Hoffmann
---
tests/qtest/bios-tables-test-allowed-diff.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8bf4..e569098abddc 100644
---
risc-v switched to use split code/vars images like the other archs.
Signed-off-by: Gerd Hoffmann
---
roms/edk2-build.config | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/roms/edk2-build.config b/roms/edk2-build.config
index 66ef9ffcb91f..ffe0d12d0cb7 100644
---
Sync with latest version from gitlab.com/kraxel/edk2-build-config
Signed-off-by: Gerd Hoffmann
---
roms/edk2-build.py | 202 -
1 file changed, 128 insertions(+), 74 deletions(-)
diff --git a/roms/edk2-build.py b/roms/edk2-build.py
index
SPR's CFAR, DEC, HDEC, TB-L/U are not implemented as part of CPUPPCState.
Hence, gdbstub is not able to access them using (CPUPPCState *)env->spr[] array.
Update gdb_get_spr_reg() method to handle these SPR's specifically.
Signed-off-by: Saif Abrar
---
target/ppc/gdbstub.c | 40
-20230918
for you to fetch changes up to 44fa20c92811a9b88b41b4882a7e948c2fe6bd08:
spapr: Remove support for NVIDIA V100 GPU with NVLink2 (2023-09-18 07:25:28
-0300)
ppc patch queue for 2023-09-18:
In this short queue we're making
From: Cédric Le Goater
NVLink2 support was removed from the PPC PowerNV platform and VFIO in
Linux 5.13 with commits :
562d1e207d32 ("powerpc/powernv: remove the nvlink support")
b392a1989170 ("vfio/pci: remove vfio_pci_nvlink2")
This was 2.5 years ago. Do the same in QEMU with a revert of
Update all relevant PowerPC entries as follows:
- Nick Piggin is promoted to Maintainer in all qemu-ppc subsystems.
Nick has been a solid contributor for the last couple of years and
has the required knowledge and motivation to drive the boat.
- Greg Kurz is being removed from all qemu-ppc
From: Cédric Le Goater
As reported by Coverity, "idx << xive->pc_shift" is evaluated using
32-bit arithmetic, and then used in a context expecting a "uint64_t".
Add a uint64_t cast.
Fixes: Coverity CID 1519049
Fixes: b68147b7a5bf ("ppc/xive: Add support for the PC MMIOs")
Signed-off-by: Cédric
Hi Mark, Artyom,
I'm looking at the CPU_FEATURE_FLOAT128 definition introduced
in commit 64a88d5d3a ("CPU feature selection support"). Any
clue how it was supposed to be used?
Thanks,
Phil.
On 9/18/23 15:14, Denis V. Lunev wrote:
On 9/18/23 15:09, Alexander Ivanov wrote:
On 9/15/23 20:41, Denis V. Lunev wrote:
The access to the bitmap is not optimized completely.
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 51
---
On 9/15/23 20:41, Denis V. Lunev wrote:
Replace 'space' representing the amount of data to preallocate with
'bytes'.
Rationale:
* 'space' at each place is converted to bytes
* the unit is more close to the variable name
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 13 +
On 9/18/23 15:09, Alexander Ivanov wrote:
On 9/15/23 20:41, Denis V. Lunev wrote:
The access to the bitmap is not optimized completely.
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 51 ---
1 file changed, 39 insertions(+), 12
On 9/15/23 20:41, Denis V. Lunev wrote:
The access to the bitmap is not optimized completely.
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 51 ---
1 file changed, 39 insertions(+), 12 deletions(-)
diff --git a/block/parallels.c
On Mon, Sep 18, 2023 at 08:52:57AM -0400, Stefan Hajnoczi wrote:
> On Mon, 18 Sept 2023 at 06:00, Gerd Hoffmann wrote:
> >
> > > Hi Gerd,
> > > I think either this pull request or your edk2 pull request causes the
> > > following CI failure:
> > >
> > > >>>
On Mon, 18 Sept 2023 at 06:00, Gerd Hoffmann wrote:
>
> > Hi Gerd,
> > I think either this pull request or your edk2 pull request causes the
> > following CI failure:
> >
> > >>> G_TEST_DBUS_DAEMON=/builds/qemu-project/qemu/tests/dbus-vmstate-daemon.sh
> > >>>
On Mon, 19 Jun 2023 at 10:58, Jonathan Cameron via wrote:
>
> On Fri, 16 Jun 2023 14:10:24 -0400
> Gregory Price wrote:
> >
> > Last I tested cxl-2023-05-25 branch of Johnathan's fork is working on x86:
> >
> > https://gitlab.com/jic23/qemu/-/tree/cxl-2023-05-25
> >
> > I have not worked with
On 17.09.23 12:46, Maciej S. Szmigiero wrote:
On 8.09.2023 16:21, David Hildenbrand wrote:
We want to support memory devices that can automatically decide how many
memslots they will use. In the worst case, they have to use a single
memslot.
The target use cases are virtio-mem and the hyper-v
On Fri, 15 Sept 2023 at 18:13, Akihiko Odaki wrote:
>
> On 2023/09/16 2:01, Viktor Prutyanov wrote:
> > Windows Server 2022 and Windows 11 require more careful kernel PE image
> > search and handling of PDB than previous Windows versions.
> > Also, improve support of large ELF dump files, dumps
On Thu, 14 Sep 2023 15:54:54 +0300
Michael Tokarev wrote:
> 13.09.2023 18:05, Jonathan Cameron via wrote:
> > Indexing has to be done into an array with the right size elements.
> > As such, the size parameter always matches the array element size
> > and can be used in place of the longer
On Thu, 14 Sept 2023 at 12:33, Thomas Huth wrote:
>
> Hi Peter!
>
> Here are some patches that add basic support for s390x to RISU.
> It's still quite limited, e.g. no support for load/store memory
> operations yet, but the basics with simple 16-bit or 32-bit
> instructions work *now* already
On 9/18/23 13:51, Jason Gunthorpe wrote:
On Fri, Sep 15, 2023 at 02:42:48PM +0200, Cédric Le Goater wrote:
On 8/30/23 12:37, Zhenzhong Duan wrote:
Hi All,
As the kernel side iommufd cdev and hot reset feature have been queued,
also hwpt alloc has been added in Jason's for_next branch [1], I'd
On Wed, Sep 13, 2023 at 06:03:12PM -0700, Stephen Brennan wrote:
> Hello all,
>
> This is the second version of my patch series about the kdump format,
> you can see the first version here [1].
>
> The current output format for dump-guest-memory's kdump compressed
> format is actually the
On Wed, Sep 13, 2023 at 06:03:15PM -0700, Stephen Brennan wrote:
> This can be used from QMP command line as "-R" to mirror the
> corresponding flag for makedumpfile. This enables the kdump_reassembled
> flag introduced in the previous patch.
>
> Signed-off-by: Stephen Brennan
> ---
>
On 9/15/23 20:41, Denis V. Lunev wrote:
We should extend the bitmap ff the file is extended and set the bit in
Typo: ff -> if.
the image used bitmap once the cluster is allocated. Sanity check at
that moment also looks like a good idea.
Signed-off-by: Denis V. Lunev
---
On Fri, Sep 15, 2023 at 02:42:48PM +0200, Cédric Le Goater wrote:
> On 8/30/23 12:37, Zhenzhong Duan wrote:
> > Hi All,
> >
> > As the kernel side iommufd cdev and hot reset feature have been queued,
> > also hwpt alloc has been added in Jason's for_next branch [1], I'd like
> > to update a new
On 9/15/23 20:41, Denis V. Lunev wrote:
This would be useful in the next patch in allocate_clusters(). This
change would not imply serious performance drawbacks as usually image
is full of data or are at the end of the bitmap.
Signed-off-by: Denis V. Lunev
---
block/parallels.c | 18
On 9/15/23 20:41, Denis V. Lunev wrote:
The test is quite similar with the original one for duplicated clusters.
There is the only difference in the operation which should fix the
image.
Signed-off-by: Denis V. Lunev
---
tests/qemu-iotests/tests/parallels-checks | 36 +++
On 9/15/23 20:41, Denis V. Lunev wrote:
Original check is broken as supposed reading from 2 different clusters
results in read from the same file offset twice. This is definitely
wrong.
We should be sure that
* the content of both clusters is correct after repair
* clusters are at the different
On 18/09/23, Philippe Mathieu-Daudé wrote:
> Hi,
>
> We want to have exec/ code agnostic to accelerators.
> still we use various call to TCG and KVM. This series
> factor the TCG code from cpu_common_reset_hold() to an
> accel-specific handler within AccelOpsClass.
>
> Based-on:
On 9/18/23 12:31, Daniel Henrique Barboza wrote:
On 9/18/23 02:01, Nicholas Piggin wrote:
Hi Daniel,
Thank you for your stwardship of ppc, I might hope to do half as good a
job with it as you have. And to Greg and David for all the work over the
years.
I'm pretty sure you'll be great :D
On 9/15/23 20:41, Denis V. Lunev wrote:
If the operation is failed, we need to check image consistency if the
problem is not about memory allocation.
Bitmap adjustments in allocate_cluster are not performed yet.
They worth to be separate. This was proven useful during debug of this
series. Kept
Hi
On Sun, Sep 17, 2023 at 10:55 AM Volker Rümelin wrote:
>
> Cc: qemu-stable. Patch 1/8 is a bug fix.
> Cc: more people. The maintainer of hw/audio is busy with other projects.
>
> Earlier this year I was asked if I could help to debug an audio playback
> speed issue with the es1370 device.
Hi
On Thu, Sep 14, 2023 at 5:03 AM Stephen Brennan
wrote:
>
> This can be used from QMP command line as "-R" to mirror the
> corresponding flag for makedumpfile. This enables the kdump_reassembled
> flag introduced in the previous patch.
>
> Signed-off-by: Stephen Brennan
> ---
>
Hi
On Thu, Sep 14, 2023 at 5:04 AM Stephen Brennan
wrote:
>
> The flattened format (currently output by qemu) is used by makedumpfile
> only when it is outputting a vmcore to a file which is not seekable. The
> flattened format functions essentially as a set of instructions of the
> form "seek
Hi
On Fri, Sep 15, 2023 at 4:46 PM Michael Tokarev wrote:
>
> 15.09.2023 14:36, marcandre.lur...@redhat.com:
> > From: Marc-André Lureau
> >
> > dpy_get_ui_info() shouldn't be called if the underlying GPU doesn't
> > support it.
> >
> > Before the assert() was added and the regression
On Mon, Sep 18, 2023 at 4:32 PM David Hildenbrand wrote:
>
> On 18.09.23 13:00, Ani Sinha wrote:
> > On Mon, Sep 18, 2023 at 4:28 PM David Hildenbrand wrote:
> >>
> >> On 18.09.23 12:54, Ani Sinha wrote:
> >>> On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand
> >>> wrote:
>
> On
On 18.09.23 13:00, Ani Sinha wrote:
On Mon, Sep 18, 2023 at 4:28 PM David Hildenbrand wrote:
On 18.09.23 12:54, Ani Sinha wrote:
On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand wrote:
On 18.09.23 12:11, Ani Sinha wrote:
Ok hopefully my last question. I am still confused on
On Mon, Sep 18, 2023 at 4:30 PM Ani Sinha wrote:
>
> On Mon, Sep 18, 2023 at 4:28 PM David Hildenbrand wrote:
> >
> > On 18.09.23 12:54, Ani Sinha wrote:
> > > On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand
> > > wrote:
> > >>
> > >> On 18.09.23 12:11, Ani Sinha wrote:
> > >>
> > >>>
> >
On Mon, 18 Sept 2023 at 11:17, Philippe Mathieu-Daudé wrote:
>
> We shouldn't call QDev DeviceReset() before DeviceRealize().
>
> Since the OMAP MMC model is not QDev'ified, it has to manually
> call the SDCard reset() handler. This breaks QDev assumptions
> that DeviceReset() is never called
On Mon, Sep 18, 2023 at 4:28 PM David Hildenbrand wrote:
>
> On 18.09.23 12:54, Ani Sinha wrote:
> > On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand wrote:
> >>
> >> On 18.09.23 12:11, Ani Sinha wrote:
> >>
> >>>
> >>> Ok hopefully my last question. I am still confused on something.
> >>>
On 18.09.23 12:54, Ani Sinha wrote:
On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand wrote:
On 18.09.23 12:11, Ani Sinha wrote:
Ok hopefully my last question. I am still confused on something.
Does the above mean that the hole64 will actually start from an
address that is
If capture-output is requested but one of the channels goes unused (eg.
we attempt to capture stderr but the command never writes to stderr), we
can leak memory.
guest_exec_output_watch() is (from what I understand) unconditionally
called for both streams if output capture is requested. The first
Currently, commands run through guest-exec are "silent" until they
finish running. This is fine for short lived commands. But for commands
that take a while, this is a bad user experience.
Usually long running programs know that they will run for a while. To
improve user experience, they will
Currently, commands run through guest-exec are "silent" until they
finish running. This is fine for short lived commands. But for commands
that take a while, this is a bad user experience.
Usually long running programs know that they will run for a while. To
improve user experience, they will
On Mon, Sep 18, 2023 at 3:49 PM David Hildenbrand wrote:
>
> On 18.09.23 12:11, Ani Sinha wrote:
>
> >
> > Ok hopefully my last question. I am still confused on something.
> > Does the above mean that the hole64 will actually start from an
> > address that is beyond maxram? Like
Add a test that simulates a long running process (by using a named pipe
to synchronize). This test ensures that full output is returned with
each call to guest-exec-status.
Signed-off-by: Daniel Xu
---
tests/unit/test-qga.c | 77 +++
1 file changed, 77
On Mon Sep 18, 2023 at 5:59 PM AEST, Alex Bennée wrote:
>
> "Nicholas Piggin" writes:
>
> > On Sat Sep 16, 2023 at 1:29 PM AEST, Richard Henderson wrote:
> >> From: Nicholas Piggin
> >>
> >> mttcg asserts that an execution ending with EXCP_HALTED must have
> >> cpu->halted. However between the
On Wed, 13 Sept 2023 at 15:06, Marcin Juszkiewicz
wrote:
>
> Armv8.1+ cpus have Virtual Host Extension (VHE) which added non-secure
> EL2 virtual timer.
>
> This change adds it to fullfil Arm BSA (Base System Architecture)
> requirements.
>
> Signed-off-by: Marcin Juszkiewicz
>
> ---
>
201 - 300 of 391 matches
Mail list logo