When talking about the job state machine, we refer to the states like
READY, ABORTING, CONCLUDED, and so forth. Except in two places, where
we use JOB_STATUS_CONCLUDED. Replace by CONCLUDED for consistency.
We should arguably use the JobStatus enum values instead. Left for
another day.
Signed-
We use "the query list" in a few places. It's not entirely obvious
what that means. It's actually the output of query-jobs or
query-block-jobs.
Documentation of @auto-dismiss talks about the job disappearing from
the query list when it reaches state @concluded. This is less than
precise. The j
The doc comment misspells JSON null as NULL. Fix that.
Cc: Kevin Wolf
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-10-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/block-core.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qapi/block-core
Queued.
Am 2. Juni 2025 08:12:39 UTC schrieb "Philippe Mathieu-Daudé"
:
>On 30/5/25 02:54, BALATON Zoltan wrote:
>> On Thu, 29 May 2025, Bernhard Beschow wrote:
>>> Am 25. April 2025 15:28:20 UTC schrieb "Philippe Mathieu-Daudé"
>>> :
From: BALATON Zoltan
We have several device tree f
Several doc comments mention block-job-cancel where the more generic
job-cancel would also work. Adjust them to mention both.
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-12-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/block-core.json | 10 +-
1 file chan
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-3-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/block-core.json | 16
qapi/block-export.json | 4 ++--
qapi/char.json | 2 +-
qapi/crypto.json | 3 ++-
qapi/job.json | 8 -
Fixes: a937b6aa739f (qapi: Reformat doc comments to conform to current
conventions)
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-2-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/acpi.json | 2 +-
qapi/block-core.json | 14 +++---
qapi/crypto.json
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-8-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/block-core.json | 6 +++---
qapi/block.json | 2 +-
qapi/cryptodev.json | 2 +-
qapi/cxl.json | 2 +-
qapi/machine.json | 2 +-
qapi/misc-i386.json |
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-9-arm...@redhat.com>
Reviewed-by: Eric Blake
---
qapi/block-core.json | 2 +-
qapi/dump.json | 6 +++---
qapi/migration.json | 26 +-
qapi/misc.json | 4 ++--
4 files changed, 19 insertio
We deprecated several block-job-FOO commands in commit
b836bf2ab68 (qapi/block-core: deprecate some block-job- APIs). Update
the doc comments to refer to their replacements instead.
Signed-off-by: Markus Armbruster
Message-ID: <20250527073916.1243024-11-arm...@redhat.com>
Reviewed-by: Eric Blake
The following changes since commit 6322b753f798337835e205b6d805356bea582c86:
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu
into staging (2025-06-02 14:52:45 -0400)
are available in the Git repository at:
https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2025-0
There is a (Since: 2.11) in a query-hotpluggable-cpus example.
Versioning information ought to be in the command description, not
examples. The command description is basically empty (there is a TODO
about it).
What exactly didn't work before 2.11 is not quite clear from the
documentation. The e
On 6/3/2025 1:26 PM, Gupta, Pankaj wrote:
> On 6/3/2025 3:26 AM, Chenyi Qiang wrote:
>>
>>
>> On 6/1/2025 5:58 PM, Gupta, Pankaj wrote:
>>> On 5/30/2025 10:32 AM, Chenyi Qiang wrote:
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") highlighted that subsyst
On 03/06/2025 01.38, Pierrick Bouvier wrote:
Fixed commit introduced common dependencies for target libraries. Alas,
it wrongly reused the 'target' variable, which was previously set from
another loop.
Thus, some dependencies were missing depending on order of target list,
as found here [1].
Th
Stefan Hajnoczi writes:
> On Wed, May 28, 2025 at 05:12:14PM -0500, Eric Blake wrote:
>> On Wed, May 28, 2025 at 03:09:13PM -0400, Stefan Hajnoczi wrote:
>> > io_uring may not be available at runtime due to system policies (e.g.
>> > the io_uring_disabled sysctl) or creation could fail due to fil
On Fri, May 30, 2025 at 10:03:06AM +0200, Paolo Bonzini wrote:
> Date: Fri, 30 May 2025 10:03:06 +0200
> From: Paolo Bonzini
> Subject: [PATCH 14/14] docs: update Rust module status
> X-Mailer: git-send-email 2.49.0
>
> error is new; offset_of is gone.
>
> Signed-off-by: Paolo Bonzini
> ---
>
Change sha348 to sha384.
Signed-off-by: Xiaoyao Li
---
target/i386/kvm/tdx.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target/i386/kvm/tdx.h b/target/i386/kvm/tdx.h
index 04b5afe199f9..8dd66e90149b 100644
--- a/target/i386/kvm/tdx.h
+++ b/target/i386/kvm/tdx.h
@@
On 6/3/2025 3:26 AM, Chenyi Qiang wrote:
On 6/1/2025 5:58 PM, Gupta, Pankaj wrote:
On 5/30/2025 10:32 AM, Chenyi Qiang wrote:
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") highlighted that subsystems like VFIO may disable RAM block
discard. However, guest_memf
Patch 1 and patch 3 are the left review feedback of TDX QEMU v9 series.
Patch 2 is caught during preparing patch 3.
Xiaoyao Li (3):
i386/cpu: Rename enable_cpuid_0x1f to force_cpuid_0x1f
i386/tdx: Fix the typo of the comment of struct TdxGuest
i386/tdx: Clarify the error message of
mrc
The name of "enable_cpuid_0x1f" isn't right to its behavior because the
leaf 0x1f can be enabled even when "enable_cpuid_0x1f" is false.
Rename it to "force_cpuid_0x1f" to better reflect its behavior.
Suggested-by: Igor Mammedov
Signed-off-by: Xiaoyao Li
---
Suggested by Igor at
https://lore.k
The error message is misleading - we successfully decoded the data,
the decoded data was simply with the wrong length.
Change the error message to show it is an length check failure with both
the received and expected values.
Suggested-by: Daniel P. Berrangé
Signed-off-by: Xiaoyao Li
---
Sugges
Hi Alistair,
Thanks for your review.
On 6/2/2025 1:11 PM, Alistair Francis wrote:
> On Thu, May 29, 2025 at 10:52 PM Nutty Liu
> wrote:
>> The original implementation incorrectly performed a bitwise AND
>> operation between the PPN of iova and PPN Mask, leading to an
>> incorrect PPN field in Tr
Hi Alistair,
> -Original Message-
> From: qemu-riscv-bounces+alvinga=andestech@nongnu.org
> On Behalf Of
> Alistair Francis
> Sent: Thursday, March 6, 2025 2:18 PM
> To: Florian Lugou
> Cc: qemu-devel@nongnu.org; Palmer Dabbelt ;
> Alistair Francis ; Bin Meng
> ; Weiwei Li ; Daniel
>
Reviewed-by: Bibo Mao
On 2025/6/3 上午11:18, Qiang Ma wrote:
Commit bab27ea2e3 ("hw/arm/virt: smbios:
inform guest of kvm") fixes the same issue
on arm.
without this patch:
[root@localhost ~]# virt-what
qemu
with this patch:
[root@localhost ~]# virt-what
kvm
Signed-off-by: Qiang Ma
---
hw/l
On Fri, May 30, 2025 at 10:03:02AM +0200, Paolo Bonzini wrote:
> Date: Fri, 30 May 2025 10:03:02 +0200
> From: Paolo Bonzini
> Subject: [PATCH 10/14] hpet: adjust VMState for consistency with Rust
> version
> X-Mailer: git-send-email 2.49.0
>
> No functional change intended.
>
> Suggested-by: Z
Commit bab27ea2e3 ("hw/arm/virt: smbios:
inform guest of kvm") fixes the same issue
on arm.
without this patch:
[root@localhost ~]# virt-what
qemu
with this patch:
[root@localhost ~]# virt-what
kvm
Signed-off-by: Qiang Ma
---
hw/loongarch/virt.c | 4
1 file changed, 4 insertions(+)
diff
>-Original Message-
>From: Nicolin Chen
>Subject: Re: [PATCH v2 3/4] vfio/iommufd: Implement [at|de]tach_hwpt handlers
>
>On Fri, May 30, 2025 at 05:35:11PM +0800, Zhenzhong Duan wrote:
>> Implement [at|de]tach_hwpt handlers in VFIO subsystem. vIOMMU
>> utilizes them to attach to or det
On 6/3/2025 1:31 AM, Cédric Le Goater wrote:
Use PRI formats where required and fix pointer cast.
Maybe we can make 32-bit build exclusive with CONFIG_TDX? since TDX is
not supported on 32-bit host.
Cc: Xiaoyao Li
Signed-off-by: Cédric Le Goater
---
target/i386/kvm/tdx.c | 26 ++
在 2025/6/3 上午11:18, Qiang Ma 写道:
Commit bab27ea2e3 ("hw/arm/virt: smbios:
inform guest of kvm") fixes the same issue
on arm.
without this patch:
[root@localhost ~]# virt-what
qemu
with this patch:
[root@localhost ~]# virt-what
kvm
Signed-off-by: Qiang Ma
---
hw/loongarch/virt.c | 4
1
>-Original Message-
>From: Nicolin Chen
>Subject: Re: [PATCH v2 4/4] vfio/iommufd: Save vendor specific device info
>
>On Fri, May 30, 2025 at 05:35:12PM +0800, Zhenzhong Duan wrote:
>> Some device information returned by ioctl(IOMMU_GET_HW_INFO) are vendor
>> specific. Save them as raw
fcond only has 22 types, add a check for fcond.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2972
Signed-off-by: Song Gao
---
.../loongarch/tcg/insn_trans/trans_fcmp.c.inc | 25 +--
.../loongarch/tcg/insn_trans/trans_vec.c.inc | 16 +---
2 files changed, 30 i
>-Original Message-
>From: Nicolin Chen
>Subject: Re: [PATCH v2 2/4] vfio/iommufd: Add properties and handlers to
>TYPE_HOST_IOMMU_DEVICE_IOMMUFD
>
>On Fri, May 30, 2025 at 05:35:10PM +0800, Zhenzhong Duan wrote:
>> Enhance HostIOMMUDeviceIOMMUFD object with 3 new members, specific
>> t
on qemu we got an aborted error
**
ERROR:../target/loongarch/tcg/insn_trans/trans_vec.c.inc:3574:vldi_get_value:
code should not be reached
Bail out!
ERROR:../target/loongarch/tcg/insn_trans/trans_vec.c.inc:3574:vldi_get_value:
code should not be reached
Aborted (core dumped)
bu on 3A600/3A5000
On Fri, May 30, 2025 at 1:19 PM Akihiko Odaki wrote:
>
> virtio_net_pre_load_queues() inspects vdev->guest_features to tell if
> VIRTIO_NET_F_RSS or VIRTIO_NET_F_MQ is enabled to infer the required
> number of queues. This works for VIRTIO_NET_F_MQ but it doesn't for
> VIRTIO_NET_F_RSS because onl
On Mon, Jun 2, 2025 at 4:57 PM Anastasia Belova wrote:
>
> s->pool has n_descs elements so maximum i should be
> n_descs - 1. Fix the upper bound.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: cb039ef3d9 ("net: add initial support for AF_XDP network backend")
> S
On Fri, May 30, 2025 at 10:02:55AM +0200, Paolo Bonzini wrote:
> Date: Fri, 30 May 2025 10:02:55 +0200
> From: Paolo Bonzini
> Subject: [PATCH 03/14] util/error: expose Error definition to Rust code
> X-Mailer: git-send-email 2.49.0
>
> This is used to preserve the file and line in a roundtrip fr
Hi all,
Kinldy ping on this patch series. I would appreciate any feedback or
comments.
Patchew URL:
https://patchew.org/QEMU/cover.1747922170.git.ktokunaga.m...@gmail.com/
Kohei
On 6/3/2025 5:10 AM, David Hildenbrand wrote:
> On 30.05.25 10:32, Chenyi Qiang wrote:
>> Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
>> discard") highlighted that subsystems like VFIO may disable RAM block
>> discard. However, guest_memfd relies on discard operations fo
Add capabilities to MigrationParameters. This structure will hold all
migration options. Capabilities will go away in the next patch.
Also add capabilities to MigrationParameter as the enum needs to be
kept in sync with MigrationParameters. This affects the parsing of
migration HMP commands so mak
QAPI_CLONE_MEMBERS is a better option than copying parameters one by
one because it operates on the entire struct and follows pointers. It
also avoids the need to alter this function every time a new parameter
is added.
Note, since this is a deep clone, now we must free the TLS strings
before assi
Add a QAPI command feature "capabilities" that can be queried by the
client to check that the parameters commands now also support
capabilities.
Signed-off-by: Fabiano Rosas
---
qapi/migration.json | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/qapi/mig
Pass the config directly via the migrate/incoming command.
Signed-off-by: Fabiano Rosas
---
tests/qtest/migration/framework.h | 2 ++
tests/qtest/migration/misc-tests.c | 39 ++
2 files changed, 41 insertions(+)
diff --git a/tests/qtest/migration/framework.h
b/tes
The QAPI converts an empty list on the block-bitmap-mapping input into
a NULL BitmapMigrationNodeAliasList. The empty list is a valid input
for the block-bitmap-mapping option, so commit 3cba22c9ad ("migration:
Fix block_bitmap_mapping migration") started using the
s->parameters.has_block_bitmap_ma
Hi,
Thanks for the reviews in the last round. Your feedback has allowed me
to reduce the complexity of the series and the code considerably.
Changes in this v2:
- Followed the suggestion to unify the TLS strings as StrOrNull. This
allows the complete removal of the MigrateSetParameters
type.
The response type of query-migrate-parameters is MigrationParameters,
the members of which are marked as optional in
migration.json. However, the design of query-migrate-parameters is
that all members are to be non-optional.
The optionality is an attempt at compatibility with
MigrateSetParameters,
Last patch added capabilities to s->parameters. Now we can replace all
instances of s->capabilities with s->parameters:
- The -global properties now get set directly in s->parameters.
- Accessors from options.c now read from s->parameters.
- migrate_caps_check() now takes a MigrationParameters o
Some migration parameters are updated immediately once they are set
via migrate-set-parameters. Move that work outside of
migrate_params_apply() and leave that function with the single
responsibility of setting s->parameters and not doing any
side-effects.
Reviewed-by: Peter Xu
Signed-off-by: Fab
MigrationParameters needs to have all of its has_* fields marked as
true when used as the return of query_migrate_parameters because the
corresponding QMP command has all of its members non-optional by
design, despite them being marked as optional in migration.json.
Extract this code into a functi
Allow the migrate and migrate_incoming commands to pass the migration
configuration options all at once, dispensing the use of
migrate-set-parameters and migrate-set-capabilities.
The motivation of this is to simplify the interface with the
management layer and avoid the usage of several command i
The migration parameters validation produces a temporary structure
which is the merge of the current parameter values (s->parameters,
MigrationParameters) with the new parameters set by the user
(MigrateSetParameters).
When copying the values from s->parameters into the temporary
structure, the ha
Do a cleanup of hmp_info_migrate_parameters() before adding more lines
into it:
- Make sure every parameter asserts that the has_* field is
set. qmp_query_migrate_parameters should have set them all.
- Remove the if (params), qmp_query_migrate_parameters never returns
NULL.
- Add a macro to
Signed-off-by: Fabiano Rosas
---
tests/qtest/libqtest.c | 42 ++
tests/qtest/libqtest.h | 12
2 files changed, 54 insertions(+)
diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
index 94526b7f9c..7ee4831841 100644
--- a/tests/qtest/
Use QAPI_CLONE_MEMBERS instead of making an assignment. The QAPI
method makes the handling of the TLS strings more intuitive because it
clones them as well.
Signed-off-by: Fabiano Rosas
---
migration/options.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff -
The MigrationParameter (singular) enumeration is not part of the
migration QMP API, it's only used for nicely converting HMP strings
into MigrationParameters (plural) members and for providing readline
completion.
Documenting this enum only serves to duplicate documentation between
MigrationParame
Instead of setting parameters one by one, use the temporary object,
which already contains the current migration parameters plus the new
ones and was just validated by migration_params_check(). Use cloning
to overwrite it.
This avoids the need to alter this function every time a new parameter
is a
The QERR_INVALID_PARAMETER_VALUE macro is documented as not to be used
in new code. Remove the usage from migration/options.c.
Signed-off-by: Fabiano Rosas
---
migration/migration.c | 3 +--
migration/options.c| 56 +++---
migration/page_cache.c | 6 ++-
The concept of capabilities is being merged into the concept of
parameters. From now on, the commands that handle capabilities are
deprecated in favor of the commands that handle parameters.
Affected commands:
- migrate-set-capabilities
- query-migrate-capabilities
Signed-off-by: Fabiano Rosas
Now that the TLS options have been made the same between
migrate-set-parameters and query-migrate-parameters, a single type can
be used. Remove MigrateSetParameters.
The TLS options documentation from MigrationParameters were replaced
with the ones from MigrateSetParameters which was more complete
The migration parameters tls_creds, tls_authz and tls_hostname
currently have a non-uniform handling. When used as arguments to
migrate-set-parameters, their type is StrOrNull and when used as
return value from query-migrate-parameters, their type is a plain
string.
Not only having to convert betw
Convert the code in migrate_params_test_apply() from an open-coded
copy of every migration parameter to a copy using visitors.
This hides the details of QAPI from the migration code and avoids the
need to update migrate_params_test_apply() every time a new migration
parameter is added. Both were v
On 6/1/2025 5:58 PM, Gupta, Pankaj wrote:
> On 5/30/2025 10:32 AM, Chenyi Qiang wrote:
>> Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
>> discard") highlighted that subsystems like VFIO may disable RAM block
>> discard. However, guest_memfd relies on discard operations fo
On 2025/6/3 上午5:58, Michael S. Tsirkin wrote:
On Mon, Jun 02, 2025 at 02:31:19PM -0400, Michael S. Tsirkin wrote:
On Mon, Jun 02, 2025 at 02:25:48PM -0400, Stefan Hajnoczi wrote:
On Mon, Jun 2, 2025 at 1:54 PM Michael S. Tsirkin wrote:
On Mon, Jun 02, 2025 at 12:39:17PM -0400, Stefan Hajn
Peter Xu writes:
> Add a global property to allow enabling postcopy-blocktime feature.
>
> Signed-off-by: Peter Xu
Reviewed-by: Fabiano Rosas
This patch set is a follow on to commit ebd1568fc732 ("hw/nvme: add atomic
write support"). These patches introduces two updates to the NVMe subsystem in
QEMU,
both aimed at enhancing atomic write support for namespaces.
hw/nvme: enable ns atomic writes
This patc
On 6/2/25 4:38 PM, Pierrick Bouvier wrote:
Fixed commit introduced common dependencies for target libraries. Alas,
it wrongly reused the 'target' variable, which was previously set from
another loop.
Thus, some dependencies were missing depending on order of target list,
as found here [1].
The
On 6/2/25 3:37 PM, Pierrick Bouvier wrote:
On 6/2/25 2:11 PM, Cédric Le Goater wrote:
On 6/2/25 22:53, Nabih Estefan wrote:
Hi Pierrick,
For what it's worth, those files were also breaking on Ubuntu and Debian for me.
I had to explicitly `sudo apt install libfdt-dev` for it to work
again. I do
Fixed commit introduced common dependencies for target libraries. Alas,
it wrongly reused the 'target' variable, which was previously set from
another loop.
Thus, some dependencies were missing depending on order of target list,
as found here [1].
The fix is to use the correct config_base_arch in
On 6/2/25 12:57 PM, Rowan Hart wrote:
This patch adds functionality to enforce the requested QEMU_PLUGIN_CB_
flags level passed when registering a callback function using the
plugins API. Each time a callback is about to be invoked, a thread-local
variable will be updated with the level that call
Add support for the namespace atomic paramters: NAWUN and NAWUN. Namespace
Atomic Compare and Write Unit (NACWU) is not currently supported.
Writes that adhere to the NACWU and NAWUPF parameters are guaranteed to be
atomic.
New NVMe QEMU Paramters (See NVMe Specification for details):
ato
Add support for the namespace atomic boundary paramters: NABO, NABSN, and
NABSPF.
Writes that cross an atomic boundary whose size is less than or equal to values
reported by AWUN/AWUPF are guaranteed to be atomic. If AWUN/AWUPF is set to
zero,
writes that cross an atomic boundary are not guarant
On 6/2/25 4:20 PM, Stefan Hajnoczi wrote:
On Mon, Jun 02, 2025 at 08:26:39AM -0400, Brian wrote:
On 5/28/25 3:09 PM, Stefan Hajnoczi wrote:
io_uring may not be available at runtime due to system policies (e.g.
the io_uring_disabled sysctl) or creation could fail due to file
descriptor resource
On 6/2/25 2:11 PM, Cédric Le Goater wrote:
On 6/2/25 22:53, Nabih Estefan wrote:
Hi Pierrick,
For what it's worth, those files were also breaking on Ubuntu and Debian for me.
I had to explicitly `sudo apt install libfdt-dev` for it to work
again. I don't believe
it was installed at all previous
From: Tanish Desai
This change improves performance by moving the hot path of the
trace_vhost_commit()(or any other trace function) logic to the header file.
Previously, even when the trace event was disabled, the function call chain:-
trace_vhost_commit()(Or any other trace function) →
The following changes since commit 6322b753f798337835e205b6d805356bea582c86:
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu
into staging (2025-06-02 14:52:45 -0400)
are available in the Git repository at:
https://gitlab.com/stefanha/qemu.git tags/tracing-pull-r
On Mon, Jun 2, 2025 at 5:58 PM Michael S. Tsirkin wrote:
>
> On Mon, Jun 02, 2025 at 02:31:19PM -0400, Michael S. Tsirkin wrote:
> > On Mon, Jun 02, 2025 at 02:25:48PM -0400, Stefan Hajnoczi wrote:
> > > On Mon, Jun 2, 2025 at 1:54 PM Michael S. Tsirkin wrote:
> > > >
> > > > On Mon, Jun 02, 2025
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.1 for any
user-visible changes.
signature.asc
Description: PGP signature
On Sun, Jun 01, 2025 at 06:12:29PM +, Tanish Desai wrote:
> inline: move hot paths from .c to .h for better performance
> Moved frequently used hot paths from the .c file to the .h file to enable
> inlining
> and improve performance. This approach is inspired by past QEMU optimizations,
> wher
Applied to my tracing tree, thanks!
https://gitlab.com/stefanha/qemu/-/commit/ffcfb0faaa95fc6ca007f7dd989e390dacf936ca
Stefan
On Sun, Jun 01, 2025 at 06:12:30PM +, Tanish Desai wrote:
> Moved rarely used (cold) code from the header file to the C file to avoid
> unnecessary inlining and reduce binary size.
How much of a binary size reduction do you measure? Most trace events
are only called once, so the difference in
On Mon, Jun 02, 2025 at 08:26:39AM -0400, Brian wrote:
> On 5/28/25 3:09 PM, Stefan Hajnoczi wrote:
> > io_uring may not be available at runtime due to system policies (e.g.
> > the io_uring_disabled sysctl) or creation could fail due to file
> > descriptor resource limits.
> >
> > Handle failure
On Mon, Jun 02, 2025 at 02:31:19PM -0400, Michael S. Tsirkin wrote:
> On Mon, Jun 02, 2025 at 02:25:48PM -0400, Stefan Hajnoczi wrote:
> > On Mon, Jun 2, 2025 at 1:54 PM Michael S. Tsirkin wrote:
> > >
> > > On Mon, Jun 02, 2025 at 12:39:17PM -0400, Stefan Hajnoczi wrote:
> > > > On Sun, Jun 1, 20
@@ -437,6 +437,10 @@ int qemu_plugin_read_register(struct
qemu_plugin_register *reg, GByteArray *buf)
{
g_assert(current_cpu);
+ if (qemu_plugin_get_cb_flags() == QEMU_PLUGIN_CB_NO_REGS) {
+ return -1;
+ }
+
return gdb_read_register(current_cpu, buf, GPOINTER_TO_INT
Allow cold-plug of smmuv3 device to virt if there is no machine
wide legacy smmuv3 or a virtio-iommu is specified.
Device tree support for new smmuv3 dev is limited to the case where
it is associated with the default pcie.0 RC.
Signed-off-by: Shameer Kolothum
---
hw/arm/smmuv3.c | 2 ++
h
On 30.05.25 10:32, Chenyi Qiang wrote:
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") highlighted that subsystems like VFIO may disable RAM block
discard. However, guest_memfd relies on discard operations for page
conversion between private and shared memory, poten
On 6/2/25 22:53, Nabih Estefan wrote:
Hi Pierrick,
For what it's worth, those files were also breaking on Ubuntu and Debian for me.
I had to explicitly `sudo apt install libfdt-dev` for it to work
again. I don't believe
it was installed at all previously, but QEMU was building and working correc
Hi Pierrick,
For what it's worth, those files were also breaking on Ubuntu and Debian for me.
I had to explicitly `sudo apt install libfdt-dev` for it to work
again. I don't believe
it was installed at all previously, but QEMU was building and working correctly
without it being explicitly installe
On 6/2/25 7:46 AM, Shameer Kolothum wrote:
default_bus_bypass_iommu tells us whether the bypass_iommu is set
for the default PCIe root bus. Make sure we check that before adding
the "iommu-map" DT property.
Fixes: 6d7a85483a06 ("hw/arm/virt: Add default_bus_bypass_iommu machine option")
Sugge
On 16.05.2025 13:05, Sairaj Kodilkar wrote:
Fix following two issues in the amd viommu
1. The guest fails to setup the passthrough device when for following setup
because amd iommu enables the no DMA memory region even when guest is
using DMA remapping mode.
-device amd-iommu,intrem
Peter Xu writes:
> I am guessing it was used to be 32bits because of the atomic ops. Now all
> the atomic ops are gone and we're protected by a mutex instead, it's ok we
> can switch to 64 bits.
>
> Reasons to move over:
>
> - Allow further patches to change the unit from ms to us: with postco
From: novafacing
This patch adds functions to the plugins API to allow plugins to read
and write memory via hardware addresses. The functions use the current
address space of the current CPU in order to avoid exposing address
space information to users. A later patch may want to add a function to
This patch series adds several new API functions focused on enabling use
cases around reading and writing guest memory from QEMU plugins. To support
these new APIs, some utility functionality around retrieving information about
address spaces is added as well.
The new qemu_plugin_write_register ut
From: novafacing
This patch adds functions to the plugins API to allow reading and
writing memory via virtual addresses. These functions only permit doing
so on the current CPU, because there is no way to ensure consistency if
plugins are allowed to read or write to other CPUs that aren't current
From: novafacing
This patch exposes the gdb_write_register function from
gdbstub/gdbstub.c via the exec/gdbstub.h header file to support use in
plugins to write register contents.
Signed-off-by: novafacing
Signed-off-by: Rowan Hart
Reviewed-by: Alex Benée
Reviewed-by: Julian Ganz
Reviewed-by
This patch is required to make the insn plugin work after adding
enforcement of QEMU_PLUGIN_CB_ flags in calls to read or write
registers. Previously, these flags were not enforced and the API could
be called from anywhere, but this was not intended as described by the
documentation. Now, the flags
From: novafacing
This patch adds a plugin that implements a simple form of hypercalls
from guest code to the plugin by using the register read API. It accepts
only one hypercall, which writes a magic value to guest memory.
Signed-off-by: novafacing
Signed-off-by: Rowan Hart
---
tests/tcg/Make
From: novafacing
This patch updates the plugin version to gate new APIs and adds notes
describing what has been added.
Signed-off-by: Rowan Hart
---
include/qemu/qemu-plugin.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/include/qemu/qemu-plugin.h b/include/qemu/
This patch adds functionality to enforce the requested QEMU_PLUGIN_CB_
flags level passed when registering a callback function using the
plugins API. Each time a callback is about to be invoked, a thread-local
variable will be updated with the level that callback requested. Then,
called API functio
From: novafacing
This patch adds a plugin that exercises the virtual and hardware memory
read-write API functions added in a previous patch. The plugin takes a
target and patch byte sequence, and will overwrite any instruction
matching the target byte sequence with the patch.
Signed-off-by: nova
From: novafacing
This patch adds a function to the plugins API to allow plugins to write
register contents. It also moves the qemu_plugin_read_register function
so all the register-related functions are grouped together in the file.
Signed-off-by: novafacing
Signed-off-by: Rowan Hart
Reviewed-
1 - 100 of 194 matches
Mail list logo
