Re: [PATCH v2 10/12] hw/xen: pvh-common: Add support for creating PCIe/GPEX

On Tue, 20 Aug 2024, Edgar E. Iglesias wrote: > From: "Edgar E. Iglesias" > > Add support for optionally creating a PCIe/GPEX controller. > > Signed-off-by: Edgar E. Iglesias Reviewed-by: Stefano Stabellini > --- > hw/xen/xen-pvh-common.c | 76 + > i

Re: [PATCH v2 11/12] hw/i386/xen: Add a Xen PVH x86 machine

On Tue, 20 Aug 2024, Edgar E. Iglesias wrote: > From: "Edgar E. Iglesias" > > Add a Xen PVH x86 machine based on the abstract PVH Machine. > > Signed-off-by: Edgar E. Iglesias Reviewed-by: Stefano Stabellini > --- > hw/i386/xen/meson.build | 1 + > hw/i386/xen/xen-pvh.c | 121

Re: [PATCH for-9.1] hw/loongarch: Fix length for lowram in ACPI SRAT

gap, i, MEM_AFFINITY_ENABLED); len -= gap; base = VIRT_HIGHMEM_BASE; gap = machine->ram_size - VIRT_LOWMEM_SIZE; --- base-commit: 075fd020afe3150a0e6c4b049705b358b597b65a change-id: 20240820-fix-numa-range-f1f0302e138d Best regards, Thanks for catching this. Reviewed-by: Bibo Mao

Re: [PULL 0/1] Migration patches for 2024-08-20

gitlab.com/farosas/qemu.git tags/migration-20240820-pull-request for you to fetch changes up to 4c107870e8b2ba3951ee0c46123f1c3b5d3a19d3: migration/multifd: FreeMultiFDRecvParams::data (2024-08-20 12:44:13 -0300) Migration pu

[PULL 2/5] bsd-user: Handle short reads in mmap_h_gt_g

In particular, if an image has a large bss, we can hit EOF before reading all bytes of the mapping. Mirror the similar change to linux-user. Signed-off-by: Richard Henderson Reviewed-by: Philippe Mathieu-Daudé Message-Id: <20240820050848.165253-3-richard.hender...@linaro.org> --- bsd-user/mmap

[PULL 3/5] target/i386: Split out gen_prepare_val_nz

Split out the TCG_COND_TSTEQ logic from gen_prepare_eflags_z, and use it for CC_OP_BMILG* as well. Prepare for requiring both zero and non-zero senses. Reviewed-by: Philippe Mathieu-Daudé Signed-off-by: Richard Henderson Message-Id: <20240801075845.573075-2-richard.hender...@linaro.org> --- ta

[PULL 5/5] target/i386: Fix tss access size in switch_tss_ra

The two limit_max variables represent size - 1, just like the encoding in the GDT, thus the 'old' access was off by one. Access the minimal size of the new tss: the complete tss contains the iopb, which may be a larger block than the access api expects, and irrelevant because the iopb is not access

[PULL 4/5] target/i386: Fix carry flag for BLSI

BLSI has inverted semantics for C as compared to the other two BMI1 instructions, BLSMSK and BLSR. Introduce CC_OP_BLSI* for this purpose. Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2175 Signed-off-by: Richard Henderson Reviewed-by: Philippe Mathieu-Daudé Message-Id: <2024080107584

[PULL 0/5] misc patch queue

Two x86 fixes and one {bsd,linux}-user fix. r~ The following changes since commit 9eb5bfbe3394b92fb37cc6f155ceea4d6c9e401c: Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2024-08-20 21:29:52 +1000) are available in the Git repository at: https:

[PULL 1/5] linux-user: Handle short reads in mmap_h_gt_g

