On 26/02/2024 23.48, Alex Bennée wrote:
The old links are dead so even if we have the ISO cached we can't
finish the install. Update to the current stable and tweak the install
strings.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2192
Signed-off-by: Alex Bennée
---
tests/vm/openbs
On 2024/02/27 1:56, Alex Bennée wrote:
We can only request a list of registers once the vCPU has been
initialised so the user needs to use either call the get function on
vCPU initialisation or during the translation phase.
We don't expose the reg number to the plugin instead hiding it behind
an
On Thu, Feb 22, 2024 at 05:56:27PM +0200, Avihai Horon wrote:
> Currently, migration code serializes device data sending during pre-copy
> iterative phase. As noted in the code comment, this is done to prevent
> faster changing device from sending its data over and over.
Frankly speaking I don't u
On Thu Feb 22, 2024 at 10:20 PM AEST, BALATON Zoltan wrote:
> On Thu, 22 Feb 2024, Philippe Mathieu-Daudé wrote:
> > On 22/2/24 12:33, BALATON Zoltan wrote:
> >> After previous changes the hypercall handling in 7xx and 74xx
> >> exception handlers can be folded into one if statement to simpilfy
> >
On Thu Feb 22, 2024 at 9:33 PM AEST, BALATON Zoltan wrote:
> After previous changes the hypercall handling in 7xx and 74xx
> exception handlers can be folded into one if statement to simpilfy
> this code. Also add "unlikely" to mark the less freqiently used branch
> for the compiler.
>
> Signed-off
On Thu Feb 22, 2024 at 9:33 PM AEST, BALATON Zoltan wrote:
> Most exceptions are raised with nip pointing to the faulting
> instruction but the sc instruction generating a syscall exception
> leaves nip pointing to next instruction. Fix gen_sc to not use
> gen_exception_err() which sets nip back bu
On Tue, Feb 20, 2024 at 04:06:22PM +, Peter Maydell wrote:
> Date: Tue, 20 Feb 2024 16:06:22 +
> From: Peter Maydell
> Subject: [PATCH 10/10] docs/devel/reset: Update to discuss system reset
> X-Mailer: git-send-email 2.34.1
>
> Now that system reset uses a three-phase-reset, update the r
On Tue, Feb 20, 2024 at 04:06:21PM +, Peter Maydell wrote:
> Date: Tue, 20 Feb 2024 16:06:21 +
> From: Peter Maydell
> Subject: [PATCH 09/10] hw/core/machine: Use qemu_register_resettable for
> sysbus reset
> X-Mailer: git-send-email 2.34.1
>
> Move the reset of the sysbus (and thus all
On Tue, Feb 20, 2024 at 04:06:20PM +, Peter Maydell wrote:
> Date: Tue, 20 Feb 2024 16:06:20 +
> From: Peter Maydell
> Subject: [PATCH 08/10] hw/core/reset: Implement qemu_register_reset via
> qemu_register_resettable
> X-Mailer: git-send-email 2.34.1
>
> Reimplement qemu_register_reset(
On Tue, Feb 20, 2024 at 04:06:19PM +, Peter Maydell wrote:
> Date: Tue, 20 Feb 2024 16:06:19 +
> From: Peter Maydell
> Subject: [PATCH 07/10] hw/core/reset: Add qemu_{register,
> unregister}_resettable()
> X-Mailer: git-send-email 2.34.1
>
> Implement new functions qemu_register_resettab
This patch adds loopback for sent characters, sent BREAK,
and modem-control signals.
Loopback of send and modem-control is often used for uart
self tests in real hardware but missing from current pl011
model, resulting in self-test failures when running in QEMU.
This implementation matches what i
Hi Peter and Philippe!
Thank you for the review and feedback!
OK, I'll fix PCIE-relarted comments and the overlapping issue
BR,
Sergey Kambalin
Software Developer,
Auriga Inc.
От: Peter Maydell
Отправлено: 26 февраля 2024 г. 10:41:31
Кому: Philippe Mathieu-
On Mon, Feb 26, 2024 at 05:08:05PM -0500, Steven Sistare wrote:
> On 2/26/2024 3:21 PM, Steven Sistare wrote:
> > On 2/26/2024 4:01 AM, Peter Xu wrote:
> >> On Mon, Feb 26, 2024 at 09:49:46AM +0100, Cédric Le Goater wrote:
> >>> Go ahead. It will help me for the changes I am doing on error reportin
>-Original Message-
>From: Joao Martins
>Subject: Re: [PATCH RFCv2 1/8] backends/iommufd: Introduce helper
>function iommufd_device_get_hw_capabilities()
>
>On 26/02/2024 07:29, Duan, Zhenzhong wrote:
>> Hi Joao,
>>
>>> -Original Message-
>>> From: Joao Martins
>>> Subject: [PAT
On Mon, Feb 26, 2024 at 07:52:20PM -0300, Fabiano Rosas wrote:
> Peter Xu writes:
>
> > On Tue, Feb 20, 2024 at 07:41:26PM -0300, Fabiano Rosas wrote:
> >> The fixed-ram migration can be performed live or non-live, but it is
> >> always asynchronous, i.e. the source machine and the destination
>
Hi Eric,
>-Original Message-
>From: Eric Auger
>Subject: [PATCH v5 3/3] virtio-iommu: Change the default granule to the
>host page size
>
>We used to set the default granule to 4KB but with VFIO assignment
>it makes more sense to use the actual host page size.
>
>Indeed when hotplugging a
>-Original Message-
>From: Eric Auger
>Subject: [PATCH v5 1/3] qdev: Add a granule_mode property
>
>Introduce a new enum type property allowing to set an
>IOMMU granule. Values are 4k, 8k, 16k, 64k and host.
>This latter indicates the vIOMMU granule will match
>the host page size.
>
>A s
>-Original Message-
>From: Eric Auger
>Subject: [PATCH v5 2/3] virtio-iommu: Add a granule property
>
>This allows to choose which granule will be used by
>default by the virtio-iommu. Current page size mask
>default is qemu_target_page_mask so this translates
>into a 4K granule.
>
>Sig
On Tue, Feb 20, 2024 at 04:06:18PM +, Peter Maydell wrote:
> Date: Tue, 20 Feb 2024 16:06:18 +
> From: Peter Maydell
> Subject: [PATCH 06/10] hw/core: Add ResetContainer which holds objects
> implementing Resettable
> X-Mailer: git-send-email 2.34.1
>
> Implement a ResetContainer. This
On 2/22/2024 23:56, Avihai Horon wrote:
> Currently, migration code serializes device data sending during pre-copy
> iterative phase. As noted in the code comment, this is done to prevent
> faster changing device from sending its data over and over.
>
> However, with switchover-ack capability enab
>-Original Message-
>From: Joao Martins
>Subject: Re: [PATCH rfcv2 18/18] intel_iommu: Block migration if cap is
>updated
>
>On 01/02/2024 07:28, Zhenzhong Duan wrote:
>> When there is VFIO device and vIOMMU cap/ecap is updated based on
>host
>> IOMMU cap/ecap, migration should be blocke
This patch adds migration test support for loongarch64. The test code
comes from aarch64 mostly, only that it booted as bios in qemu since
kernel requires elf format and bios uses binary format.
In addition to providing the binary, this patch also includes the source
code and the build script in t
Migration test case is added for loongarch64 here. Since compat machine
type is required for migration test case, also compat machine qemu 9.0
is added for loongarch virt machine.
Migration test case passes to run in both tcg and kvm mode with the
patch.
---
Change in v2:
1. Keep the default me
Since migration test case requires compat machine type support,
compat machine is added for qemu 9.0 here.
Signed-off-by: Bibo Mao
---
hw/loongarch/virt.c | 60 +++--
1 file changed, 47 insertions(+), 13 deletions(-)
diff --git a/hw/loongarch/virt.c b/hw/
On LoongArch system, there is only virt machine type now, name
LOONGARCH_MACHINE is confused, rename it with VIRT_MACHINE. Machine name
about Other real hw boards can be added in future.
Signed-off-by: Bibo Mao
---
hw/loongarch/acpi-build.c | 8
hw/loongarch/virt.c | 19 +
The minimum memory size for LoongArch UEFI bios is 256M, also some
test cases such as migration and qos use 256M memory by default.
Here set minimum memory size for Loongarch VirtMachine with 256M rather
than 1G, so that test cases with 256M memory can pass to run.
Signed-off-by: Bibo Mao
---
h
Rename LoongArchMachineState with VirtMachineState, and change variable
name LoongArchMachineState *lams with VirtMachineState *vms, and rename
function loongarch_xxx() with virt_xxx() also.
Signed-off-by: Bibo Mao
---
hw/loongarch/acpi-build.c | 80 +-
hw/loongarch/fw_cfg.c |
Hi Alistair,
> -Original Message-
> From: Alistair Francis
> Sent: Tuesday, February 27, 2024 8:02 AM
> To: Alvin Che-Chia Chang(張哲嘉)
> Cc: qemu-ri...@nongnu.org; qemu-devel@nongnu.org;
> alistair.fran...@wdc.com; bin.m...@windriver.com; liwei1...@gmail.com;
> dbarb...@ventanamicro.com;
According to RISC-V Debug specification version 0.13 [1] (also applied
to version 1.0 [2] but it has not been ratified yet), there are several
common matching conditions before firing a trigger, including the
enabled privilege levels of the trigger.
This commit adds trigger_common_match() to prepa
We have implemented trigger_common_match(), which checks if the enabled
privilege levels of the trigger match CPU's current privilege level.
Remove the related code in riscv_cpu_debug_check_watchpoint() and invoke
trigger_common_match() to check the privilege levels of the type 2 and
type 6 trigger
According to RISC-V Debug specification ratified version 0.13 [1]
(also applied to version 1.0 [2] but it has not been ratified yet), the
enabled privilege levels of the trigger is common match conditions for
all the types of the trigger.
This series modularize the code for checking the privilege
We have implemented trigger_common_match(), which checks if the enabled
privilege levels of the trigger match CPU's current privilege level. We
can invoke trigger_common_match() to check the privilege levels of the
type 3 triggers.
Signed-off-by: Alvin Chang
---
target/riscv/debug.c | 2 +-
1 fi
We have implemented trigger_common_match(), which checks if the enabled
privilege levels of the trigger match CPU's current privilege level.
Remove the related code in riscv_cpu_debug_check_breakpoint() and invoke
trigger_common_match() to check the privilege levels of the type 2 and
type 6 trigger
On Mon, Feb 26, 2024 at 06:04:17PM +, Jonathan Cameron wrote:
> On Wed, 21 Feb 2024 10:16:01 -0800
> nifan@gmail.com wrote:
>
> > From: Fan Ni
> >
> > Per CXL spec 3.1, two mailbox commands are implemented:
> > Add Dynamic Capacity Response (Opcode 4802h) 8.2.9.9.9.3, and
> > Release Dyn
On Mon, Feb 26, 2024 at 06:04:17PM +, Jonathan Cameron wrote:
> On Wed, 21 Feb 2024 10:16:01 -0800
> nifan@gmail.com wrote:
>
> > From: Fan Ni
> >
> > Per CXL spec 3.1, two mailbox commands are implemented:
> > Add Dynamic Capacity Response (Opcode 4802h) 8.2.9.9.9.3, and
> > Release Dyn
On Mon, Feb 26, 2024 at 5:10 PM Alvin Chang via wrote:
>
> According to latest RISC-V Debug specification version 1.0 [1], the
The issue here is that we really only support the "debug" spec. That's
the 0.13 version of the spec.
We do also support bits of the 1.0 spec, but those should be changed
On Fri, Feb 23, 2024 at 12:22 PM Alvin Chang via wrote:
>
> We have implemented trigger_common_match(), which checks if the enabled
> privilege levels of the trigger match CPU's current privilege level.
> Remove the related code in riscv_cpu_debug_check_breakpoint() and invoke
> trigger_common_mat
Peter Xu writes:
> On Tue, Feb 20, 2024 at 07:41:26PM -0300, Fabiano Rosas wrote:
>> The fixed-ram migration can be performed live or non-live, but it is
>> always asynchronous, i.e. the source machine and the destination
>> machine are not migrating at the same time. We only need some pieces
>>
Am 26. Februar 2024 11:14:09 UTC schrieb "Philippe Mathieu-Daudé"
:
>Instantiate TYPE_ICH_DMI_PCI_BRIDGE in TYPE_ICH9_SOUTHBRIDGE.
>
>Since the Q35 machine doesn't use it, add the 'd2p-enabled'
>property to disable it.
>
>Signed-off-by: Philippe Mathieu-Daudé
>---
> include/hw/southbridge/ich9
The old links are dead so even if we have the ISO cached we can't
finish the install. Update to the current stable and tweak the install
strings.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2192
Signed-off-by: Alex Bennée
---
tests/vm/openbsd | 9 +
1 file changed, 5 insertio
Am 26. Februar 2024 11:13:59 UTC schrieb "Philippe Mathieu-Daudé"
:
>Since v1 [1]:
>- Rebased on top of Bernhard patches
>- Rename files with 'ich9_' prefix (Bernhard)
>
>Hi,
>
>I have a long standing southbridge QOM rework branches. Since
>Bernhard is actively working on the PIIX, I'll try to
A small number of migration options are accessed by migration clients,
but to see them clients must include all of options.h, which is mostly
for migration core code. migrate_mode() in particular will be needed by
multiple clients.
Refactor the option declarations so clients can see the necessary
On 2/26/2024 3:21 PM, Steven Sistare wrote:
> On 2/26/2024 4:01 AM, Peter Xu wrote:
>> On Mon, Feb 26, 2024 at 09:49:46AM +0100, Cédric Le Goater wrote:
>>> Go ahead. It will help me for the changes I am doing on error reporting
>>> for VFIO migration. I will rebase on top.
>>
>> Thanks for confirm
As reported by Volker [1], commit 6f6ad2b24582 "hw/i386/pc: Confine system
flash handling to pc_sysfw" causes a regression when specifying the property
`-M pflash0` in the PCI PC machines:
qemu-system-x86_64: Property 'pc-q35-9.0-machine.pflash0' not found
Revert the commit for now until a soluti
Specifying the property `-M pflash0` results in a regression:
qemu-system-x86_64: Property 'pc-q35-9.0-machine.pflash0' not found
Revert the change for now until a solution is found.
This reverts commit 6f6ad2b24582593d8feb00434ce2396840666227.
Reported-by: Volker Rümelin
Signed-off-by: Bernha
Commit 6f6ad2b24582 "hw/i386/pc: Confine system flash handling to pc_sysfw"
causes a regression when specifying the property `-M pflash0` in the PCI PC
machines:
qemu-system-x86_64: Property 'pc-q35-9.0-machine.pflash0' not found
In order to revert the commit, the commit below must be reverted fi
On Mon, 26 Feb 2024 at 19:21, Arnaud Minier
wrote:
> > From: "Peter Maydell"
> >> +static const MemoryRegionOps stm32l4x5_rcc_ops = {
> >> +.read = stm32l4x5_rcc_read,
> >> +.write = stm32l4x5_rcc_write,
> >> +.endianness = DEVICE_NATIVE_ENDIAN,
> >> +.valid = {
> >> +.max_
Thank you for the review and for the tips ! It really helps.
I will address the problems you have highlighted and will send a new version
later this week.
Arnaud
- Original Message -
> From: "Peter Maydell"
> To: "Arnaud Minier"
> Cc: "qemu-devel" , "Thomas Huth" ,
> "Laurent Vivier"
Fabiano Rosas writes:
> Peter Xu writes:
>
>> On Tue, Feb 20, 2024 at 07:41:23PM -0300, Fabiano Rosas wrote:
>>> Currently multifd does not need to have knowledge of pages on the
>>> receiving side because all the information needed is within the
>>> packets that come in the stream.
>>>
>>> We'
- Original Message -
> From: "Peter Maydell"
> To: "Arnaud Minier"
> Cc: "qemu-devel" , "Thomas Huth" ,
> "Laurent Vivier" , "Inès
> Varhol" , "Samuel Tardieu"
> , "qemu-arm"
> , "Alistair Francis" , "Paolo
> Bonzini" , "Alistair
> Francis"
> Sent: Friday, February 23, 2024 3:44:59 PM
From: Cédric Le Goater
close_return_path_on_source() retrieves the migration error from the
the QEMUFile '->to_dst_file' to know if a shutdown is required. This
shutdown is required to exit the return-path thread.
Avoid relying on '->to_dst_file' and use migrate_has_error() instead.
(using to_d
These were extracted from:
[PATCH 00/14] migration: Improve error reporting
https://lore.kernel.org/r/20240207133347.1115903-1-...@redhat.com
We're currently relying on the presence of a QEMUFile error in the
to_dst_file to infer whether the return path file (rp_state.from_dst_file)
might be hangi
The return path thread might hang at a blocking system call. Before
joining the thread we might need to issue a shutdown() on the socket
file descriptor to release it. To determine whether the shutdown() is
necessary we look at the QEMUFile error.
Make sure we only clean up the QEMUFile after the
Add myself to maintain multifd zero page checking acceleration function.
Signed-off-by: Hao Xiang
---
MAINTAINERS | 5 +
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 992799171f..4a4f8f24e0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3413,6 +3413,11 @@ F: t
On 27/02/24 1:04 am, Het Gala wrote:
On 26/02/24 6:31 pm, Fabiano Rosas wrote:
Het Gala writes:
On 24/02/24 1:42 am, Fabiano Rosas wrote:
this was the same first approach that I attempted. It won't work because
The final 'migrate' QAPI with channels string would look like
{ "execute": "m
On 2/26/2024 4:01 AM, Peter Xu wrote:
> On Mon, Feb 26, 2024 at 09:49:46AM +0100, Cédric Le Goater wrote:
>> Go ahead. It will help me for the changes I am doing on error reporting
>> for VFIO migration. I will rebase on top.
>
> Thanks for confirming. I queued the migration patches then, but lea
Make sure the decoding of HVX .new is correctly handling this case
Signed-off-by: Taylor Simpson
---
tests/tcg/hexagon/hvx_misc.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/tests/tcg/hexagon/hvx_misc.c b/tests/tcg/hexagon/hvx_misc.c
index b45170acd1..1fe
This data structure is not used
Signed-off-by: Taylor Simpson
---
target/hexagon/opcodes.c| 7
target/hexagon/README | 1 -
target/hexagon/gen_shortcode.py | 63 -
target/hexagon/meson.build | 10 --
4 files changed, 81 deletions(
Check that the value matches opcode_wregs
Signed-off-by: Taylor Simpson
---
target/hexagon/insn.h | 1 +
target/hexagon/decode.c | 3 +++
target/hexagon/gen_trans_funcs.py | 4
3 files changed, 8 insertions(+)
diff --git a/target/hexagon/insn.h b/target/hexagon/insn.h
Signed-off-by: Taylor Simpson
---
target/hexagon/hex_common.py | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/target/hexagon/hex_common.py b/target/hexagon/hex_common.py
index 195620c7ec..4bacef223f 100755
--- a/target/hexagon/hex_common.py
+++ b/target/hexagon
Check that the value matches opcode_reginfo/opcode_wregs
Signed-off-by: Taylor Simpson
---
target/hexagon/insn.h | 1 +
target/hexagon/decode.c | 2 ++
target/hexagon/mmvec/decode_ext_mmvec.c | 2 ++
target/hexagon/gen_trans_funcs.py | 4
4 files chan
The attribinfo data structure is not used
Adjust the command-line arguments to the python scripts
Add hex_common.read_common_files for TCG/helper generation scripts
Signed-off-by: Taylor Simpson
---
target/hexagon/gen_analyze_funcs.py | 21 ++-
target/hexagon/gen_helper_funcs.py
During .new decode, there are several places where strchr is used.
We remove these by generating the values that are needed.
Once we have generated the proper values, we no longer need
op_regs_generated.h.inc. We remove the script that generates it as
well as the code in meson.build
We also remo
Signed-off-by: Taylor Simpson
---
target/hexagon/README | 1 -
target/hexagon/gen_op_regs.py | 125 --
target/hexagon/meson.build| 14 +---
3 files changed, 2 insertions(+), 138 deletions(-)
delete mode 100755 target/hexagon/gen_op_regs.py
diff --g
Signed-off-by: Taylor Simpson
---
target/hexagon/opcodes.h| 4 --
target/hexagon/decode.c | 57 +++--
target/hexagon/mmvec/decode_ext_mmvec.c | 34 +++
target/hexagon/opcodes.c| 28
4 files changed, 13 i
Check that the value matches opcode_reginfo
Signed-off-by: Taylor Simpson
---
target/hexagon/insn.h | 3 ++-
target/hexagon/decode.c | 2 ++
target/hexagon/mmvec/decode_ext_mmvec.c | 2 ++
target/hexagon/gen_trans_funcs.py | 15 ++-
4 files
1. Add zero_pages field in MultiFDPacket_t.
2. Implements the zero page detection and handling on the multifd
threads for non-compression, zlib and zstd compression backends.
3. Added a new value 'multifd' in ZeroPageDetection enumeration.
4. Handle migration QEMU9.0 -> QEMU8.2 compatibility.
5. Ad
v3 update:
* Change "zero" to "zero-pages" and use type size for "zero-bytes".
* Fixed ZeroPageDetection interface description.
* Move zero page unit tests to its own path.
* Removed some asserts.
* Added backward compatibility support for migration 9.0 -> 8.2.
* Removed fields "zero" and "normal"
This change extends the MigrationStatus interface to track zero pages
and zero bytes counter.
Signed-off-by: Hao Xiang
---
migration/migration-hmp-cmds.c | 4
migration/migration.c | 2 ++
qapi/migration.json | 15 ++-
tests/migration/guestpe
1. Add a dedicated handler for MigrationOps::ram_save_target_page in
multifd live migration.
2. Refactor ram_save_target_page_legacy so that the legacy and multifd
handlers don't have internal functions calling into each other.
Signed-off-by: Hao Xiang
---
migration/ram.c | 43 ++
Now that zero page checking is done on the multifd sender threads by
default, we still provide an option for backward compatibility. This
change adds a qtest migration test case to set the zero-page-detection
option to "legacy" and run multifd migration with zero page checking on the
migration main
Set default "zero-page-detection" option to "multifd". Now zero page
checking can be done in the multifd threads and this becomes the
default configuration. We still provide backward compatibility
where zero page checking is done from the migration main thread.
Signed-off-by: Hao Xiang
---
migra
This new parameter controls where the zero page checking is running.
1. If this parameter is set to 'legacy', zero page checking is
done in the migration main thread.
2. If this parameter is set to 'none', zero page checking is disabled.
Signed-off-by: Hao Xiang
---
hw/core/qdev-properties-syste
Peter Maydell writes:
> 'make vm-build-openbsd' has stopped working -- I suspect that this
> line from the logs is probably relevant:
>
> http://cdn.openbsd.org/pub/OpenBSD/7.2/packages/amd64/: no such dir
>
> though we don't eventually fail until much later, in 'make check' with
> gmake
The main problem is that "check-venv" is a .PHONY target will always
evaluate and trigger a full re-build of the VM images. While its
tempting to drop it from the dependencies that does introduce a
breakage on freshly configured builds.
Fortunately we do have the otherwise redundant --force flag f
On Sun, Feb 25, 2024 at 11:19 PM Wang, Lei wrote:
>
> On 2/17/2024 6:39, Hao Xiang wrote:
> > This new parameter controls where the zero page checking is running.
> > 1. If this parameter is set to 'legacy', zero page checking is
> > done in the migration main thread.
> > 2. If this parameter is s
On 26/02/24 6:31 pm, Fabiano Rosas wrote:
Het Gala writes:
On 24/02/24 1:42 am, Fabiano Rosas wrote:
this was the same first approach that I attempted. It won't work because
The final 'migrate' QAPI with channels string would look like
{ "execute": "migrate", "arguments": { "channels": "[ {
Thanks Peter for the review,
- Original Message -
> From: "Peter Maydell"
> To: "Arnaud Minier"
> Cc: "qemu-devel" , "Thomas Huth" , "Laurent Vivier" , "Inès
> Varhol" , "Samuel Tardieu" , "qemu-arm"
> , "Alistair Francis" , "Paolo Bonzini" , "Alistair
> Francis"
> Sent: Friday, Februar
Peter Xu writes:
> On Tue, Feb 20, 2024 at 07:41:23PM -0300, Fabiano Rosas wrote:
>> Currently multifd does not need to have knowledge of pages on the
>> receiving side because all the information needed is within the
>> packets that come in the stream.
>>
>> We're about to add support to fixed-
22.02.2024 00:16, Michael Tokarev wrote:
-static int64_t cvtnum_full(const char *name, const char *value, int64_t min,
- int64_t max)
+static int64_t cvtnum_full(const char *name, const char *value,
+ bool issize, int64_t min, int64_t max)
{
On Mon, Feb 26, 2024 at 05:33:17PM +, Jonathan Cameron wrote:
> On Wed, 21 Feb 2024 10:15:55 -0800
> nifan@gmail.com wrote:
>
> > From: Fan Ni
> >
> > Per cxl spec r3.1, add dynamic capacity region representative based on
> > Table 8-165 and extend the cxl type3 device definition to incl
On 2/25/24 16:22, Jinjie Ruan wrote:
On 2024/2/24 3:03, Richard Henderson wrote:
On 2/23/24 00:32, Jinjie Ruan via wrote:
Add ALLINT MSR (immediate) to decodetree. And the EL0 check is necessary
to ALLINT. Avoid the unconditional write to pc and use raise_exception_ra
to unwind.
Signed-off-b
26.02.2024 17:14, Daniel P. Berrangé :
On Thu, Feb 22, 2024 at 12:15:42AM +0300, Michael Tokarev wrote:
Currently we have:
./qemu-img resize none +10
qemu-img: Could not open 'none': Could not open 'none': No such file or
directory
stop printing the message twice, - local_err already ha
Best Regards,
Konstantin Kostiuk.
On Mon, Feb 26, 2024 at 7:02 PM Andrey Drobyshev <
andrey.drobys...@virtuozzo.com> wrote:
> Since the commit 25b5ff1a86 ("qga: add mountpoint usage info to
> GuestFilesystemInfo") we have 2 values reported in guest-get-fsinfo:
> used = (f_blocks - f_bfree), tota
On 26/2/24 19:11, Eric Auger wrote:
This allows to choose which granule will be used by
default by the virtio-iommu. Current page size mask
default is qemu_target_page_mask so this translates
into a 4K granule.
Signed-off-by: Eric Auger
---
v4 -> v5:
- use -(n * KiB) (Phild)
v3 -> v4:
- granu
On Mon, Feb 26, 2024 at 05:46:39PM +, Alex Bennée wrote:
> There are two problems.
>
> The first is a .PHONY target will always evaluate which triggers a
> full re-build of the VM images. Drop the requirement knowing that this
> introduces a manual step on freshly configure build dirs.
For co
On 24/2/24 13:43, Akihiko Odaki wrote:
Akihiko Odaki (10):
ui/cocoa: Split [-QemuCocoaView handleEventLocked:]
ui/cocoa: Immediately call [-QemuCocoaView handleMouseEvent:buttons:]
ui/cocoa: Release specific mouse buttons
ui/cocoa: Scale with NSView instead of Core Gr
This allows to choose which granule will be used by
default by the virtio-iommu. Current page size mask
default is qemu_target_page_mask so this translates
into a 4K granule.
Signed-off-by: Eric Auger
---
v4 -> v5:
- use -(n * KiB) (Phild)
v3 -> v4:
- granule_mode introduction moved to that pat
We used to set the default granule to 4KB but with VFIO assignment
it makes more sense to use the actual host page size.
Indeed when hotplugging a VFIO device protected by a virtio-iommu
on a 64kB/64kB host/guest config, we current get a qemu crash:
"vfio: DMA mapping failed, unable to continue"
We used to set the default granule to 4kB but with VFIO assignment
it makes more sense to use the actual host page size.
Indeed when hotplugging a VFIO device protected by a virtio-iommu
on a 64kB/64kB host/guest config, we currently get a qemu crash:
"vfio: DMA mapping failed, unable to cont
Introduce a new enum type property allowing to set an
IOMMU granule. Values are 4k, 8k, 16k, 64k and host.
This latter indicates the vIOMMU granule will match
the host page size.
A subsequent patch will add such a property to the
virtio-iommu device.
Signed-off-by: Eric Auger
Signed-off-by: Phil
On Mon, 26 Feb 2024 at 18:06, Alex Bennée wrote:
>
> Alex Bennée writes:
>
> > There are two problems.
> >
> > The first is a .PHONY target will always evaluate which triggers a
> > full re-build of the VM images. Drop the requirement knowing that this
> > introduces a manual step on freshly conf
On Wed, 21 Feb 2024 10:16:02 -0800
nifan@gmail.com wrote:
> From: Fan Ni
>
> Since fabric manager emulation is not supported yet, the change implements
> the functions to add/release dynamic capacity extents as QMP interfaces.
>
> Note: we skips any FM issued extent release request if the e
On Mon, 26 Feb 2024 at 00:04, Sergey Kambalin wrote:
>
> Introducing Raspberry Pi 4B model.
> It contains new BCM2838 SoC, PCIE subsystem,
> RNG200, Thermal sensor and Genet network controller.
>
> It can work with recent linux kernels 6.x.x.
> Two avocado tests was added to check that.
>
> Unit t
On 14/11/23 00:01, Gustavo Romero wrote:
Currently, the QTest API does not provide a function to capture when an
IRQ line is raised or lowered, although the QTest Protocol already
reports such IRQ transitions. As a consequence, it is also not possible
to capture when an IRQ line is toggled. Funct
On Wed, 21 Feb 2024 10:16:01 -0800
nifan@gmail.com wrote:
> From: Fan Ni
>
> Per CXL spec 3.1, two mailbox commands are implemented:
> Add Dynamic Capacity Response (Opcode 4802h) 8.2.9.9.9.3, and
> Release Dynamic Capacity (Opcode 4803h) 8.2.9.9.9.4.
>
> Signed-off-by: Fan Ni
Hi Fan,
C
Alex Bennée writes:
> There are two problems.
>
> The first is a .PHONY target will always evaluate which triggers a
> full re-build of the VM images. Drop the requirement knowing that this
> introduces a manual step on freshly configure build dirs.
>
> The second is a minor unrelated tweak to th
On Wed, 21 Feb 2024 10:16:00 -0800
nifan@gmail.com wrote:
> From: Fan Ni
>
> Add dynamic capacity extent list representative to the definition of
> CXLType3Dev and add get DC extent list mailbox command per
> CXL.spec.3.1:.8.2.9.9.9.2.
>
> Signed-off-by: Fan Ni
Follow on from earlier comme
There are two problems.
The first is a .PHONY target will always evaluate which triggers a
full re-build of the VM images. Drop the requirement knowing that this
introduces a manual step on freshly configure build dirs.
The second is a minor unrelated tweak to the Makefile also triggers an
expens
On Wed, 21 Feb 2024 10:15:59 -0800
nifan@gmail.com wrote:
> From: Fan Ni
>
> Add (file/memory backed) host backend, all the dynamic capacity regions
> will share a single, large enough host backend. Set up address space for
> DC regions to support read/write operations to dynamic capacity fo
1 - 100 of 376 matches
Mail list logo
