On 20/5/25 20:28, Chenyi Qiang wrote:
Update ReplayRamDiscard() function to return the result and unify the
ReplayRamPopulate() and ReplayRamDiscard() to ReplayRamDiscardState() at
the same time due to their identical definitions. This unification
simplifies related structures, such as VirtIOM
On 20/5/25 20:28, Chenyi Qiang wrote:
Modify memory_region_set_ram_discard_manager() to return -EBUSY if a
RamDiscardManager is already set in the MemoryRegion. The caller must
handle this failure, such as having virtio-mem undo its actions and fail
the realize() process. Opportunistically mov
Hi Gustavo,
On 5/26/25 6:09 PM, Gustavo Romero wrote:
> Hi Eric,
>
> On 5/26/25 12:28, Eric Auger wrote:
>> Hi Gustavo,
>>
>> On 5/26/25 7:31 AM, Gustavo Romero wrote:
>>> ACPI PCI hotplug is now turned on by default so we need to change the
>>> existing tests to keep it off. However, even setting
On 5/27/25 11:13, Thomas Huth wrote:
On 25/05/2025 09.07, Alexandr Moshkov wrote:
Add new tests to check the correctness of the `-overcommit memlock`
option (possible values: off, on, on-fault) by using
`/proc/{qemu_pid}/status` file to check in VmSize, VmRSS and VmLck
values:
* if `memlock=o
On 25/05/2025 09.07, Alexandr Moshkov wrote:
Add new tests to check the correctness of the `-overcommit memlock`
option (possible values: off, on, on-fault) by using
`/proc/{qemu_pid}/status` file to check in VmSize, VmRSS and VmLck
values:
* if `memlock=off`, then VmLck = 0;
* if `memlock=on`,
From: Haibo Xu
KVM_CAP_ARM_EL2 must be supported by the cpu to enable ARM_FEATURE_EL2.
In case the host does support NV, expose the feature.
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
Signed-off-by: Eric Auger
Reviewed-by: Richard Henderson
---
v2 -> v3:
- check pmu->has_el2 on kvm_
This is a linux header update against kvm/next (e9f17038d814)
especially targeted to get nested virt enablement.
Signed-off-by: Eric Auger
---
include/standard-headers/linux/virtio_pci.h | 1 +
linux-headers/asm-arm64/kvm.h | 9 +
linux-headers/linux/kvm.h
Now that ARM nested virt has landed in kvm/next, let's turn the series
into a PATCH series. The linux header update was made against kvm/next.
For gaining virt functionality in KVM accelerated L1, The host needs to
be booted with "kvm-arm.mode=nested" option and qemu needs to be invoked
with: -mac
From: Haibo Xu
Introduce query support for KVM_CAP_ARM_EL2.
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
Signed-off-by: Eric Auger
Reviewed-by: Richard Henderson
Reviewed-by: Philippe Mathieu-Daudé
---
target/arm/kvm_arm.h | 7 +++
target/arm/kvm-stub.c | 5 +
target/arm/kvm
From: Haibo Xu
Allow virt arm machine to set the interrupt ID for the KVM
GIC maintenance interrupt.
This setting must be done before the KVM_DEV_ARM_VGIC_CTRL_INIT
hence the choice to perform the setting in the GICv3 realize
instead of proceeding the same way as kvm_arm_pmu_set_irq().
Signed-o
From: Haibo Xu
Up to now virt support on guest has been only supported with TCG.
Now it becomes feasible to use it with KVM acceleration.
Also check only in-kernel GICv3 is used along with KVM EL2.
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
Signed-off-by: Eric Auger
Reviewed-by: Rich
From: Junichi Uekawa
virtio-9p is not a console protocol, it's a file sharing protocol. Seems
like an artifact of old copy-and-paste error.
Fixes: 3ca4f5ca7305 ("virtio: add virtio IDs file")
Signed-off-by: Junichi Uekawa
---
include/uapi/linux/virtio_ids.h | 4 ++--
1 file changed, 2 insertio
27.05.2025 07:11, dan...@debian.org wrote:
From: Junichi Uekawa
virtio-9p is not a console protocol, it's a file sharing protocol. Seems
like an artifact of old copy-and-paste error.
-#define VIRTIO_ID_9P 9 /* 9p virtio console */
+#define VIRTIO_ID_9P 9 /
On 27/5/25 13:14, Chenyi Qiang wrote:
On 5/27/2025 9:20 AM, Alexey Kardashevskiy wrote:
On 27/5/25 11:15, Chenyi Qiang wrote:
On 5/26/2025 7:16 PM, Alexey Kardashevskiy wrote:
On 26/5/25 19:28, Chenyi Qiang wrote:
On 5/26/2025 5:01 PM, David Hildenbrand wrote:
On 20.05.25 12:28,
On 5/26/2025 5:08 PM, David Hildenbrand wrote:
> On 20.05.25 12:28, Chenyi Qiang wrote:
>> As guest_memfd is now managed by RamBlockAttribute with
>> RamDiscardManager, only block uncoordinated discard.
>>
>> Signed-off-by: Chenyi Qiang
>> ---
>> Changes in v5:
>> - Revert to use RamDiscar
On 5/26/2025 8:44 PM, Cédric Le Goater wrote:
> On 5/26/25 12:36, Cédric Le Goater wrote:
>> On 5/20/25 12:28, Chenyi Qiang wrote:
>>> So that the caller can check the result of NotifyRamDiscard() handler if
>>> the operation fails.
>>>
>>> Signed-off-by: Chenyi Qiang
>>> ---
>>> Changes in v5:
Hi Cédric,
>-Original Message-
>From: Cédric Le Goater
>Subject: Re: [PATCH rfcv3 05/21] vfio/iommufd: Save vendor specific device info
>
>Hello Zhenzhong,
>
>On 5/21/25 13:14, Zhenzhong Duan wrote:
>> Some device information returned by ioctl(IOMMU_GET_HW_INFO) are vendor
>> specific. Sa
Hi Marc-André,
> Subject: Re: [PATCH v4 0/7] ui/spice: Enable gl=on option for non-local or
> remote clients
>
> Hi
>
> On Thu, May 15, 2025 at 4:49 AM Vivek Kasireddy
> mailto:vivek.kasire...@intel.com> > wrote:
>
>
> To address the limitation that this option is incompatible with
>
From: Junichi Uekawa
virtio-9p is not a console protocol, it's a file sharing protocol. Seems
like an artifact of old copy-and-paste error.
Fixes: 3ca4f5ca7305 ("virtio: add virtio IDs file")
Signed-off-by: Junichi Uekawa
---
include/uapi/linux/virtio_ids.h | 2 +-
1 file changed, 1 insertion(
Xiaoyao Li writes:
> On 5/27/2025 12:12 AM, Paolo Bonzini wrote:
>> On 5/8/25 16:59, Xiaoyao Li wrote:
>>> This is the v9 series of TDX QEMU enabling. The series is also available
>>> at github:
>>> https://github.com/intel-staging/qemu-tdx/tree/tdx-qemu-upstream-v9
>>>
>>> Note, this series has
> Can you explain 3 more?
Pablo and I have looked into object files for one of default trace point "
trace_vhost_commit"(first tracepoint of hw/virtio) before and after making
this change and we found that by moves the hot-path check for
_simple_trace_vhost_commit into the caller (in the .h file) a
Hi Marc-André,
> Hi
>
> On Thu, May 15, 2025 at 4:49 AM Vivek Kasireddy
> mailto:vivek.kasire...@intel.com> > wrote:
>
>
> In the specific case where the display layer (virtio-gpu) is using
> dmabuf, and if remote clients are enabled (-spice gl=on,port=),
> it makes sense
Hi Michael,
> Subject: Re: [PATCH v4 5/7] ui/console-gl: Add a helper to create a texture
> with linear memory layout
>
> Hi all,
>
> I just noticed that Dmitry Osipenko had already pointed out a similar issue
> earlier-so my message was somewhat redundant. Apologies for the
> duplication.
Yeah,
在 2025/5/23 下午5:51, Bibo Mao 写道:
Memory about LoongArchExtIOICommonState::cpu is allocated in common
code, it had better be freed in common code also.
Signed-off-by: Bibo Mao
---
hw/intc/loongarch_extioi.c| 9 -
hw/intc/loongarch_extioi_common.c | 9 +
在 2025/5/5 上午4:57, Richard Henderson 写道:
Check va32 state.
Cc: Song Gao
Cc: Bibo Mao
Signed-off-by: Richard Henderson
---
target/loongarch/cpu.c | 7 +++
1 file changed, 7 insertions(+)
Reviewed-by: Song Gao
Thanks.
Song Gao
On 5/27/2025 9:20 AM, Alexey Kardashevskiy wrote:
>
>
> On 27/5/25 11:15, Chenyi Qiang wrote:
>>
>>
>> On 5/26/2025 7:16 PM, Alexey Kardashevskiy wrote:
>>>
>>>
>>> On 26/5/25 19:28, Chenyi Qiang wrote:
On 5/26/2025 5:01 PM, David Hildenbrand wrote:
> On 20.05.25 12:28, Chen
>-Original Message-
>From: Cédric Le Goater
>Subject: Re: [PATCH rfcv3 00/21] intel_iommu: Enable stage-1 translation for
>passthrough device
>
>On 5/21/25 13:14, Zhenzhong Duan wrote:
>> Hi,
>>
>> Per Jason Wang's suggestion, iommufd nesting series[1] is split into
>> "Enable stage-1 tr
On 2025/05/27 1:51, Paolo Bonzini wrote:
On 5/26/25 07:29, Akihiko Odaki wrote:
Changes in v4:
- Added patch "qemu-thread: Remove qatomic_read() in qemu_event_set()".
Hi Akihiko,
I'm not so confident about putting this patch before the other changes;
I'm referring basically to this hunk:
dif
On 2025/05/26 23:48, Peter Xu wrote:
On Mon, May 26, 2025 at 02:29:10PM +0900, Akihiko Odaki wrote:
Akihiko Odaki (11):
futex: Check value after qemu_futex_wait()
futex: Support Windows
qemu-thread: Remove qatomic_read() in qemu_event_set()
qemu-thread: Replace __linu
On 5/27/2025 12:12 AM, Paolo Bonzini wrote:
On 5/8/25 16:59, Xiaoyao Li wrote:
This is the v9 series of TDX QEMU enabling. The series is also available
at github:
https://github.com/intel-staging/qemu-tdx/tree/tdx-qemu-upstream-v9
Note, this series has a dependency on
https://lore.kernel.org/qe
On 5/26/2025 7:16 PM, Alexey Kardashevskiy wrote:
>
>
> On 26/5/25 19:28, Chenyi Qiang wrote:
>>
>>
>> On 5/26/2025 5:01 PM, David Hildenbrand wrote:
>>> On 20.05.25 12:28, Chenyi Qiang wrote:
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") highlighted
On 27/5/25 11:15, Chenyi Qiang wrote:
On 5/26/2025 7:16 PM, Alexey Kardashevskiy wrote:
On 26/5/25 19:28, Chenyi Qiang wrote:
On 5/26/2025 5:01 PM, David Hildenbrand wrote:
On 20.05.25 12:28, Chenyi Qiang wrote:
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
dis
On 2025/5/5 上午4:57, Richard Henderson wrote:
Check va32 state.
Cc: Song Gao
Cc: Bibo Mao
Signed-off-by: Richard Henderson
---
target/loongarch/cpu.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/target/loongarch/cpu.c b/target/loongarch/cpu.c
index f7535d1be7..abad84c054 10
Commit 56b1f50e3c10 ("hw/i386/pc: Wire RTC ISA IRQs in south bridges")
attempted to refactor RTC IRQ wiring which was previously done in
pc_basic_device_init() but forgot about the isapc machine. Fix this by
wiring in the code section dedicated exclusively to the isapc machine.
Resolves: https://g
Hi Eric,
On 5/26/25 12:28, Eric Auger wrote:
Hi Gustavo,
On 5/26/25 7:31 AM, Gustavo Romero wrote:
ACPI PCI hotplug is now turned on by default so we need to change the
existing tests to keep it off. However, even setting the ACPI PCI
hotplug off in the existing tests, there will be changes in
在2025年5月26日周一 下午7:05，Philippe Mathieu-Daudé写道：
> Intented to help SeaBIOS development; untested there
> (except with QEMU test suite).
>
> Jiaxun, is it helpful to you?
Hi Philippe,
Thanks for the proposal!
The spec says:
```
HBA Reset (HR): When set by SW, this bit causes an internal reset
+Gustavo
On 4/5/25 22:57, Richard Henderson wrote:
For a-profile, check A32 vs A64 state.
For m-profile, use cpu_pointer_wrap_uint32.
Cc: qemu-...@nongnu.org
Signed-off-by: Richard Henderson
---
target/arm/cpu.c | 24
target/arm/tcg/cpu-v7m.c | 1 +
2 file
Both commit ab61335025 ("block: drain from main loop thread in
bdrv_co_yield_to_drain()") and commit d05ab380db ("block: Mark drain
related functions GRAPH_RDLOCK") introduced a GLOBAL_STATE_CODE()
macro in bdrv_do_drained_end(). The assertion of being in the main
thread cannot change here, so keep
On 4/5/25 22:57, Richard Henderson wrote:
Check va32 state.
Cc: Song Gao
Cc: Bibo Mao
Signed-off-by: Richard Henderson
---
target/loongarch/cpu.c | 7 +++
1 file changed, 7 insertions(+)
Reviewed-by: Philippe Mathieu-Daudé
On 5/5/25 18:16, Richard Henderson wrote:
On 5/5/25 07:41, Philippe Mathieu-Daudé wrote:
On 4/5/25 22:57, Richard Henderson wrote:
Use the existing wrap_address function.
Cc: qemu-s3...@nongnu.org
Signed-off-by: Richard Henderson
---
target/s390x/cpu.c | 9 +
1 file changed, 9 inse
On 5/5/25 20:59, Richard Henderson wrote:
On 5/5/25 09:47, Philippe Mathieu-Daudé wrote:
On 4/5/25 22:57, Richard Henderson wrote:
Check 32 vs 64-bit and pointer masking state.
Cc: qemu-ri...@nongnu.org
Signed-off-by: Richard Henderson
---
target/riscv/tcg/tcg-cpu.c | 26 +++
On 24/5/25 16:40, Richard Henderson wrote:
When we moved TLB_MMIO and TLB_DISCARD_WRITE to TLB_SLOW_FLAGS_MASK,
we failed to update atomic_mmu_lookup to properly reconstruct flags.
Fixes: 24b5e0fdb543 ("include/exec: Move TLB_MMIO, TLB_DISCARD_WRITE to slow
flags")
Cc'ing Pierrick
Reported-
On 23/5/25 18:01, Liam Merwick wrote:
When the '--enable-trace-backends=syslog' build option is configured,
the following compilation error is encountered.
In file included from /usr/include/sys/syslog.h:207,
from /usr/include/syslog.h:1,
from ./trace/trace-hw
AHCI reset is not instantaneous in physical world, and software
might poll the reset bits of port and host control registers to
detect completion (see chapter 14 of AHCI spec).
In preparation of adding a timed reset, split ahci_reset()
as ahci_reset_delayed() which keeps the reset bits and
ahci_re
Give few milliseconds to (emulated) hardware to complete
its reset sequence.
The intent is to have this model better match hardware,
reducing firmware bugs "works in QEMU but not in real
world" such https://github.com/FlyGoat/csmwrap/issues/14.
Reported-by: Jiaxun Yang
Signed-off-by: Philippe Ma
Intented to help SeaBIOS development; untested there
(except with QEMU test suite).
Jiaxun, is it helpful to you?
Philippe Mathieu-Daudé (2):
hw/ide/ahci: Introduce ahci_reset_delayed() and ahci_reset_complete()
hw/ide/ahci: Delay a bit before completing reset
include/hw/ide/ahci.h | 1 +
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.1 for any
user-visible changes.
signature.asc
Description: PGP signature
OK. Let me clarify this at the top as I see the gap here now:
First, the vSMMU model is based on Zhenzhong's older series that
keeps an ioas_id in the HostIOMMUDeviceIOMMUFD structure, which
now it only keeps an hwpt_id in this RFCv3 series. This ioas_id
is allocated when a passthrough cdev attach
On 5/26/25 10:52, Philippe Mathieu-Daudé wrote:
Replace target_ulong by vaddr or size_t types to match
cpu_memory_rw_debug() prototype in "exec/cpu-common.h":
> int cpu_memory_rw_debug(CPUState *cpu, vaddr addr,
> void *ptr, size_t len,
>
On 5/26/25 10:52, Philippe Mathieu-Daudé wrote:
Signed-off-by: Philippe Mathieu-Daudé
---
semihosting/meson.build | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/semihosting/meson.build b/semihosting/meson.build
index f3d38dda91d..b1ab2506c6e 100644
--- a/semihosting/m
The test fails with --enable-asan as the error struct is never freed.
In the case where the test expects a success but it fails, let's also
report the error for debugging (it will be freed internally).
Fixes 316e8ee8d6 ("util/qemu-sockets: Refactor inet_parse() to use QemuOpts")
Signed-off-by: Mat
On 5/26/25 07:29, Akihiko Odaki wrote:
Changes in v4:
- Added patch "qemu-thread: Remove qatomic_read() in qemu_event_set()".
Hi Akihiko,
I'm not so confident about putting this patch before the other changes;
I'm referring basically to this hunk:
diff --git a/util/event.c b/util/event.c
inde
On 5/19/25 15:26, Steve Sistare wrote:
Modify memory_get_xlat_addr and vfio_get_xlat_addr to return the memory
region that the translated address is found in. This will be needed by
CPR in a subsequent patch to map blocks using IOMMU_IOAS_MAP_FILE.
Also return the xlat offset, so we can simplif
On 5/22/25 17:16, Tomita Moeko wrote:
In vfio_pci_igd_opregion_detect(), errp will be set when the device does
not have OpRegion or is hotplugged. This errp will be propagated to
pci_qdev_realize(), which interprets it as failure, causing unexpected
termination on devices without OpRegion like SR
On 5/26/25 10:54, Julian Ganz wrote:
Hi Richard,
May 26, 2025 at 11:01 AM, Richard Henderson wrote:
On 5/25/25 21:16, Julian Ganz wrote:
Also, some targets such as tricore only have a dummy/stub do_interrupt
and handle exceptions differently inside non-returning functions. For
those, we wo
On Fri, May 23, 2025 at 04:01:34PM +, Liam Merwick wrote:
> When the '--enable-trace-backends=syslog' build option is configured,
> the following compilation error is encountered.
>
> In file included from /usr/include/sys/syslog.h:207,
> from /usr/include/syslog.h:1,
>
On 5/8/25 16:59, Xiaoyao Li wrote:
This is the v9 series of TDX QEMU enabling. The series is also available
at github:
https://github.com/intel-staging/qemu-tdx/tree/tdx-qemu-upstream-v9
Note, this series has a dependency on
https://lore.kernel.org/qemu-devel/20241217123932.948789-1-xiaoyao...@i
Queued, thanks.
Paolo
On Fri, May 23, 2025 at 02:06:42AM +, Zhijian Li (Fujitsu) wrote:
>
>
> On 22/05/2025 21:16, Peter Xu wrote:
> > I followed up with Dave's idea, but then added all entries into it, below.
> >
> >Status: postcopy-active
> >Time (ms): total=40504, setup=14, down=145
> >RAM info:
>
Peter Xu writes:
> On Thu, May 22, 2025 at 02:39:48PM -0300, Fabiano Rosas wrote:
>> Actually, this doesn't work...
>>
>> The migrate-set-* commands have optional fields, so we need some form of
>> checking has_* to know which fields the user is setting. Otherwise
>> MigrationSetParameters will
Markus Armbruster writes:
> Fabiano Rosas writes:
>
>> Commit 407bc4bf90 ("qapi: Move include/qapi/qmp/ to include/qobject/")
>> brought the migration-helpers.c back by mistake. This file has been
>> replaced with migration/migration-qmp.c and
>> migration/migration-util.c.
>>
>> Fixes: 407bc4bf
On Mon, May 26, 2025 at 08:09:13AM +0200, Markus Armbruster wrote:
> Fabiano Rosas writes:
>
> > Commit 407bc4bf90 ("qapi: Move include/qapi/qmp/ to include/qobject/")
> > brought the migration-helpers.c back by mistake. This file has been
> > replaced with migration/migration-qmp.c and
> > migra
Hi Gustavo,
On 5/26/25 7:31 AM, Gustavo Romero wrote:
> ACPI PCI hotplug is now turned on by default so we need to change the
> existing tests to keep it off. However, even setting the ACPI PCI
> hotplug off in the existing tests, there will be changes in the ACPI
> tables because the _OSC method
Hi all,
I just noticed that Dmitry Osipenko had already pointed out a similar
issue earlier—so my message was somewhat redundant. Apologies for the
duplication.
Also, I made a small mistake in the patch I proposed:
The call to glDeleteMemoryObjectsEXT(1, &mem_obj); should be placed
above the
On 5/24/25 02:33, Dmitry Osipenko wrote:
> + * - Asahi DRM native context
> +- `Downstream version`_ of Asahi Linux kernel
> +- `mr1274`_
> +
> +.. _mr1384:
> https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1384
> +.. _mr1274:
> https://gitlab.freedesktop.org/virgl/vi
Rust makes the current file available as a statically-allocated string,
but without a NUL terminator. Allow this by storing an optional maximum
length in the Error.
Note that for portability I am not relying on fprintf's precision
specifier not accessing memory beyond what will be printed.
Signe
On 5/24/25 02:32, Dmitry Osipenko wrote:
> @@ -872,6 +872,8 @@ void virtio_gpu_virgl_process_cmd(VirtIOGPU *g,
>struct virtio_gpu_ctrl_command *cmd)
> {
> bool cmd_suspended = false;
> +uint32_t flags;
Realized I re-introduced the build warning wit
On Mon, May 26, 2025 at 10:03:55AM +0200, Markus Armbruster wrote:
> > diff --git a/qapi/migration.json b/qapi/migration.json
> > index bb2487dbc6..5bd8f0f1b2 100644
> > --- a/qapi/migration.json
> > +++ b/qapi/migration.json
> > @@ -1638,6 +1638,10 @@
>##
># @migrate:
>#
># Migrate
On Mon, May 26, 2025 at 02:29:10PM +0900, Akihiko Odaki wrote:
> Akihiko Odaki (11):
> futex: Check value after qemu_futex_wait()
> futex: Support Windows
> qemu-thread: Remove qatomic_read() in qemu_event_set()
> qemu-thread: Replace __linux__ with CONFIG_LINUX
> qemu
On 5/26/25 3:51 PM, Gustavo Romero wrote:
> Hi Eric,
>
> On 5/26/25 07:25, Eric Auger wrote:
>> Hi Gustavo,
>>
>> On 5/26/25 7:31 AM, Gustavo Romero wrote:
>>> Update the aarch64 'virt' base blob and all of its variants. All of
>>> them
>>> have the same diff, so only one is shown below. The ess
On Thu, May 08, 2025 at 06:50:34PM -0400, Zhuoying Cai wrote:
> The secure-IPL-code-loading-attributes facility (SCLAF)
> provides additional security during IPL.
>
> Availability of SCLAF is determined by byte 136 bit 3 of the
> SCLP Read Info block.
>
> Signed-off-by: Zhuoying Cai
> ---
> tar
This is used to preserve the file and line in a roundtrip from
C Error to Rust and back to C.
Signed-off-by: Paolo Bonzini
---
include/qapi/error-internal.h | 26 ++
rust/wrapper.h| 1 +
util/error.c | 10 +-
3 files changed, 28 i
Do not silently adjust num_timers, and fail if intcap is 0.
Signed-off-by: Paolo Bonzini
---
hw/timer/hpet.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
index d1b7bc52b7b..d78aba04bcd 100644
--- a/hw/timer/hpet.c
+++ b/hw/
This is a cleaned up and separated version of the patches at
https://lore.kernel.org/all/20240701145853.1394967-4-pbonz...@redhat.com/
https://lore.kernel.org/all/20240701145853.1394967-5-pbonz...@redhat.com/
Its first user will be the Error bindings; for example a QEMU Error ** can be
converted t
On Sun, May 25, 2025 at 11:23:57PM +0200, Cédric Le Goater wrote:
> Michael,
>
> On 5/20/25 15:46, Cédric Le Goater wrote:
> >
> > > > > @@ -1010,6 +1017,8 @@ static void
> > > > > vfio_iommu_map_dirty_notify(IOMMUNotifier *n, IOMMUTLBEntry *iotlb)
> > > > > ram_addr_t translated_addr;
> >
From: Steffen Hirschmann
This commit implements counting of executed instruction within certain
virtual address ranges via libinsn.so
Signed-off-by: Steffen Hirschmann
---
docs/about/emulation.rst | 2 +
tests/tcg/plugins/insn.c | 91
2 files changed,
Great to see this patch making progress.
I've tested it extensively, and unfortunately, I’ve noticed a memory
leak in surface_gl_create_texture_from_fd(). The memory leak is hard to
see since the memory is owned by the gpu driver.
On Intel hardware, it's possible to observe the leak using:
ca
Signed-off-by: Paolo Bonzini
---
rust/hw/char/pl011/src/device.rs | 5 +++--
rust/hw/timer/hpet/src/hpet.rs | 5 +++--
rust/qemu-api/src/qdev.rs| 10 ++
3 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/rust/hw/char/pl011/src/device.rs b/rust/hw/char/pl011/src/de
Philippe Mathieu-Daudé writes:
> +Markus
>
> On 24/5/25 13:55, Richard Henderson wrote:
>> On 5/15/25 14:20, Thomas Huth wrote:
>>> +static int machine_get_endianness(Object *obj, Error **errp G_GNUC_UNUSED)
>>> +{
>>> + S3Adsp1800MachineState *ms = PETALOGIX_S3ADSP1800_MACHINE(obj);
>>> +
Provide an implementation of std::error::Error that bridges the Rust
anyhow::Error and std::panic::Location types with QEMU's Error*.
It also has several utility methods, analogous to error_propagate(),
that convert a Result into a return value + Error** pair.
Signed-off-by: Paolo Bonzini
---
ru
Match the code in hpet.c; this also allows removing the
BqlCell from the num_timers field.
Signed-off-by: Paolo Bonzini
---
rust/hw/timer/hpet/src/fw_cfg.rs | 7 +++
rust/hw/timer/hpet/src/hpet.rs | 16 +++-
2 files changed, 10 insertions(+), 13 deletions(-)
diff --git a/rust
From: Zhao Liu
Now that the num_timers field is initialized as a property, someone may
change its default value using qdev_prop_set_uint8(), but the value is
fixed after the Rust code sees it first. Since there is no need to modify
it after realize(), it is not to be necessary to have a BqlCell
The function name is not available in Rust, so make it optional.
Signed-off-by: Paolo Bonzini
---
util/error.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/util/error.c b/util/error.c
index 6c1033eaba5..b977007faaf 100644
--- a/util/error.c
+++ b/util/error.c
@@ -2
Remove the need to convert after every read of the BqlCell. Because the
vmstate uses a u8 as the size of the VARRAY, this requires switching
the VARRAY to use num_timers_save; which in turn requires ensuring that
the num_timers_save is always there. For simplicity do this by
removing support for
This is a standard replacement for Box which is more efficient (it
only
occcupies one word) and provides a backtrace of the error. This could be
plumbed
into &error_abort in the future.
Signed-off-by: Paolo Bonzini
---
rust/meson.build | 2 ++
subprojects/.gitign
Crates like "bilge" and "libc" can be shared by more than one directory,
so declare them directly in rust/meson.build. While at it, make their
variable names end with "_rs" and always add a subproject() statement
(as that pinpoints the error better if the subproject is missing and
cannot be downlo
This was one of the first bindings that I wrote in
https://lore.kernel.org/qemu-devel/20240701145853.1394967-1-pbonz...@redhat.com/T/,
but there were a few obstacles to clear before including them:
1) cleaning up the *foreign*() functions (patches 3-4 from the above
series) or deciding not to use
On 26/5/25 15:18, BALATON Zoltan wrote:
On Mon, 26 May 2025, Philippe Mathieu-Daudé wrote:
Only add default devices checking defaults_enabled().
Remove the unused usb_disabled field in MachineState.
At least for Mac machines this may be more complex. I think there is a -
usb switch to enable/
Many write-locked sections are also drained sections. A new
bdrv_graph_wrunlock_drained() wrapper around bdrv_graph_wrunlock() is
introduced, which will begin a drained section first. A global
variable is used so bdrv_graph_wrunlock() knows if it also needs
to end such a drained section. Both the a
Hi Eric,
On 5/26/25 10:23, Eric Auger wrote:
Hi Gustavo,
On 5/26/25 7:31 AM, Gustavo Romero wrote:
ACPI PCI hotplug is now turned on by default so we need to change the
existing tests to keep it off. However, even setting the ACPI PCI
hotplug off in the existing tests, there will be changes in
On Thu, May 22, 2025 at 08:08:44PM +0200, Thomas Huth wrote:
> On 22/05/2025 16.38, Peter Xu wrote:
> > On Thu, May 22, 2025 at 03:37:55PM +0200, Thomas Huth wrote:
> >
> > [...]
> >
> > > +def test_vmstate(self):
> > > +target_machine = {
> > > +'aarch64': 'virt-7.2',
> >
Hi Eric,
On 5/26/25 07:21, Eric Auger wrote:
Hi Gustavo,
On 5/26/25 7:55 AM, Gustavo Romero wrote:
Hi Eric,
On 5/14/25 14:00, Eric Auger wrote:
This series enables ACPI PCI hotplug/hotunplug on ARM
and makes it default for 10.1 machine type. This aligns with
x86 q35 machine. Expected benefit
Suggested-by: Kevin Wolf
Signed-off-by: Fiona Ebner
---
No changes in v3.
tests/qemu-iotests/tests/graph-changes-while-io | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/qemu-iotests/tests/graph-changes-while-io
b/tests/qemu-iotests/tests/graph-changes-while-io
index 194fda500e..354
Hi Eric,
On 5/26/25 07:25, Eric Auger wrote:
Hi Gustavo,
On 5/26/25 7:31 AM, Gustavo Romero wrote:
Update the aarch64 'virt' base blob and all of its variants. All of them
have the same diff, so only one is shown below. The essential changes is
in the AML code of the _OSC (OS Capabilities) met
On Thu, May 22, 2025 at 08:12:49PM +0200, Thomas Huth wrote:
> On 22/05/2025 16.40, Peter Xu wrote:
> > On Thu, May 22, 2025 at 03:37:56PM +0200, Thomas Huth wrote:
> > > From: Thomas Huth
> > >
> > > We've got two vmstate dump files in the repository which are meant
> > > for verifying whether t
This is part of resolving the deadlock mentioned in commit "block:
move draining out of bdrv_change_aio_context() and mark GRAPH_RDLOCK".
bdrv_root_unref_child() is called by:
1. blk_remove_bs(), where a drained section is introduced.
2. bdrv_unref_child(), which runs under the graph lock, so the
This is in preparation to mark bdrv_drained_begin() as GRAPH_UNLOCKED.
More granular draining is not trivially possible, because
bdrv_snapshot_delete() can recursively call itself.
The return value of bdrv_all_delete_snapshot() changes from -1 to
-errno propagated from failed sub-calls. This is f
This is in preparation to mark bdrv_drained_begin() as GRAPH_UNLOCKED.
More granular draining is not trivially possible, because
bdrv_reopen_queue_child() can recursively call itself.
Signed-off-by: Fiona Ebner
Reviewed-by: Kevin Wolf
---
No changes in v3.
block.c | 19 +++
1
This is in preparation to mark bdrv_drained_begin() as GRAPH_UNLOCKED.
Signed-off-by: Fiona Ebner
---
No changes in v3.
blockdev.c | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index bd5ca77619..506755bef1 100644
--- a/blockdev
This is a small step in preparation to mark bdrv_drained_begin() as
GRAPH_UNLOCKED. More concretely, it allows marking the
change_aio_ctx() callback GRAPH_RDLOCK_PTR, which is the next step.
Signed-off-by: Fiona Ebner
Reviewed-by: Kevin Wolf
---
No changes in v3.
block.c | 8
1 file
1 - 100 of 228 matches
Mail list logo
