Em Sun, 11 May 2025 09:45:55 -0400
"Michael S. Tsirkin" escreveu:
> On Sun, May 11, 2025 at 09:45:04AM -0400, Michael S. Tsirkin wrote:
> > On Fri, Mar 07, 2025 at 08:14:29PM +0100, Mauro Carvalho Chehab wrote:
> > > Hi Michael,
> > >
> > > I'm sending v8 to avoid a merge conflict with v7 due
The GHES migration logic should now support HEST table location too.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Jonathan Cameron
Reviewed-by: Igor Mammedov
---
hw/acpi/generic_event_device.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/hw/acpi/gener
The ghes_record_cper_errors() function was introduced to be used
by other types of errors, as part of the error injection
patch series. That's why it is not static.
Make it non-static again to allow its usage outside ghes.c
This reverts commit 611f3bdb20f7828b0813aa90d47d1275ef18329b.
Signed-off
Such file will be used to track HEST table changes.
For now, disallow HEST table check until we update it to the
current data.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Igor Mammedov
Reviewed-by: Jonathan Cameron
---
tests/data/acpi/aarch64/virt/HEST | 0
tests/qtest/bios-table
On 5/13/25 13:38, Anthony Krowiak wrote:
On 5/12/25 2:02 PM, Rorie Reyes wrote:
Handle interception of the CHSC SEI instruction for requests
indicating the guest's AP configuration has changed.
If configuring --without-default-devices, hw/s390x/ap-stub.c
was created to handle such circumstan
On 19.05.2025 07:04, alistai...@gmail.com wrote:
From: Alistair Francis
First RISC-V PR for 10.1
* Add support for RIMT to virt machine ACPI
* Don't allow PMP RLB to bypass rule privileges
* Fix checks on writes to pmpcfg in Smepmp MML mode
* Generate strided vector loads/stores with tcg nod
On 5/16/25 19:58, Steven Sistare wrote:
On 5/16/2025 4:31 AM, Cédric Le Goater wrote:
On 5/12/25 17:32, Steve Sistare wrote:
Export various MSI functions, for use by CPR in subsequent patches.
No functional change.
Signed-off-by: Steve Sistare
Please rename this routines with a 'vfio_pci' p
Creates a QMP command to be used for generic ACPI APEI hardware error
injection (HEST) via GHESv2, and add support for it for ARM guests.
Error injection uses ACPI_HEST_SRC_ID_QMP source ID to be platform
independent. This is mapped at arch virt bindings, depending on the
types supported by QEMU a
Hi Michael,
This is v9 of the patch series, rebased to apply after release
10.0. It addresses 3 issues:
- backward compatibility logic moved to version 10.0;
- fixed a compilation issue with target/arm/kvm.c (probably
caused by some rebase - funny enough, incremental
compilation was fine her
Currently, aarch64 can generate a HEST table when loaded with
-machine ras=on. Add support for it.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Igor Mammedov
Reviewed-by: Jonathan Cameron
---
tests/qtest/bios-tables-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
We'll be adding a new GED device for HEST GPIO notification and
increasing the number of entries at the HEST table.
Blocklist testing HEST and DSDT tables until such changes
are completed.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Igor Mammedov
Reviewed-by: Jonathan Cameron
---
tests/qte
Store HEST table address at GPA, placing its the start of the table at
hest_addr_le variable.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Jonathan Cameron
Reviewed-by: Igor Mammedov
---
hw/acpi/ghes.c | 22 --
include/hw/acpi/ghes.h | 6 +-
2 files change
The current code is actually dependent on having just one error
structure with a single source, as any change there would cause
migration issues.
As the number of sources should be arch-dependent, as it will depend on
what kind of notifications will exist, and how many errors can be
reported at th
@@ -1,39 +1,39 @@
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20240322 (64-bit version)
* Copyright (c) 2000 - 2023 Intel Corporation
*
- * Disassembly of tests/data/acpi/aarch64/virt/HEST
+ * Disassembly of /tmp/aml-DMPE22
*
* ACPI Data Table [HEST]
*
*
Move the check logic into a common function and simplify the
code which checks if GHES is enabled and was properly setup.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Jonathan Cameron
Reviewed-by: Igor Mammedov
---
hw/acpi/ghes-stub.c| 7 ---
hw/acpi/ghes.c | 38 +
Now that HEST table is checked for aarch64, add the current
firmware file.
Signed-off-by: Mauro Carvalho Chehab
Acked-by: Igor Mammedov
Reviewed-by: Jonathan Cameron
---
tests/data/acpi/aarch64/virt/HEST | Bin 0 -> 132 bytes
tests/qtest/bios-tables-test-allowed-diff.h | 1 -
2 fil
Using the QMP GHESv2 API requires preparing a raw data array
containing a CPER record.
Add a helper script with subcommands to prepare such data.
Currently, only ARM Processor error CPER record is supported, by
using:
$ ghes_inject.py arm
which produces those warnings on Linux:
[ 705.0
On 5/19/25 15:26, Steve Sistare wrote:
Modify memory_get_xlat_addr and vfio_get_xlat_addr to return the memory
region that the translated address is found in. This will be needed by
CPR in a subsequent patch to map blocks using IOMMU_IOAS_MAP_FILE.
Also return the xlat offset, so we can simplif
Add a new ags flag to change the way HEST offsets are calculated.
Currently, offsets needed to store ACPI HEST offsets and read ack
are calculated based on a previous knowledge from the logic
which creates the HEST table.
Such logic is not generic, not allowing to easily add more HEST
entries nor
While the HEST layout didn't change, there are some internal
changes related to how offsets are calculated and how memory error
events are triggered.
Update specs to reflect such changes.
Signed-off-by: Mauro Carvalho Chehab
Reviewed-by: Jonathan Cameron
Reviewed-by: Igor Mammedov
---
docs/sp
Adds a generic error device to handle generic hardware error
events as specified at ACPI 6.5 specification at 18.3.2.7.2:
https://uefi.org/specs/ACPI/6.5/18_Platform_Error_Interfaces.html#event-notification-for-generic-error-sources
using HID PNP0C33.
The PNP0C33 device is used to report hardware
On Mon, May 19, 2025 at 3:20 AM Alistair Francis wrote:
>
> On Tue, May 6, 2025 at 8:47 AM Daniel Henrique Barboza
> wrote:
> >
> > Hi Alistair,
> >
> >
> > I think we should push this upstream and see what happens. We'll have a
> > full release cycle to undo the change in case we find unintended
On 5/15/25 08:05, Alistair Francis wrote:
On Mon, May 12, 2025 at 7:53 PM Paolo Bonzini wrote:
Same as v4, with suggestion from Richard to avoid parentheses---which also
fixes the issue with kvm-cpu.c reported by Daniel Barboza. KVM/RISC-V is
now covered in CI and passes with this version.
P
On 5/12/25 17:32, Steve Sistare wrote:
If there are multiple containers and unmap-all fails for some container, we
need to remap vaddr for the other containers for which unmap-all succeeded.
Recover by walking all address ranges of all containers to restore the vaddr
for each. Do so by invoking
On Tue, May 20, 2025 at 3:08 PM Michael Tokarev wrote:
>
> On 19.05.2025 07:04, alistai...@gmail.com wrote:
> > From: Alistair Francis
>
> > First RISC-V PR for 10.1
> >
> > * Add support for RIMT to virt machine ACPI
> > * Don't allow PMP RLB to bypass rule privileges
> > * Fix checks on writes
Hello John,
Would it be complex to propose a functional test for it ?
We have a libvfio-user we can use, but this would be a problem:
487 │ 2025-05-19 14:19:20,304: modprobe gpio-pci-idio-16
488 │ 2025-05-19 14:19:20,306: modprobe: FATAL: Module gpio-pci-idio-16 not
found in director
On 19.05.25 2:10 PM, Fiona Ebner wrote:
> Am 14.05.25 um 21:54 schrieb Kevin Wolf:
>> Am 08.05.2025 um 16:09 hat Fiona Ebner geschrieben:
>>> In bdrv_graph_wrlock() there is a comment that it uses
>>> bdrv_drain_all_begin_nopoll() to make sure that constantly arriving
>>> new I/O doesn't cause star
There are two pointers that are needed during error injection:
1. The start address of the CPER block to be stored;
2. The address of the read ack.
It is preferable to calculate them from the HEST table. This allows
checking the source ID, the size of the table and the type of the
HEST error blo
>Hello,
>
>On 5/19/25 02:01, edmund.raile wrote:
Restore SR-IOV Intel iGPU VF passthrough capability:
Check x-igd-opregion=off parameter in vfio_pci_igd_config_quirk and
vfio_pci_kvmgt_config_quirk to ensure x-igd-opregion=off is
respected despite subsequent attempt of automatic
On 2025/5/19 下午2:50, Jiaxun Yang wrote:
在2025年5月19日周一 上午3:56，Bibo Mao写道：
[...]
Hi Bibo,
I believe hijacking loongarch_extioi.c is not the proper way to do it.
The sensible solution is to create a TYPE_LOONGARCH_EXTIOI_KVM, which
inherits TYPE_LOONGARCH_EXTIOI_COMMON, and let machine creat
Hi,
On Mon, 12 May 2025 at 18:22, Prasad Pandit wrote:
> From: Prasad Pandit
>
> Add new qtests to run postcopy migration with multifd
> channels enabled.
>
> Signed-off-by: Prasad Pandit
> ---
> tests/qtest/migration/compression-tests.c | 18
> tests/qtest/migration/postcopy-tests.c
On 5/19/25 08:59, edmund.raile wrote:
Hello,
On 5/19/25 02:01, edmund.raile wrote:
Restore SR-IOV Intel iGPU VF passthrough capability:
Check x-igd-opregion=off parameter in vfio_pci_igd_config_quirk and
vfio_pci_kvmgt_config_quirk to ensure x-igd-opregion=off is
respected despite subsequent at
Hi Philippe,
On 5/16/2025 8:08 PM, Philippe Mathieu-Daudé wrote:
> Hi,
>
> On 16/5/25 12:05, Sairaj Kodilkar wrote:
>> From: Vasant Hegde
>>
>> If vCPUs > 255 then x86 common code (x86_cpus_init()) call
>> kvm_enable_x2apic().
>> But if vCPUs <= 255 then the common code won't calls kvm_enable_
>On 5/19/25 08:59, edmund.raile wrote:
>>> Hello,
>>>
>>> On 5/19/25 02:01, edmund.raile wrote:
>> Restore SR-IOV Intel iGPU VF passthrough capability:
>> Check x-igd-opregion=off parameter in vfio_pci_igd_config_quirk and
>> vfio_pci_kvmgt_config_quirk to ensure x-igd-opregion=off is
>
Restore SR-IOV Intel iGPU VF passthrough capability:
Check x-igd-opregion=off parameter in vfio_pci_igd_config_quirk and
vfio_pci_kvmgt_config_quirk to ensure x-igd-opregion=off is
respected despite subsequent attempt of automatic
IGD opregion detection.
Fixes: c0273e77f2d7 ("vfio/igd: Detect IGD
On 5/18/25 19:00, John Levon wrote:
On Fri, May 16, 2025 at 05:11:27PM +0200, Cédric Le Goater wrote:
@@ -121,7 +121,7 @@ struct VFIOIOMMUClass {
void (*listener_commit)(VFIOContainerBase *bcontainer);
We forgot to document the listener_commit() and listener_begin() handlers.
Apologi
On 17.05.25 15:55, Steven Sistare wrote:
On 5/16/2025 4:50 PM, David Hildenbrand wrote:
On 16.05.25 21:26, Steven Sistare wrote:
On 5/16/2025 2:58 PM, David Hildenbrand wrote:
On 16.05.25 19:13, Steve Sistare wrote:
Modify memory_get_xlat_addr and vfio_get_xlat_addr to return the memory
regio
Hello Jamin
On 5/19/25 03:52, Jamin Lin wrote:
Hi Cédric
Subject: Re: [PULL 45/46] tests/functional/aspeed: Add test case for AST2700
A1
On 5/16/25 04:59, Jamin Lin wrote:
Hi Cédric
On a BE host, if I run an ast2700a0-evb machine :
$ qemu-system-aarch64 -machine ast2700a0-evb ...
Hi Donald,
>-Original Message-
>From: Donald Dutile
>Subject: Re: [PATCH rfcv2 00/20] intel_iommu: Enable stage-1 translation for
>passthrough device
>
>Zhenzhong,
>
>Hi!
>Eric asked me to review this series.
>Since it's rather late since you posted will summarize review feedback
>below/b
On 5/16/25 21:48, Steven Sistare wrote:
On 5/16/2025 1:17 PM, Steven Sistare wrote:
On 5/16/2025 12:37 PM, Cédric Le Goater wrote:
Steve,
+ John
On 5/12/25 17:32, Steve Sistare wrote:
Support vfio and iommufd devices with the cpr-transfer live migration mode.
Devices that do not support live
Pierrick Bouvier writes:
> From: Daniel P. Berrangé
>
> This removes the TARGET_* conditions from all the CPU commands
> that are conceptually target independent. Top level stubs are
> provided to cope with targets which do not currently implement
> all of the commands.
>
> Reviewed-by: Richard
On Sun, 11 May 2025 14:10:46 -0400
"Michael S. Tsirkin" wrote:
> On Thu, Apr 24, 2025 at 01:24:38PM +0100, Alireza Sanaee wrote:
> > From: Yicong Yang
> >
> > Currently we build the PPTT starting from the socket node and each
> > socket will be a separate tree. For a multi-socket system it'll
>
Pierrick Bouvier writes:
> There is no more QAPI files that need to be compiled per target, so we
> can remove this.
Yes, with the target-specific conditonals gone, no QAPI-generated file
needs to be compiled per target. Garbage collection has two parts:
* qapi_specific_outputs has become empt
在2025年5月19日周一 上午8:09，Bibo Mao写道：
> On 2025/5/19 下午2:50, Jiaxun Yang wrote:
>>
>>
>> 在2025年5月19日周一 上午3:56，Bibo Mao写道：
>> [...]
Hi Bibo,
I believe hijacking loongarch_extioi.c is not the proper way to do it.
The sensible solution is to create a TYPE_LOONGARCH_EXTIOI_KVM,
On 5/16/25 20:18, Steven Sistare wrote:
On 5/16/2025 4:35 AM, Cédric Le Goater wrote:
On 5/12/25 17:32, Steve Sistare wrote:
cpr-transfer breaks vfio network connectivity to and from the guest, and
the host system log shows:
irq bypass consumer (token a03c32e5) registration fails: -1
Pierrick Bouvier writes:
> Reviewed-by: Daniel P. Berrangé
> Reviewed-by: Richard Henderson
> Signed-off-by: Pierrick Bouvier
> ---
> qapi/meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qapi/meson.build b/qapi/meson.build
> index 7582c2b5bcf..6cc3afce721
On Wed, 30 Apr 2025 08:27, Mario Fleischmann
wrote:
>Support three main memory space types:
>
>* Physical memory
>* Logical memory (MMU)
>* GDB Registers
>
>Use custom memory type to mark memory spaces as secure
>
>V=1 QTEST_QEMU_BINARY="./qemu-system-arm -M virt,secure=on -cpu cortex-a15"
>test
On Wed, 30 Apr 2025 08:27, Mario Fleischmann
wrote:
>Signed-off-by: Mario Fleischmann
>---
> gdbstub/gdbstub.c | 2 +-
> include/exec/gdbstub.h | 10 ++
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
>diff --git a/gdbstub/gdbstub.c b/gdbstub/gdbstub.c
>index 291ac55..6ace944 10
在2025年5月19日周一 上午9:55，Bibo Mao写道：
[...]
>> It's actually different machine as kernel irqchip is never on par with
>> usermode
>> emulation. This approach is taken by i386 (TYPE_KVM_IOAPIC vs TYPE_IOAPIC),
>> Arm (TYPE_KVM_ARM_ITS vs TYPE_ARM_GICV3_ITS), PowerPC (TYPE_KVM_OPENPIC vs
>> TYPE_OPENP
On Fri, May 16, 2025 at 05:56:54PM +0200, Juraj Marcin wrote:
> From: Juraj Marcin
>
> This is done in preparation for enabling the SO_KEEPALIVE support for
> server sockets and adding settings for more TCP keep-alive socket
> options.
>
> Signed-off-by: Juraj Marcin
> ---
> util/qemu-sockets.
On Fri, May 16, 2025 at 05:56:59PM +0200, Juraj Marcin wrote:
> From: Juraj Marcin
>
> With the default TCP stack configuration, it could be even 2 hours
> before the connection times out due to the other side not being
> reachable. However, in some cases, the application needs to be aware of
> a
On Sat, May 17, 2025 at 11:11:52PM +0300, Nir Soffer wrote:
> Testings reading and writing from qemu-nbd using a unix domain socket
> shows that the platform default send buffer size is too low, leading to
> poor performance and hight cpu usage.
>
> Add a helper for setting socket send buffer size
On Sat, May 17, 2025 at 11:11:53PM +0300, Nir Soffer wrote:
> On macOS we need to increase unix socket buffers size on the client and
> server to get good performance. We set socket buffers on macOS after
> connecting or accepting a client connection.
>
> Testing shows that setting socket receive
On Sat, May 17, 2025 at 11:11:54PM +0300, Nir Soffer wrote:
> Like macOS we have similar issue on Linux. For TCP socket the send
> buffer size is 2626560 bytes (~2.5 MiB) and we get good performance.
> However for unix socket the default and maximum buffer size is 212992
> bytes (208 KiB) and we se
On Thu, May 15, 2025 at 07:20:11PM -0300, Fabiano Rosas wrote:
> The IOWatchPoll holds a reference to the iochannel while the "child"
> source (iwp->src) is removed from the context and freed. Freeing the
> source leads to the iochannel being also freed at
> qio_channel_fd_source_finalize().
>
> L
On Thu, May 15, 2025 at 07:20:12PM -0300, Fabiano Rosas wrote:
> tcp_chr_free_connection() can be called multiple times in succession,
> in which case the yank function will get as argument a NULL s->sioc
> that has been cleared by the previous tcp_chr_free_connection() call.
>
> This leads to an
On Thu, May 15, 2025 at 07:20:14PM -0300, Fabiano Rosas wrote:
> It's possible for the hup_source to have its reference decremented by
> remove_hup_source() while it's still being added to the context,
> leading to asserts in glib:
IIUC this must mean that
tcp_chr_free_connection
is being call
On Thu, May 15, 2025 at 07:20:13PM -0300, Fabiano Rosas wrote:
> There's currently five places where the yank function is being
> registered and they all come right before tcp_chr_new_client(). Fold
> them into it.
>
> Signed-off-by: Fabiano Rosas
> ---
> chardev/char-socket.c | 31 ++---
On Wed, 30 Apr 2025 08:27, Mario Fleischmann
wrote:
>Signed-off-by: Mario Fleischmann
>---
> gdbstub/gdbstub.c | 7 ---
> include/exec/gdbstub.h | 8 +++-
> 2 files changed, 7 insertions(+), 8 deletions(-)
>
>diff --git a/gdbstub/gdbstub.c b/gdbstub/gdbstub.c
>index 565f6b3..291ac55 1
On Fri, May 16, 2025 at 05:56:57PM +0200, Juraj Marcin wrote:
> From: Juraj Marcin
>
> Before refactoring the inet_parse() function, this patch adds tests
> verifying the inet address parsing works correctly.
>
> Signed-off-by: Juraj Marcin
> ---
> tests/unit/test-util-sockets.c | 161
Signed-off-by: Edmund Raile
---
hw/vfio/igd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/vfio/igd.c b/hw/vfio/igd.c
index e54a2a2f00..36ceb85212 100644
--- a/hw/vfio/igd.c
+++ b/hw/vfio/igd.c
@@ -203,7 +203,7 @@ static bool vfio_pci_igd_opregion_detect(VFIOPCIDevice
*
+1,5 @@
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
---
base-commit: 757a34115e7491744a63dfc3d291fd1de5297ee2
change-id: 20250519-gdbstub-aarch64-pstate-xml-d90bac349712
--
γαῖα πυρί μιχθήτω
On Sat, May 17, 2025 at 11:11:52PM +0300, Nir Soffer wrote:
> Testings reading and writing from qemu-nbd using a unix domain socket
Nit pick that this should be "Testing", not "Testings". (Or
"Experiments" if you really wanted a plural noun.)
Rich.
--
Richard Jones, Virtualization Group, Red H
Hello Paolo, Bernhard,
On Mon, May 12, 2025 at 6:32 PM Paolo Bonzini wrote:
>
> Hi, now that GSoC selection is over I'm back. Sorry for the delay;
> Tanish Desai will work mostly on tracing, so logging can remain yours.
>
> On Tue, Apr 8, 2025 at 10:59 PM Bernhard Beschow wrote:
> > >Currently t
Alexandre Ghiti writes:
> The satp mode is set using the svXX properties, but that actually
> restricts the satp mode to the minimum required by the profile and
> prevents the use of higher satp modes.
>
> Fix this by not setting any svXX property and allow all satp mode to be
> supported.
I fig
Am 14.05.25 um 21:54 schrieb Kevin Wolf:
> Am 08.05.2025 um 16:09 hat Fiona Ebner geschrieben:
>> In bdrv_graph_wrlock() there is a comment that it uses
>> bdrv_drain_all_begin_nopoll() to make sure that constantly arriving
>> new I/O doesn't cause starvation. The changes from this series are at
>>
On Thu, 15 May 2025 at 14:59, Daniel P. Berrangé wrote:
>
> Various checks in the code were under-indented relative to other
> surrounding code.
Isn't the problem here not that they're under-indented,
but that they don't follow the "indent with hard coded
tab characters" style that the rest of th
On Thu, 15 May 2025 at 14:59, Daniel P. Berrangé wrote:
>
> Some checks want to be performed either at the start of a new file
> within a patch, or at the end. This is complicated by the fact that
> the information relevant to the check may be spread across multiple
> lines. It is further complica
On Thu, 15 May 2025 at 15:00, Daniel P. Berrangé wrote:
>
> Going forward we want all newly created source files to have an
> SPDX-License-Identifier tag present.
>
> Initially mandate this for C, Python, Perl, Shell source files,
> as well as JSON (QAPI) and Makefiles, while encouraging users
> t
On Thu, 15 May 2025 at 15:00, Daniel P. Berrangé wrote:
>
> The current regex matches Makefile & Makefile.objs, but the latter is
> no longer used, and we're missing coverage of Makefile.include and
> Makefile.target. Expand the pattern to match any suffix.
>
> Signed-off-by: Daniel P. Berrangé
>
On Wed, May 14, 2025 at 4:10 PM Aleksandar Rakic
wrote:
> Could you please let us know if you have any comments
> on the latest version of this patch?
>
> Kind regards,
> Aleksandar Rakic
I confirm my "reviewed-by" for v5 1/3 (v5 is the same as the initial
one I reviewed, except tests are added)
On Thu, 15 May 2025 at 14:59, Daniel P. Berrangé wrote:
>
> The ACPI test data check needs to analyse a list of all files in a
> commit, so can use the new hook for processing the file list.
>
> Signed-off-by: Daniel P. Berrangé
> ---
> scripts/checkpatch.pl | 61
On Thu, 15 May 2025 at 15:00, Daniel P. Berrangé wrote:
>
> When seeing a new/deleted/renamed file we check to see if MAINTAINERS
> is updated, but we don't give the user a list of files affected, as
> we don't want to repeat the same warning many times over.
>
> Using the new file list hook, we c
Am 14.05.25 um 19:26 schrieb Kevin Wolf:
> Am 08.05.2025 um 16:09 hat Fiona Ebner geschrieben:
>> Signed-off-by: Fiona Ebner
>> ---
>>
>> Could the bs associated to the device change because of polling
>> when draining? If yes, does that mean we need to drain all in the
>> beginning and not tempor
John,
+ Steven,
On 5/15/25 17:43, John Levon wrote:
The series contains an implement of a vfio-user client in QEMU, along with a few
more preparatory patches.
The vfio-user protocol allows for implementing (PCI) devices in another
userspace process; SPDK is one example, which includes a virtua
On 5/19/25 13:24, edmund.raile wrote:
Signed-off-by: Edmund Raile
Reviewed-by: Cédric Le Goater
Thanks,
C.
---
hw/vfio/igd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/vfio/igd.c b/hw/vfio/igd.c
index e54a2a2f00..36ceb85212 100644
--- a/hw/vfio/igd.c
+++ b
On Thu, 15 May 2025 at 14:59, Daniel P. Berrangé wrote:
>
> The file permissions check is the kind of check intended to be performed
> in the new start of file hook.
>
> Reviewed-by: Cédric Le Goater
> Signed-off-by: Daniel P. Berrangé
> ---
> scripts/checkpatch.pl | 19 +++
> 1
On 5/16/25 9:23 AM, Alexandre Ghiti wrote:
The satp mode is set using the svXX properties, but that actually
restricts the satp mode to the minimum required by the profile and
prevents the use of higher satp modes.
For rva23s64, in "Optional Extensions" we'll find:
https://github.com/riscv/
On Thu, 15 May 2025 18:04:18 +0900
Itaru Kitayama wrote:
> > On May 13, 2025, at 20:14, Jonathan Cameron
> > wrote:
> >
> > Add a single complex case for aarch64 virt machine.
> > Given existing much more comprehensive tests for x86 cover the
> > common functionality, a single test should be e
Hi Manos,
You mentioned you are looking at a Rust implementation of our PFlash
model. IMHO better would be to implement from scratch without looking
at the C code. In case you need to, here are few notes about some
oddities I unfortunately inherited as maintainer.
[*] Interface to write sector
Manos Pitsidianakis writes:
> Update aarch64-core.xml to include field definitions for PSTATE, which
> in gdb is modelled in the cpsr (current program status register)
> pseudo-register, named after the actual cpsr register in armv7.
>
> Defining the fields layout of the register allows easy insp
On 2025/5/19 下午4:49, Jiaxun Yang wrote:
在2025年5月19日周一 上午8:09，Bibo Mao写道：
On 2025/5/19 下午2:50, Jiaxun Yang wrote:
在2025年5月19日周一 上午3:56，Bibo Mao写道：
[...]
Hi Bibo,
I believe hijacking loongarch_extioi.c is not the proper way to do it.
The sensible solution is to create a TYPE_LOONGARCH_E
Alex Bennée writes:
> Dominik 'Disconnect3d' Czarnota writes:
>
>> This commit adds support for the `qGDBServerVersion` packet to the qemu
>> gdbstub which could be used by clients to detect the QEMU version
>> (and, e.g., use a workaround for known bugs).
>>
>> This packet is not documented/st
Thanks!
On Mon, 19 May 2025 at 14:59, Alex Bennée wrote:
> Alex Bennée writes:
>
> > Dominik 'Disconnect3d' Czarnota writes:
> >
> >> This commit adds support for the `qGDBServerVersion` packet to the qemu
> >> gdbstub which could be used by clients to detect the QEMU version
> >> (and, e.g.,
On 5/18/25 18:26, Yiwei Zhang wrote:
> Venus and later native contexts have their own fence context along with
> multiple timelines within. Fences wtih VIRTIO_GPU_FLAG_INFO_RING_IDX in
> the flags must be dispatched to be created on the target context. Fence
> signaling also has to be handled on th
On 5/15/25 21:08, Steven Sistare wrote:
On 5/15/2025 8:59 AM, Cédric Le Goater wrote:
On 5/12/25 17:32, Steve Sistare wrote:
At vfio creation time, save the value of vfio container, group, and device
descriptors in CPR state. On qemu restart, vfio_realize() finds and uses
the saved descriptors
On 5/19/2025 4:28 AM, David Hildenbrand wrote:
On 17.05.25 15:55, Steven Sistare wrote:
On 5/16/2025 4:50 PM, David Hildenbrand wrote:
On 16.05.25 21:26, Steven Sistare wrote:
On 5/16/2025 2:58 PM, David Hildenbrand wrote:
On 16.05.25 19:13, Steve Sistare wrote:
Modify memory_get_xlat_addr a
This patch fixes two critical issues in QEMU with KVM:
1. Post-Migration Failure in User Mode: When QEMU with KVM is running in user
mode, the guest may fail to function correctly after migration due to incorrect
privilege state restoration.
2. Multi-Core Guest Inconsistency: After migration, o
On Thu, 15 May 2025 at 15:00, Daniel P. Berrangé wrote:
>
> The previous commit mandates use of SPDX-License-Identifier on common
> source files, and encourages it on all other files.
>
> Some contributors are none the less still also including the license
> boilerplate text. This is redundant and
Modify memory_get_xlat_addr and vfio_get_xlat_addr to return the memory
region that the translated address is found in. This will be needed by
CPR in a subsequent patch to map blocks using IOMMU_IOAS_MAP_FILE.
Also return the xlat offset, so we can simplify the interface by removing
the out param
On 5/19/25 9:07 AM, Björn Töpel wrote:
Alexandre Ghiti writes:
The satp mode is set using the svXX properties, but that actually
restricts the satp mode to the minimum required by the profile and
prevents the use of higher satp modes.
Fix this by not setting any svXX property and allow all
On Fri, 16 May 2025 at 16:01, wrote:
>
> From: Souleymane Conte
>
> buglink: https://gitlab.com/qemu-project/qemu/-/issues/527
>
> Signed-off-by: Souleymane Conte
Thanks for this patch. It looks good, so I only have
some minor changes to suggest below.
A minor thing: for a single patch, please
On Mon, May 19, 2025 at 02:40:12PM +0200, Cédric Le Goater wrote:
> patches 3-5 seem be ok to merge. They are first on my vfio-next
> candidates.
>
> patches 1-2 should be reworked on top of the memory_get_xlat_addr()
> changes [1] proposed by Steven.
Now v5 is out I will rebase on top of it.
>
On 5/15/25 21:08, Steven Sistare wrote:
On 5/15/2025 9:42 AM, Cédric Le Goater wrote:
On 5/12/25 17:32, Steve Sistare wrote:
In new QEMU, do not register the memory listener at device creation time.
Register it later, in the container post_load handler, after all vmstate
that may affect regions
Gustavo Romero writes:
> Hi Phil,
>
> On 5/16/25 15:47, Philippe Mathieu-Daudé wrote:
>> On 12/5/25 16:45, Gustavo Romero wrote:
>>> Add a functional test, aarch64_hotplug_pci, to exercise PCI hotplug and
>>> hot-unplug on arm64.
>>>
>>> Signed-off-by: Gustavo Romero
>>> Reviewed-by: Daniel P. B
On Sun, May 18, 2025 at 01:54:20PM -0400, Cole Robinson wrote:
> This was fixed in c9d77526bddba0803a1fa982fb59ec98057150f9 for
> 9.2.0 but regressed in db34be329162cf6b06192703065e6c1010dbe3c5 in
> 10.0.0
>
> When the bit is present, rpmbuild complains about missing ELF build-id
>
> Signed-off-b
On Mon, May 19, 2025 at 06:26:43AM -0700, Steve Sistare wrote:
> !---|
> CAUTION: External Email
>
> |---!
>
> Modify memory_get_xlat_addr and vfio_get_xlat_addr to r
On Mon, 19 May 2025 15:55, Alex Bennée wrote:
>Manos Pitsidianakis writes:
>
>> Update aarch64-core.xml to include field definitions for PSTATE, which
>> in gdb is modelled in the cpsr (current program status register)
>> pseudo-register, named after the actual cpsr register in armv7.
>>
>> Defin
The verification of the Stable Release Update for qemu has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
Nicholas Piggin writes:
> Add tests which init the host controller registers to the point where
> command and event rings, irqs are operational. Enumerate ports and set
> up an attached device context that enables device transfer ring to be
> set up and tested.
>
> Signed-off-by: Nicholas Piggin
1 - 100 of 260 matches
Mail list logo
