From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the commands on non-Windows.
The command will be rejected at QMP dispatch time instead,
avoiding reimplementing rejection
The following changes since commit 23fa74974d8c96bc95cbecc0d4e2d90f984939f6:
Merge tag 'pull-target-arm-20240718' of
https://git.linaro.org/people/pmaydell/qemu-arm into staging (2024-07-19
07:02:17 +1000)
are available in the Git repository at:
https://github.com/kostyanf14/qemu.git tags/
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the commands on Windows.
The command will be rejected at QMP dispatch time instead,
avoiding reimplementing rejection by
From: Daniel P. Berrangé
It is referenced by QGAState already, and it is clearer to declare all
data types at the top of the file, rather than have them mixed with
code later.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Konstantin Kostiuk
Signed-off-by: Daniel P. Berrangé
Reviewed-by: Ma
From: Daniel P. Berrangé
This variable was used to support back compat for the old config
file key name, and became redundant after the following change:
commit a7a2d636ae4549ef0551134d4bf8e084a14431c4
Author: Philippe Mathieu-Daudé
Date: Thu May 30 08:36:43 2024 +0200
qga: Remove
From: Daniel P. Berrangé
Rather than creating stubs for every comamnd that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the network interface command on
POSIX platforms lacking getifaddrs().
The command will be rejected at QMP dispatch time
From: Dehan Meng
The Route information of the Linux VM needs to be used
by administrators and users when debugging network problems
and troubleshooting.
Signed-off-by: Dehan Meng
Reviewed-by: Konstantin Kostiuk
Message-ID: <20240613092802.346246-2-dem...@redhat.com>
Signed-off-by: Konstantin K
From: Daniel P. Berrangé
The qmp_guest_{fstrim, get_fsinfo, get_disks} command impls in
commands-posix.c are surrounded by '#ifdef __linux__' so should
instead live in commands-linux.c
Reviewed-by: Manos Pitsidianakis
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Konstantin Kostiuk
Signed-
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the schema to fully
exclude generation of the filesystem trimming commands on POSIX
platforms lacking required APIs.
The command will be rejected at QMP dispatch time i
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the filesystem trimming commands
on POSIX platforms lacking required APIs.
The command will be rejected at QMP dispatch t
From: Daniel P. Berrangé
Allowing the user to set the QGA_CONF environment variable to change
the default configuration file path is very unusual practice, made
more obscure since this ability is not documented.
This introduces the more normal '-c PATH' / '--config=PATH' command
line argument a
From: Thomas Lamprecht
While the `allow-rpcs` option is documented in the CLI options
section, it was missing in the section about the configuration file
syntax.
And while it's mentioned that "the list of keys follows the command line
options", having `block-rpcs` there but not `allow-rpcs` seem
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the schema to fully
exclude generation of the filesystem freezing commands on POSIX
platforms lacking the required APIs.
The command will be rejected at QMP dispatch ti
From: Daniel P. Berrangé
Some commands were blocked based on CONFIG_FSFREEZE, but their
impl had nothing todo with CONFIG_FSFREEZE, and were instead
either Linux-only, or Win+Linux-only.
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QA
From: Daniel P. Berrangé
The fsfreeze commands are already written to report an error if
vss_init() fails. Reporting a more specific error message is more
helpful than a generic "command is disabled" message, which cannot
between an admin config decision and lack of platform support.
Reviewed-by
From: Daniel P. Berrangé
It is confusing having many different pieces of code enabling and
disabling commands, and it is not clear that they all have the same
semantics, especially wrt prioritization of the block/allow lists.
The code attempted to prevent the user from setting both the block
and
From: Zhao Liu
Make ga_wait_child() return boolean and check the returned boolean
in ga_run_command() instead of dereferencing @errp.
Cc: Michael Roth
Cc: Konstantin Kostiuk
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Zhao Liu
Reviewed-by: Konstantin Kostiuk
Message-ID: <202407161623
From: Daniel P. Berrangé
The qmp_guest_{set,get}_{memory_blocks,block_info} command impls in
commands-posix.c are surrounded by '#ifdef __linux__' so should
instead live in commands-linux.c
This also removes a "#ifdef CONFIG_LINUX" that was nested inside
a "#ifdef __linux__".
Reviewed-by: Phili
From: Daniel P. Berrangé
The qmp_guest_{diskstats,cpustats} command impls in
commands-posix.c are surrounded by '#ifdef __linux__' so should
instead live in commands-linux.c
This also removes a "#ifdef CONFIG_LINUX" that was nested inside
a "#ifdef __linux__".
Reviewed-by: Philippe Mathieu-Daud
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the commands on other UNIX.
The command will be rejected at QMP dispatch time instead,
avoiding reimplementing rejection
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the get-users command on POSIX
platforms lacking required APIs.
The command will be rejected at QMP dispatch time instead
From: Daniel P. Berrangé
Rather than creating stubs for every command that just return
QERR_UNSUPPORTED, use 'if' conditions in the QAPI schema to
fully exclude generation of the commands on non-Linux POSIX
platforms
The command will be rejected at QMP dispatch time instead,
avoiding reimplement
From: Daniel P. Berrangé
Defining these at the meson level allows them to be used a conditional
tests in the QAPI schemas.
Signed-off-by: Daniel P. Berrangé
Reviewed-by: Konstantin Kostiuk
Reviewed-by: Philippe Mathieu-Daudé
Message-ID: <20240712132459.3974109-8-berra...@redhat.com>
Signed-of
>-Original Message-
>From: Cédric Le Goater
>Subject: Re: [PATCH v6 5/9] vfio/iommufd: Probe and request hwpt dirty
>tracking capability
>
>On 7/23/24 08:13, Joao Martins wrote:
>> On 23/07/2024 06:11, Duan, Zhenzhong wrote:
>>>
>>>
-Original Message-
From: Joao Martins
From: Daniel P. Berrangé
The qmp_guest_set_vcpus and qmp_guest_get_vcpus command impls in
commands-posix.c are surrounded by '#ifdef __linux__' so should
instead live in commands-linux.c
Reviewed-by: Manos Pitsidianakis
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Konstantin Kostiuk
Signe
From: Daniel P. Berrangé
This command has never existed in tree, since it was renamed to
guest-get-memory-block-info before being merged.
Reviewed-by: Manos Pitsidianakis
Reviewed-by: Konstantin Kostiuk
Signed-off-by: Daniel P. Berrangé
Reviewed-by: Philippe Mathieu-Daudé
Message-ID: <202407
On 7/19/24 14:04, Joao Martins wrote:
> In preparation to skip initialization of the HostIOMMUDevice for mdev,
> extract the checks that validate if a device is an mdev into helpers.
>
> A vfio_device_is_mdev() is created, and subsystems consult VFIODevice::mdev
> to check if it's mdev or not.
>
From: Daniel P. Berrangé
The qmp_guest_suspend_{disk,ram,hybrid} command impls in
commands-posix.c are surrounded by '#ifdef __linux__' so should
instead live in commands-linux.c
Reviewed-by: Manos Pitsidianakis
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Konstantin Kostiuk
Signed-off-by
Reviewed-by: Clément Mathieu--Drif
On 18/07/2024 10:16, Zhenzhong Duan wrote:
> Caution: External email. Do not open attachments or click links, unless this
> email comes from a known sender and you know the content is safe.
>
>
> From: Yu Zhang
>
> Spec revision 3.0 or above defines more detai
On 19/07/2024 05:39, Duan, Zhenzhong wrote:
> Caution: External email. Do not open attachments or click links, unless this
> email comes from a known sender and you know the content is safe.
>
>
>> -Original Message-
>> From: Duan, Zhenzhong]
>> Subject: RE: [PATCH v1 03/17] intel_iommu:
Reviewed-by: Clément Mathieu--Drif
On 18/07/2024 10:16, Zhenzhong Duan wrote:
> Caution: External email. Do not open attachments or click links, unless this
> email comes from a known sender and you know the content is safe.
>
>
> According to spec, Page-Selective-within-Domain Invalidation (11b
On 23/07/2024 08:24, Philippe Mathieu-Daudé wrote:
> Hi Clément,
>
> On 17/7/24 14:45, Clément Léger wrote:
>> Since commit 03e471c41d8b ("qemu_init: increase NOFILE soft limit on
>> POSIX"), the maximum number of file descriptors that can be opened are
>> raised to nofile.rlim_max. On recent d
On 7/22/24 23:13, Joao Martins wrote:
> There's generally two modes of operation for IOMMUFD:
>
> 1) The simple user API which intends to perform relatively simple things
> with IOMMUs e.g. DPDK. The process generally creates an IOAS and attaches
> to VFIO and mainly performs IOAS_MAP and UNMAP.
On 7/22/24 23:13, Joao Martins wrote:
> Remove caps::aw_bits which requires the bcontainer::iova_ranges being
> initialized after device is actually attached. Instead defer that to
> .get_cap() and call vfio_device_get_aw_bits() directly.
>
> This is in preparation for HostIOMMUDevice::realize()
On 7/22/24 23:13, Joao Martins wrote:
> Store the value of @caps returned by iommufd_backend_get_device_info()
> in a new field HostIOMMUDeviceCaps::hw_caps. Right now the only value is
> whether device IOMMU supports dirty tracking (IOMMU_HW_CAP_DIRTY_TRACKING).
>
> This is in preparation for H
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
> Move the HostIOMMUDevice::realize() to be invoked during the attach of the
> device
> before we allocate IOMMUFD hardware pagetable objects (HWPT). This allows the
> use
> of the hw_caps obtained by IOMMU_GET_HW_INFO that essentially tell if the
Hi
On Wed, Jul 17, 2024 at 4:48 PM Clément Léger wrote:
> Since commit 03e471c41d8b ("qemu_init: increase NOFILE soft limit on
> POSIX"), the maximum number of file descriptors that can be opened are
> raised to nofile.rlim_max. On recent debian distro, this yield a maximum
> of 1073741816 file
On 7/23/24 09:38, Eric Auger wrote:
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
Move the HostIOMMUDevice::realize() to be invoked during the attach of the
device
before we allocate IOMMUFD hardware pagetable objects (HWPT). This allows the
use
of the hw_caps obtained by IOMMU_GET_HW_INFO t
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
> In preparation to using the dirty tracking UAPI, probe whether the IOMMU
> supports dirty tracking. This is done via the data stored in
> hiod::caps::hw_caps initialized from GET_HW_INFO.
>
> Qemu doesn't know if VF dirty tracking is supported when
On 23/07/2024 08:38, Eric Auger wrote:
> Hi Joao,
>
> On 7/22/24 23:13, Joao Martins wrote:
>> Move the HostIOMMUDevice::realize() to be invoked during the attach of the
>> device
>> before we allocate IOMMUFD hardware pagetable objects (HWPT). This allows
>> the use
>> of the hw_caps obtained b
On Tue, Jul 23, 2024 at 09:16:15AM +0200, Clément Léger wrote:
>
>
> On 23/07/2024 08:24, Philippe Mathieu-Daudé wrote:
> > Hi Clément,
> >
> > On 17/7/24 14:45, Clément Léger wrote:
> >> Since commit 03e471c41d8b ("qemu_init: increase NOFILE soft limit on
> >> POSIX"), the maximum number of fil
On 7/23/24 09:44, Cédric Le Goater wrote:
> On 7/23/24 09:38, Eric Auger wrote:
>> Hi Joao,
>>
>> On 7/22/24 23:13, Joao Martins wrote:
>>> Move the HostIOMMUDevice::realize() to be invoked during the attach
>>> of the device
>>> before we allocate IOMMUFD hardware pagetable objects (HWPT). This
On 7/23/24 09:53, Joao Martins wrote:
On 23/07/2024 08:38, Eric Auger wrote:
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
Move the HostIOMMUDevice::realize() to be invoked during the attach of the
device
before we allocate IOMMUFD hardware pagetable objects (HWPT). This allows the
use
of t
On 23/07/2024 08:50, Eric Auger wrote:
> Hi Joao,
>
> On 7/22/24 23:13, Joao Martins wrote:
>> In preparation to using the dirty tracking UAPI, probe whether the IOMMU
>> supports dirty tracking. This is done via the data stored in
>> hiod::caps::hw_caps initialized from GET_HW_INFO.
>>
>> Qemu do
On 2024/7/23 10:40, Yee Li wrote:
When dmar_readq or devmem2 read the DW of IQA always 0UL because
"& VTD_IQA_QS". So, try to fix it.
case:
after vtd_mem_write
IQA val: 0x100206801
after vtd_mem_read
IQA val: 0x100206001
Signed-off-by: yeeli
I think you may need to capitalize the first char
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
> ioctl(iommufd, IOMMU_HWPT_SET_DIRTY_TRACKING, arg) is the UAPI that
> enables or disables dirty page tracking. The ioctl is used if the hwpt
> has been created with dirty tracking supported domain (stored in
> hwpt::flags) and it is called on the wh
On 23/07/2024 08:55, Eric Auger wrote:
>
>
> On 7/23/24 09:44, Cédric Le Goater wrote:
>> On 7/23/24 09:38, Eric Auger wrote:
>>> Hi Joao,
>>>
>>> On 7/22/24 23:13, Joao Martins wrote:
Move the HostIOMMUDevice::realize() to be invoked during the attach
of the device
before we alloc
On 7/23/24 10:05, Joao Martins wrote:
On 23/07/2024 08:55, Eric Auger wrote:
On 7/23/24 09:44, Cédric Le Goater wrote:
On 7/23/24 09:38, Eric Auger wrote:
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
Move the HostIOMMUDevice::realize() to be invoked during the attach
of the device
before
On 7/23/24 10:00, Joao Martins wrote:
> On 23/07/2024 08:50, Eric Auger wrote:
>> Hi Joao,
>>
>> On 7/22/24 23:13, Joao Martins wrote:
>>> In preparation to using the dirty tracking UAPI, probe whether the IOMMU
>>> supports dirty tracking. This is done via the data stored in
>>> hiod::caps::hw_
On 7/23/24 10:05, Joao Martins wrote:
> On 23/07/2024 08:55, Eric Auger wrote:
>>
>> On 7/23/24 09:44, Cédric Le Goater wrote:
>>> On 7/23/24 09:38, Eric Auger wrote:
Hi Joao,
On 7/22/24 23:13, Joao Martins wrote:
> Move the HostIOMMUDevice::realize() to be invoked during the
On 23/07/2024 09:03, Eric Auger wrote:
> Hi Joao,
>
> On 7/22/24 23:13, Joao Martins wrote:
>> ioctl(iommufd, IOMMU_HWPT_SET_DIRTY_TRACKING, arg) is the UAPI that
>> enables or disables dirty page tracking. The ioctl is used if the hwpt
>> has been created with dirty tracking supported domain (sto
On 7/23/24 10:14, Joao Martins wrote:
> On 23/07/2024 09:03, Eric Auger wrote:
>> Hi Joao,
>>
>> On 7/22/24 23:13, Joao Martins wrote:
>>> ioctl(iommufd, IOMMU_HWPT_SET_DIRTY_TRACKING, arg) is the UAPI that
>>> enables or disables dirty page tracking. The ioctl is used if the hwpt
>>> has been c
On 23/07/2024 09:09, Eric Auger wrote:
>
>
> On 7/23/24 10:00, Joao Martins wrote:
>> On 23/07/2024 08:50, Eric Auger wrote:
>>> Hi Joao,
>>>
>>> On 7/22/24 23:13, Joao Martins wrote:
In preparation to using the dirty tracking UAPI, probe whether the IOMMU
supports dirty tracking. This
>-Original Message-
>From: Joao Martins
>Subject: Re: [PATCH v6 4/9] vfio/{iommufd,container}: Invoke
>HostIOMMUDevice::realize() during attach_device()
>
>On 23/07/2024 08:55, Eric Auger wrote:
>>
>>
>> On 7/23/24 09:44, Cédric Le Goater wrote:
>>> On 7/23/24 09:38, Eric Auger wrote:
>>
On 7/22/24 23:13, Joao Martins wrote:
> By default VFIO migration is set to auto, which will support live
> migration if the migration capability is set *and* also dirty page
> tracking is supported.
>
> For testing purposes one can force enable without dirty page tracking
> via enable-migration
Hi Manos,
(This patch contains too many codes so that mail list rejects to display
it at https://lore.kernel.org/qemu-devel)
Please correct me if I'm wrong...
Is the reason for not using git submodules here because v5 abandoned
compilation through Cargo, so it’s necessary to add meson.build to t
On Mon, Jul 22, 2024 at 02:43:35PM +0300, Manos Pitsidianakis wrote:
> Date: Mon, 22 Jul 2024 14:43:35 +0300
> From: Manos Pitsidianakis
> Subject: [RFC PATCH v5 5/8] .gitattributes: add Rust diff and merge
> attributes
> X-Mailer: git-send-email 2.44.0
>
> Set rust source code to diff=rust (bui
On 7/23/24 10:20, Duan, Zhenzhong wrote:
>
>> -Original Message-
>> From: Joao Martins
>> Subject: Re: [PATCH v6 4/9] vfio/{iommufd,container}: Invoke
>> HostIOMMUDevice::realize() during attach_device()
>>
>> On 23/07/2024 08:55, Eric Auger wrote:
>>>
>>> On 7/23/24 09:44, Cédric Le Go
On 23/07/2024 09:24, Eric Auger wrote:
>
>
> On 7/23/24 10:20, Duan, Zhenzhong wrote:
>>
>>> -Original Message-
>>> From: Joao Martins
>>> Subject: Re: [PATCH v6 4/9] vfio/{iommufd,container}: Invoke
>>> HostIOMMUDevice::realize() during attach_device()
>>>
>>> On 23/07/2024 08:55, Eric
On 7/22/24 23:13, Joao Martins wrote:
> The property 'x-pre-copy-dirty-page-tracking' allows disabling the whole
> tracking of VF pre-copy phase of dirty page tracking, though it means
> that it will only be used at the start of the switchover phase.
>
> Add an option that disables the VF dirty
On 7/22/24 21:43, Manos Pitsidianakis wrote:
From: Alex Bennée
For rust development we need cargo, rustc and bindgen in our various
development environments. Update the libvirt-ci project to (!495) and
regenerate the containers and other dependency lists.
The cover letter for v5 says use of ca
On 7/22/24 21:43, Manos Pitsidianakis wrote:
Add job that builds with rust support enabled on debian.
Signed-off-by: Manos Pitsidianakis
---
.gitlab-ci.d/buildtest.yml | 11 +++
1 file changed, 11 insertions(+)
Reviewed-by: Richard Henderson
r~
On 7/22/24 23:13, Joao Martins wrote:
This small series adds support for IOMMU dirty tracking support via the
IOMMUFD backend. The hardware capability is available on most recent x86
hardware (and these SMMUv3 in upcoming v6.11). The series is divided
organized as follows:
* Patches 1 - 7: IOMMU
On Mon, Jul 22, 2024 at 02:43:33PM +0300, Manos Pitsidianakis wrote:
> Add job that builds with rust support enabled on debian.
>
> Signed-off-by: Manos Pitsidianakis
> ---
> .gitlab-ci.d/buildtest.yml | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/.gitlab-ci.d/buildtest.
On 18/7/24 15:32, Philippe Mathieu-Daudé wrote:
From: Bibo Mao
In preparation to extract common IPI code in few commits,
extract loongson_ipi_common_finalize().
Signed-off-by: Bibo Mao
[PMD: Extracted from bigger commit, added commit description]
Co-Developed-by: Philippe Mathieu-Daudé
Signe
On 23/07/2024 09:31, Eric Auger wrote:
>
>
> On 7/22/24 23:13, Joao Martins wrote:
>> The property 'x-pre-copy-dirty-page-tracking' allows disabling the whole
>> tracking of VF pre-copy phase of dirty page tracking, though it means
>> that it will only be used at the start of the switchover phase
ach(map, walk_map, state);
+xkb_state_unref(state);
+xkb_keymap_unref(map);
/* add quirks */
fprintf(outfile,
---
base-commit: a87a7c449e532130d4fa8faa391ff7e1f04ed660
change-id: 20240723-unref-d62e2b8338f4
Best regards,
--
Akihiko Odaki
>-Original Message-
>From: CLEMENT MATHIEU--DRIF
>Subject: Re: [PATCH v1 03/17] intel_iommu: Add a placeholder variable for
>scalable modern mode
>
>
>
>On 19/07/2024 05:39, Duan, Zhenzhong wrote:
>> Caution: External email. Do not open attachments or click links, unless this
>email come
On 23/07/2024 09:35, Cédric Le Goater wrote:
> On 7/22/24 23:13, Joao Martins wrote:
>> This small series adds support for IOMMU dirty tracking support via the
>> IOMMUFD backend. The hardware capability is available on most recent x86
>> hardware (and these SMMUv3 in upcoming v6.11). The series is
On 7/23/24 10:56, Joao Martins wrote:
On 23/07/2024 09:35, Cédric Le Goater wrote:
On 7/22/24 23:13, Joao Martins wrote:
This small series adds support for IOMMU dirty tracking support via the
IOMMUFD backend. The hardware capability is available on most recent x86
hardware (and these SMMUv3 in
On 22/07/2024 16.50, Collin Walling wrote:
On 7/20/24 1:33 AM, Markus Armbruster wrote:
Collin Walling writes:
Currently, there is no way to execute the query-cpu-model-expansion
command to retrieve a comprehenisve list of deprecated properties, as
the result is dependent per-model. To enable
Hi,
The KVM/QEMU community call is at:
https://meet.jit.si/kvmcallmeeting
@
23/07/2024 14:00 UTC
Unfortunately I won't be able to make it to chair but everyone on the
invite list should be able to start the call and edit the notes (see
link in the invite).
Are there any agenda items for the s
在 2024/7/23 下午4:41, Philippe Mathieu-Daudé 写道:
On 18/7/24 15:32, Philippe Mathieu-Daudé wrote:
From: Bibo Mao
In preparation to extract common IPI code in few commits,
extract loongson_ipi_common_finalize().
Signed-off-by: Bibo Mao
[PMD: Extracted from bigger commit, added commit description
It's possible for AT_EXECFD to end up with a valid value of 0. Check
errno when using qemu_getauxval instead of return value to handle this
case.
Not handling this case leads to a confusing condition where the
executable ends up as fd 0, i.e. stdin.
Signed-off-by: Vivian Wang
Reviewed-by: Richar
Found when trying to build coreutils under linux-user as binfmt_misc
interpreter with "open-binary" flag.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2448
Changes since v1 [1]:
- Removed old glibc check in patch 1
- Added Reviewed-by
[1]: https://lore.kernel.org/qemu-devel/2024072109
Sometimes zero is a valid value for getauxval (e.g. AT_EXECFD). Make
sure that we can distinguish between a valid zero value and a not found
entry by setting errno.
Assumes that getauxval from sys/auxv.h sets errno correctly.
Signed-off-by: Vivian Wang
---
util/getauxval.c | 6 +-
1 file ch
On 2024/07/23 18:09, Phil Dennis-Jordan wrote:
This can certainly be useful in various situations! However, wholesale
enabling get-task-allow will enable other processes on the system to
inject code, connect a debugger, etc. to the Qemu process. Normally,
this is only something you'd enable for
On Tue, 23 Jul 2024 11:39, "Daniel P. Berrangé" wrote:
On Mon, Jul 22, 2024 at 02:43:33PM +0300, Manos Pitsidianakis wrote:
Add job that builds with rust support enabled on debian.
Signed-off-by: Manos Pitsidianakis
---
.gitlab-ci.d/buildtest.yml | 11 +++
1 file changed, 11 insertio
On Tue, Jul 23, 2024 at 01:06:20PM +0300, Manos Pitsidianakis wrote:
> On Tue, 23 Jul 2024 11:39, "Daniel P. Berrangé" wrote:
> > On Mon, Jul 22, 2024 at 02:43:33PM +0300, Manos Pitsidianakis wrote:
> > > Add job that builds with rust support enabled on debian.
> > >
> > > Signed-off-by: Manos Pi
On 7/23/24 10:42, Joao Martins wrote:
> On 23/07/2024 09:31, Eric Auger wrote:
>>
>> On 7/22/24 23:13, Joao Martins wrote:
>>> The property 'x-pre-copy-dirty-page-tracking' allows disabling the whole
>>> tracking of VF pre-copy phase of dirty page tracking, though it means
>>> that it will only
Hello Richard,
On Tue, 23 Jul 2024 11:31, Richard Henderson
wrote:
On 7/22/24 21:43, Manos Pitsidianakis wrote:
From: Alex Bennée
For rust development we need cargo, rustc and bindgen in our various
development environments. Update the libvirt-ci project to (!495) and
regenerate the containe
On 2024/07/18 2:15, marcandre.lur...@redhat.com wrote:
From: Marc-André Lureau
Hi,
-display dbus clipboard is broken after a client reconnection. The two main
issues are capabilities not renegotiated (and thus guest agent not fully
functional), and qemu clipboard serial not correctly reset.
M
Zhao Liu writes:
> Hi Markus,
>
> On Mon, Jul 22, 2024 at 03:24:24PM +0200, Markus Armbruster wrote:
>> Date: Mon, 22 Jul 2024 15:24:24 +0200
>> From: Markus Armbruster
>> Subject: Re: [PATCH 1/8] hw/core: Make CPU topology enumeration
>> arch-agnostic
>>
>> One little thing...
>>
>> Zhao Liu
On 23/7/24 12:00, gaosong wrote:
在 2024/7/23 下午4:41, Philippe Mathieu-Daudé 写道:
On 18/7/24 15:32, Philippe Mathieu-Daudé wrote:
From: Bibo Mao
In preparation to extract common IPI code in few commits,
extract loongson_ipi_common_finalize().
Signed-off-by: Bibo Mao
[PMD: Extracted from bigge
On Tue, 23 Jul 2024 09:37, Zhao Liu wrote:
Hi Manos,
On Mon, Jul 22, 2024 at 02:43:31PM +0300, Manos Pitsidianakis wrote:
Date: Mon, 22 Jul 2024 14:43:31 +0300
From: Manos Pitsidianakis
Subject: [RFC PATCH v5 1/8] build-sys: Add rust feature option
X-Mailer: git-send-email 2.44.0
Add rust fe
On 22.07.24 23:32, Richard Henderson wrote:
On 7/22/24 10:16, Michael S. Tsirkin wrote:
A couple of fixes are outstanding, will merge later.
The following changes since commit
a87a7c449e532130d4fa8faa391ff7e1f04ed660:
Merge tag 'pull-loongarch-20240719'
ofhttps://gitlab.com/gaosong/qemu
On 19/7/24 15:04, Philippe Mathieu-Daudé wrote:
On 19/7/24 14:56, Jiaxun Yang wrote:
在2024年7月18日七月 下午9:32，Philippe Mathieu-Daudé写道：
Since v4:
- Fix build failure due to rebase (Song)
- Loongarch -> LoongArch (Song)
- Added Song's tags
Since v3:
- Use DEFINE_TYPES() macro (unreviewed patch #1
Zhao Liu writes:
> As the comment in qapi/error, dereferencing @errp requires
Suggest "According to the comment in qapi/error.h".
> ERRP_GUARD():
>
> * = Why, when and how to use ERRP_GUARD() =
> *
> * Without ERRP_GUARD(), use of the @errp parameter is restricted:
> * - It must not be derefere
On Tue, 23 Jul 2024 11:37, Zhao Liu wrote:
Hi Manos,
(This patch contains too many codes so that mail list rejects to display
it at https://lore.kernel.org/qemu-devel)
Please correct me if I'm wrong...
Is the reason for not using git submodules here because v5 abandoned
compilation through Ca
On Tue, 23 Jul 2024 13:11, "Daniel P. Berrangé" wrote:
On Tue, Jul 23, 2024 at 01:06:20PM +0300, Manos Pitsidianakis wrote:
On Tue, 23 Jul 2024 11:39, "Daniel P. Berrangé" wrote:
> On Mon, Jul 22, 2024 at 02:43:33PM +0300, Manos Pitsidianakis wrote:
> > Add job that builds with rust support en
The QSD depends on chardev code, and is built when have_tools is
true. This means conditionalizing chardev trace on have_system
is wrong, we need have_block which is set have_system || have_tools.
This latent bug was historically harmless because only the spice
chardev included tracing, which wasn
On Tue, Jul 23, 2024 at 12:18:48PM +0200, Hanna Czenczek wrote:
> On 22.07.24 23:32, Richard Henderson wrote:
> > On 7/22/24 10:16, Michael S. Tsirkin wrote:
> > > A couple of fixes are outstanding, will merge later.
> > >
> > >
> > > The following changes since commit
> > > a87a7c449e532130d4fa8
From: Zheyu Ma
Currently, if the function fails during the key_len check, the op_code
does not have a proper value, causing virtio_crypto_free_create_session_req
not to free the memory correctly, leading to a memory leak.
By setting the op_code before performing any checks, we ensure that
virtio
From: Gregory Price
Preparation for allowing devices to define their own CCI commands
Signed-off-by: Gregory Price
Link:
https://lore.kernel.org/r/20230906001517.324380-2-gregory.pr...@memverge.com
Signed-off-by: Jonathan Cameron
Message-Id: <20240705123039.963781-2-jonathan.came...@huawei.co
From: Stefano Garzarella
I have recently been working on supporting vhost-user on any POSIX,
so I want to help maintain it.
Cc: Michael S. Tsirkin
Signed-off-by: Stefano Garzarella
Message-Id: <20240704081336.21208-1-sgarz...@redhat.com>
Reviewed-by: Alex Bennée
Reviewed-by: Michael S. Tsirki
From: Davidlohr Bueso
Iterate over the list keeping the output payload size into account,
returning the results from a previous scan media operation. The
scan media operation does not fail prematurely due to device being
out of storage, so this implementation does not deal with the
retry/restart
From: Shiju Jose
CXL spec 3.1 section 8.2.9.9.11.1 describes the device patrol scrub control
feature. The device patrol scrub proactively locates and makes corrections
to errors in regular cycle. The patrol scrub control allows the request to
configure patrol scrub input configurations.
The patr
From: Davidlohr Bueso
Implement transfer and activate functionality per 3.1 spec for
supporting update metadata (no actual buffers). Transfer times
are arbitrarily set to ten and two seconds for full and part
transfers, respectively.
cxl update-firmware mem0 -F fw.img
cxl update-firmware mem0
From: Fan Ni
The whole mailbox output payload space is already zeroed after copying
out the input payload, which happens before processing the specific mailbox
command:
https://elixir.bootlin.com/qemu/v8.2.1/source/hw/cxl/cxl-device-utils.c#L204
Signed-off-by: Fan Ni
Link: https://lore.kernel.o
From: Yi Liu
Signed-off-by: Yi Liu
Message-Id: <20240708032112.796339-1-yi.l@intel.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b7e9ced3e8..8ad64ff76b 100644
--- a
1 - 100 of 370 matches
Mail list logo