In particular, if an image has a large bss, we can hit EOF before reading all host_len bytes of the mapping. Create a helper, mmap_pread to handle the job for both the larger block in mmap_h_gt_g itself, as well as the smaller block in mmap_frag. Cc: qemu-sta...@nongnu.org Fixes: eb5027ac618 ("li

[PULL 0/1] LoongArch: Fix for 9.1

The following changes since commit 4220ebde107c44412755d593fb46e168eeaed936: Merge tag 'migration-20240820-pull-request' of https://gitlab.com/farosas/qemu into staging (2024-08-21 08:46:45 +1000) are available in the Git repository at: https://gitlab.com/gaosong/qemu.git

[PULL 1/1] hw/loongarch: Fix length for lowram in ACPI SRAT

From: Jiaxun Yang The size of lowram should be "gap" instead of the whole node. This is failing kernel's sanity check: [0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x-0x] [0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x8000-0x16fff] [0.00] ACPI: SRAT: Node 1 PXM 1

Re: [PATCH v3] kvm: replace fprintf with error_report/printf() in kvm_init()

> On 16 Aug 2024, at 11:51 AM, Philippe Mathieu-Daudé wrote: > > On 12/8/24 11:59, Ani Sinha wrote: >> On Mon, 12 Aug, 2024, 3:23 pm Ani Sinha, > > wrote: >>On Fri, Aug 9, 2024 at 2:06 PM Philippe Mathieu-Daudé >>mailto:phi...@linaro.org>> wrote: >> > >>

Re: [PULL 0/5] misc patch queue

On 8/21/24 12:25, Richard Henderson wrote: The following changes since commit 9eb5bfbe3394b92fb37cc6f155ceea4d6c9e401c: Merge tag 'for_upstream' ofhttps://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2024-08-20 21:29:52 +1000) are available in the Git repository at: https://gi

Re: [PATCH v2 1/4] gdbstub: Use specific MMU index when probing MTE addresses

On 8/8/24 15:15, Gustavo Romero wrote: @@ -458,8 +459,10 @@ static void handle_q_memtag(GArray *params, void *user_ctx) gdb_put_packet("E03"); } +/* Find out the current translation regime for probe. */ +mmu_index = cpu_mmu_index(env_cpu(env), false) & ARM_MMU_IDX_CORE

Re: [PATCH v2 4/4] tests/tcg/aarch64: Extend MTE gdbstub tests to system mode

On 8/8/24 15:15, Gustavo Romero wrote: diff --git a/tests/tcg/aarch64/system/boot.S b/tests/tcg/aarch64/system/boot.S index 501685d0ec..79a2ada74a 100644 --- a/tests/tcg/aarch64/system/boot.S +++ b/tests/tcg/aarch64/system/boot.S @@ -135,6 +135,17 @@ __start: orr x1, x1, x3 st

Re: [PATCH RFC V3 17/29] arm/virt: Release objects for *disabled* possible vCPUs after init

Hi Salil, On 8/21/24 2:40 AM, Salil Mehta wrote: I don’t understand this clearly. Are you suggesting to reuse only single vCPU object to initialize all KVM vCPUs not yet plugged? If yes, then I'm not sure what do we gain here by adding this complexity? It does not consume time or resources bec

Re: [PULL 0/1] LoongArch: Fix for 9.1

On 8/21/24 12:47, Song Gao wrote: The following changes since commit 4220ebde107c44412755d593fb46e168eeaed936: Merge tag 'migration-20240820-pull-request' ofhttps://gitlab.com/farosas/qemu into staging (2024-08-21 08:46:45 +1000) are available in the Git repository at:

Re: [PATCH 2/5] hw/net/can/xlnx-versal-canfd: Fix CAN FD flag check

Hello Doug Brown, On Friday 16 of August 2024 18:35:02 Doug Brown wrote: > When checking the QEMU_CAN_FRMF_TYPE_FD flag, we need to ignore other > potentially set flags. Before this change, received CAN FD frames from > SocketCAN weren't being recognized as CAN FD. > > Signed-off-by: Doug Brown >

<    1   2