Hi Alistair,
On 24/7/24 04:44, Alistair Francis wrote:
On Sat, Jul 20, 2024 at 9:15 AM LIU Zhiwei wrote:
This patch set aims to expose 32-bit RISC-V cpu to RV64 QEMU. Thus
qemu-system-riscv64 can directly boot a RV32 Linux.
This patch set has been tested with 6.9.0 Linux Image.
And add an av
On 24/7/24 15:07, Philippe Mathieu-Daudé wrote:
The 'any' CPU is deprecated since commit f57d5f8004b
("target/riscv: deprecate the 'any' CPU type"). Users
are better off using the default CPUs or the 'max' CPU.
Signed-off-by: Philippe Mathieu-Daudé
---
docs/about/deprecated.rst | 13 ---
On 24/7/24 12:51, Michael S. Tsirkin wrote:
with max-bytes set to 0, quota is 0 and so device does not work.
block this to avoid user confusion
Signed-off-by: Michael S. Tsirkin
---
hw/virtio/virtio-rng.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Math
On 24/7/24 11:55, Daniel P. Berrangé wrote:
Daniel P. Berrangé (2):
gitlab: record installed packages in /packages.txt in containers
gitlab: display /packages.txt in build jobs
Reviewed-by: Philippe Mathieu-Daudé
As guest_memfd is now managed by guest_memfd_manager with
RamDiscardManager, only block uncoordinated discard.
Signed-off-by: Chenyi Qiang
---
system/physmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/system/physmem.c b/system/physmem.c
index 98072ae246..ffd68debf0 100
guest_memfd was initially set to shared until the commit bd3bcf6962
("kvm/memory: Make memory type private by default if it has guest memfd
backend"). To align with this change, the default state in
guest_memfd_manager is set to discarded.
One concern raised by this commit is the handling of the v
Introduce a helper function within RamDiscardManager to efficiently
notify all registered RamDiscardListeners, including VFIO listeners
about the memory conversion events between shared and private in
guest_memfd. The existing VFIO listener can dynamically DMA map/unmap
the shared pages based on th
Commit 852f0048f3 ("RAMBlock: make guest_memfd require uncoordinated
discard") effectively disables device assignment with guest_memfd.
guest_memfd is required for confidential guests, so device assignment to
confidential guests is disabled. A supporting assumption for disabling
device-assignment w
As the commit 852f0048f3 ("RAMBlock: make guest_memfd require
uncoordinated discard") highlighted, some subsystems like VFIO might
disable ram block discard. However, guest_memfd relies on the discard
operation to perform page conversion between private and shared memory.
This can lead to stale IOM
Instantiate a new guest_memfd_manager object and register it in the
target MemoryRegion. From this point, other subsystems such as VFIO can
register their listeners in guest_memfd_manager and receive conversion
events through RamDiscardManager.
Signed-off-by: Chenyi Qiang
---
system/physmem.c |
Once exit to userspace to convert the page from private to shared or
vice versa at runtime, notify the state change via the
guest_memfd_state_change() helper so that other registered subsystems
like VFIO can be notified.
Signed-off-by: Chenyi Qiang
---
accel/kvm/kvm-all.c | 7 +++
1 file cha
Markus Armbruster writes:
> Collin Walling writes:
>
>> On 7/24/24 3:56 AM, Markus Armbruster wrote:
>>> Collin Walling writes:
>> Let me try to explain the purpose of @deprecated-props and see if it
>> helps bring us closer to some semblance of a mutual understanding so we
>> can work together
On 25.07.24 09:35, Markus Armbruster wrote:
Markus Armbruster writes:
Collin Walling writes:
On 7/24/24 3:56 AM, Markus Armbruster wrote:
Collin Walling writes:
Let me try to explain the purpose of @deprecated-props and see if it
helps bring us closer to some semblance of a mutual unders
On Sat, 15 Jun 2024 09:45:48 +0800
maobibo wrote:
> On 2024/6/14 下午10:03, Daniel P. Berrangé wrote:
> > On Fri, Jun 14, 2024 at 01:17:39PM +0800, maobibo wrote:
> >>
> >>
> >> On 2024/6/14 下午12:27, Jiaxun Yang wrote:
> >>>
> >>>
> >>> 在2024年6月14日六月 上午4:32,maobibo写道:
> It is interesting
On 7/24/24 23:21, Michael Kowal wrote:
From: Frederic Barrat
Additional END state 'info pic' information as added. The 'ignore',
'crowd' and 'precluded escalation control' bits of an Event Notification
Descriptor are all used when delivering an interrupt targeting a VP-group
or crowd.
Signed-
On 7/24/24 23:21, Michael Kowal wrote:
From: Frederic Barrat
In XIVE Gen 2 there were some minor changes to the TIMA header that were
updated when printed.
Signed-off-by: Frederic Barrat
Signed-off-by: Michael Kowal
Reviewed-by: Cédric Le Goater
Thanks,
C.
---
hw/intc/xive.c | 12
On 7/24/24 23:21, Michael Kowal wrote:
From: Frederic Barrat
Moving xive2_nvp_pic_print_info() to align with the other "pic_print_info"
functions.
Signed-off-by: Frederic Barrat
Signed-off-by: Michael Kowal
Reviewed-by: Cédric Le Goater
Thanks,
C.
---
include/hw/ppc/xive2_regs.h |
On Thu, 13 Jun 2024 18:30:15 +0100
Jiaxun Yang wrote:
> Implement S3 and S4 sleep with ACPI_GED_REG_SLEEP_CTL.SLP_TYP
> writes.
>
> Implement wakeup callback and WAK_STS register to inform guest
> about current states.
>
> All new functions are gated by "slp-typs" property, it is defaulted
> to
On Thu, 13 Jun 2024 18:30:16 +0100
Jiaxun Yang wrote:
> Wire up S3 and S4 sleep by setting relevant slp-typs bits for
> GED and generate _S3 and _S4 methods in acpi table.
>
> Signed-off-by: Jiaxun Yang
> ---
> hw/loongarch/acpi-build.c | 18 ++
> hw/loongarch/virt.c | 3
On Thu, 13 Jun 2024 18:30:14 +0100
Jiaxun Yang wrote:
> Hi all,
>
> This series implemented S3 and S4 sleep for loongarch virt machine
> and microvm.
>
> For loongarch/virt a kernel patch is requried [1].
>
> [1]:
> https://lore.kernel.org/loongarch/20240613-loongarch64-sleep-v1-0-a245232af..
On Thu, Jul 25, 2024 at 10:22:15AM +0200, Igor Mammedov wrote:
> On Thu, 13 Jun 2024 18:30:15 +0100
> Jiaxun Yang wrote:
>
> > Implement S3 and S4 sleep with ACPI_GED_REG_SLEEP_CTL.SLP_TYP
> > writes.
> >
> > Implement wakeup callback and WAK_STS register to inform guest
> > about current states
On Wed, 24 Jul 2024 23:27:31 -0400
Yao Xingtao via wrote:
> Since the downstream port is not checked, two slots can be linked to
> a single port. However, this can prevent the driver from detecting the
> device properly.
>
> It is necessary to ensure that a downstream port is not linked more tha
Zhao Liu writes:
> Hi Markus,
>
> I realized I should reply this mail first...
>
> On Wed, Jul 24, 2024 at 01:35:17PM +0200, Markus Armbruster wrote:
>> Date: Wed, 24 Jul 2024 13:35:17 +0200
>> From: Markus Armbruster
>> Subject: Re: [PATCH 2/8] qapi/qom: Introduce smp-cache object
>>
>> Zhao L
On Thu, 25 Jul 2024 04:30:42 -0400
"Michael S. Tsirkin" wrote:
> On Thu, Jul 25, 2024 at 10:22:15AM +0200, Igor Mammedov wrote:
> > On Thu, 13 Jun 2024 18:30:15 +0100
> > Jiaxun Yang wrote:
> >
> > > Implement S3 and S4 sleep with ACPI_GED_REG_SLEEP_CTL.SLP_TYP
> > > writes.
> > >
> > > Impl
Zhao Liu writes:
> Hi Markus and Daniel,
>
> I have the questions about the -object per cache implementation:
>
> On Wed, Jul 24, 2024 at 02:39:29PM +0200, Markus Armbruster wrote:
>> Date: Wed, 24 Jul 2024 14:39:29 +0200
>> From: Markus Armbruster
>> Subject: Re: [PATCH 8/8] qemu-options: Add t
> -Original Message-
> From: Igor Mammedov
> Sent: Thursday, July 25, 2024 4:36 PM
> To: Yao Xingtao via
> Cc: Yao, Xingtao/姚 幸涛 ; m...@redhat.com;
> marcel.apfelb...@gmail.com
> Subject: Re: [PATCH v3] pci-bridge: avoid linking a single downstream port
> more
> than once
>
> On Wed,
Since the downstream port is not checked, two slots can be linked to
a single port. However, this can prevent the driver from detecting the
device properly.
It is necessary to ensure that a downstream port is not linked more than
once.
Links:
https://lore.kernel.org/qemu-devel/oszpr01mb6453bc61d
Hello Daniel,
On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" wrote:
Many times we see a build job start failing, we wonder if the installed
packages have changed since the last passing build. We can rarely
diagnose this, however, since we only have the new container image, not
the old one.
Mauro Carvalho Chehab writes:
> From: Jonathan Cameron
>
> 1. Some GHES functions require handling addresses. Add a helper function
>to support it.
>
> 2. Add support for ACPI CPER (firmware-first) ARM processor error injection.
>
> Compliance with N.2.4.4 ARM Processor Error Section in UEFI
Il gio 25 lug 2024, 08:19 Manos Pitsidianakis <
manos.pitsidiana...@linaro.org> ha scritto:
> >(before the call to qemu_chr_fe_accept_input):
> >// TODO: this causes a callback that creates another "&mut self".
> >// This is forbidden by Rust aliasing rules and has to be fixed
> >// using interior
On Thu, Jul 25, 2024 at 09:35:22AM +1000, Richard Henderson wrote:
> On 7/25/24 03:52, Thomas Huth wrote:
> > The Avocado v88 that we use in QEMU is already on a life support
> > system: It is not supported by upstream anymore, and with the latest
> > versions of Python, it won't work anymore since
Hi Michael, thanks for the review!
On Thu, 2024-07-25 at 01:48 -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 24, 2024 at 06:16:37PM +0100, David Woodhouse wrote:
> > From: David Woodhouse
> >
> > The vmclock "device" provides a shared memory region with precision clock
> > information. By using
On 25/07/2024 11.42, Manos Pitsidianakis wrote:
Hello Daniel,
On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" wrote:
Many times we see a build job start failing, we wonder if the installed
packages have changed since the last passing build. We can rarely
diagnose this, however, since we only h
On Thu, 2024-07-25 at 01:54 -0400, Michael S. Tsirkin wrote:
> one other thing worth mentioning is that this design can't work
> with confidential computing setups. By comparison, mapping e.g. a
> range in a PCI BAR would work for these setups.
Why so? This is just like mapping a PCI BAR, isn't it
On Thu, Jul 25, 2024 at 12:42:18PM +0300, Manos Pitsidianakis wrote:
> Hello Daniel,
>
> On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" wrote:
> > Many times we see a build job start failing, we wonder if the installed
> > packages have changed since the last passing build. We can rarely
> > dia
Mauro Carvalho Chehab writes:
> Enrich CPER error injection logic for ARM processor to allow
> setting values to from UEFI 2.10 tables N.16 and N.17.
>
> It should be noticed that, with such change, all arguments are
> now optional, so, once QMP is negotiated with:
>
> { "execute": "qmp_ca
On Tue, 23 Jul 2024 at 08:03, Konstantin Kostiuk wrote:
>
> 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-
On 25/07/2024 01.35, Richard Henderson wrote:
On 7/25/24 03:52, Thomas Huth wrote:
The Avocado v88 that we use in QEMU is already on a life support
system: It is not supported by upstream anymore, and with the latest
versions of Python, it won't work anymore since it depends on the
"imp" module
Manos Pitsidianakis writes:
> Hello Daniel,
>
> On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" wrote:
>>Many times we see a build job start failing, we wonder if the installed
>>packages have changed since the last passing build. We can rarely
>>diagnose this, however, since we only have the ne
On Thu, 25 Jul 2024 12:50, Paolo Bonzini wrote:
Il gio 25 lug 2024, 08:19 Manos Pitsidianakis <
manos.pitsidiana...@linaro.org> ha scritto:
>(before the call to qemu_chr_fe_accept_input):
>// TODO: this causes a callback that creates another "&mut self".
>// This is forbidden by Rust aliasing
On Tue, 23 Jul 2024 at 15:17, Paolo Bonzini wrote:
>
> From: Anthony Harivel
>
> Starting with the "Sandy Bridge" generation, Intel CPUs provide a RAPL
> interface (Running Average Power Limit) for advertising the accumulated
> energy consumption of various power domains (e.g. CPU packages, DRAM,
On Thu, 25 Jul 2024 12:56, Thomas Huth wrote:
On 25/07/2024 11.42, Manos Pitsidianakis wrote:
Hello Daniel,
On Wed, 24 Jul 2024 12:55, "Daniel P. Berrangé" wrote:
Many times we see a build job start failing, we wonder if the installed
packages have changed since the last passing build. We ca
LIU Zhiwei writes:
> make check-avocado AVOCADO_TESTS=tests/avocado/tuxrun_baselines.py: \
> TuxRunBaselineTest:test_riscv64_rv32
>
> Signed-off-by: LIU Zhiwei
> Suggested-by: Daniel Henrique Barboza
Acked-by: Alex Bennée
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
On Tue, 23 Jul 2024 at 15:16, Paolo Bonzini wrote:
>
> From: Anthony Harivel
>
> Introduce a privileged helper to access RAPL MSR.
Hi; Coverity points out an issue with this commit
(CID 1558555):
> +static void coroutine_fn vh_co_entry(void *opaque)
> +{
> +VMSRHelperClient *client = opaqu
On Thu, Jul 25, 2024 at 12:28 PM Peter Maydell wrote:
> > +if (r < 0) {
> > +error_report_err(local_err);
> > +goto out;
>
> Here we have a check for r < 0 that forces an early exit...
>
> > +}
> > +
> > +while (r < 0) {
>
> ...but then immediately we do a while (r < 0)
On Tue, 23 Jul 2024 at 11:58, Michael S. Tsirkin wrote:
>
> From: Salil Mehta
>
> KVM vCPU creation is done once during the vCPU realization when Qemu vCPU
> thread
> is spawned. This is common to all the architectures as of now.
>
> Hot-unplug of vCPU results in destruction of the vCPU object i
On 7/25/24 19:55, Daniel P. Berrangé wrote:
On Thu, Jul 25, 2024 at 09:35:22AM +1000, Richard Henderson wrote:
On 7/25/24 03:52, Thomas Huth wrote:
The Avocado v88 that we use in QEMU is already on a life support
system: It is not supported by upstream anymore, and with the latest
versions of P
On 7/25/24 20:13, Thomas Huth wrote:
Hi Richard,
just for my understanding, did you try to run the tests in parallel (i.e. something like
"make -j$(nproc)")?
No, I ran "make check-functional" with zero parallelism.
For me, it works fine if I use normal serial testing with "-j" (btw. Avocad
On Thu, 25 Jul 2024 11:50:59 +0100
Jonathan Cameron wrote:
Resending as this bounced due (I think) to an address typo.
> Hi Markus, Zhao Liu
>
> From the ARM server side this is something I want to see as well.
> So I can comment on why we care.
>
> > >> This series adds a way to configure cac
On Thu, Jul 25, 2024 at 08:42:31PM +1000, Richard Henderson wrote:
> On 7/25/24 19:55, Daniel P. Berrangé wrote:
> > On Thu, Jul 25, 2024 at 09:35:22AM +1000, Richard Henderson wrote:
> > > On 7/25/24 03:52, Thomas Huth wrote:
> > > > The Avocado v88 that we use in QEMU is already on a life support
On Thu, Jul 25, 2024 at 12:14 PM Manos Pitsidianakis
wrote:
> >Unfortunately that's a *mut, not a &mut. A &mut must be unique, so the cast
> >in pl011_read() is undefined behavior.
>
> Actually it's:
>
> unsafe { qemu_chr_fe_accept_input(&mut self.char_backend) };
>
> And you can ensure there's
Hi,
Just a bunch of 'nits below
On 7/24/24 19:16, David Woodhouse wrote:
diff --git a/drivers/ptp/ptp_vmclock.c b/drivers/ptp/ptp_vmclock.c
new file mode 100644
index ..9c508c21c062
--- /dev/null
+++ b/drivers/ptp/ptp_vmclock.c
[...]
+/*
+ * Multiply a 64-bit count by a 64-bit t
On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> Hi Michael, thanks for the review!
>
> On Thu, 2024-07-25 at 01:48 -0400, Michael S. Tsirkin wrote:
> > On Wed, Jul 24, 2024 at 06:16:37PM +0100, David Woodhouse wrote:
> > > From: David Woodhouse
> > >
> > > The vmclock "device"
Guoyi Tu writes:
> In the test environment, we conducted IO stress tests on all storage disks
> within a virtual machine that had five storage devices mounted.During
> testing,
> we found that the qemu process allocated a large amount of memory (~800MB)
> to handle these IO operations.
>
> When
Hi Markus,
On Thu, Jul 25, 2024 at 10:51:49AM +0200, Markus Armbruster wrote:
[snip]
> >> What's the use case? The commit messages don't tell.
> >
> > i386 has the default cache topology model: l1 per core/l2 per core/l3
> > per die.
> >
> > Cache topology affects scheduler performance, e.g., k
On 7/24/24 10:07 AM, Philippe Mathieu-Daudé wrote:
The 'any' CPU is deprecated since commit f57d5f8004b
("target/riscv: deprecate the 'any' CPU type"). Users
are better off using the default CPUs or the 'max' CPU.
Signed-off-by: Philippe Mathieu-Daudé
---
docs/about/deprecated.rst |
Thanks Jonathon!
On Thu, Jul 25, 2024 at 11:59:02AM +0100, Jonathan Cameron wrote:
[snip]
> > > I think I understand why you want to configure caches. My question was
> > > about the connection to SMP.
> > >
> > > Say we run a guest with a single core, no SMP. Could configuring caches
> > > s
On 23/7/24 15:10, Peter Maydell wrote:
The documentation of the "Set palette" mailbox property at
https://github.com/raspberrypi/firmware/wiki/Mailbox-property-interface#set-palette
says it has the form:
Length: 24..1032
Value:
u32: offset: first palette index to set (0-255)
On Thu, 2024-07-25 at 13:20 +0200, Paolo Abeni wrote:
>
>
> Just a bunch of 'nits below
Thank you. Fixed in
https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/vmclock
I'll post a new version once I've finished resolving mst's and any
other feedback.
smime.p7s
Description: S/
On 24/7/24 19:52, Thomas Huth wrote:
Some Avocado-based tests use the "archive" module from avocado.utils
to extract files from an archive. To be able to use these tests
without Avocado, we have to provide our own function for extracting
files. Fortunately, there is already the tarfile module tha
On Thu, 2024-07-25 at 12:31 +0100, Daniel P. Berrangé wrote:
> On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > Hi Michael, thanks for the review!
> >
> > On Thu, 2024-07-25 at 01:48 -0400, Michael S. Tsirkin wrote:
> > > Do you want to just help complete virtio-rtc then? Would
On 24/7/24 19:52, Thomas Huth wrote:
Nothing thrilling in here, just straight forward conversions.
Signed-off-by: Thomas Huth
---
MAINTAINERS | 8 ++--
tests/functional/meson.build | 10 +
.../test_ppc64_powernv.py}
On 25/7/24 08:55, Philippe Mathieu-Daudé wrote:
Hi Thomas,
On 24/7/24 19:52, Thomas Huth wrote:
These test are rather simple and don't need any modifications apart
from adjusting the "from avocado_qemu" line. To ease debugging, make
the files executable and add a shebang line and Python '__main
On Thu, Jul 25, 2024 at 01:35:21PM +0200, Markus Armbruster wrote:
> Guoyi Tu writes:
>
> > In the test environment, we conducted IO stress tests on all storage disks
> > within a virtual machine that had five storage devices mounted.During
> > testing,
> > we found that the qemu process allocat
On 24/7/24 19:52, Thomas Huth wrote:
These test are rather simple and don't need any modifications apart
from adjusting the "from avocado_qemu" line. To ease debugging, make
the files executable and add a shebang line and Python '__main__'
handling, too, so that these tests can now be run by exec
On 24/7/24 19:52, Thomas Huth wrote:
The next patch is going to add some entries that need more space between
the command and the help text, so let's increase the indentation here
first.
Signed-off-by: Thomas Huth
---
tests/Makefile.include | 30 +++---
1 file changed
On Thu, Jul 25, 2024 at 12:53:34PM +0100, David Woodhouse wrote:
> On Thu, 2024-07-25 at 12:31 +0100, Daniel P. Berrangé wrote:
> > On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > > Hi Michael, thanks for the review!
> > >
> > > On Thu, 2024-07-25 at 01:48 -0400, Michael S. Ts
On 24/7/24 19:52, Thomas Huth wrote:
These simple tests can be converted to stand-alone tests quite easily,
e.g. by just setting the machine to 'none' now manually or by adding
"-cpu" command line parameters, since we don't support the corresponding
avocado tags in the new python test framework.
On 24/7/24 19:52, Thomas Huth wrote:
Now that we've got a working fetch_asset() function, we can convert
some Avocado tests that use this function for downloading their
required files.
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Thomas Huth
---
MAINTAINERS
HI Peter,
> From: Peter Maydell
> Sent: Thursday, July 25, 2024 11:36 AM
> To: Michael S. Tsirkin
>
> On Tue, 23 Jul 2024 at 11:58, Michael S. Tsirkin wrote:
> >
> > From: Salil Mehta
> >
> > KVM vCPU creation is done once during the vCPU realization when Qemu
> > vCPU thread is spa
On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > Do you want to just help complete virtio-rtc then? Would be easier than
> > trying to keep two specs in sync.
>
> The ACPI version is much more lightweight and doesn't take up a
> valuable PCI slot#. (I know, you can do virtio wi
On Thu, 25 Jul 2024 at 13:05, Salil Mehta wrote:
>
> HI Peter,
>
> > From: Peter Maydell
> > Sent: Thursday, July 25, 2024 11:36 AM
> > To: Michael S. Tsirkin
> >
> > On Tue, 23 Jul 2024 at 11:58, Michael S. Tsirkin wrote:
> > >
> > > From: Salil Mehta
> > >
> > > KVM vCPU creation is
On Thu, 2024-07-25 at 08:17 -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > > Do you want to just help complete virtio-rtc then? Would be easier than
> > > trying to keep two specs in sync.
> >
> > The ACPI version is much more lightweight an
On Thu, Jul 25, 2024 at 01:27:49PM +0100, David Woodhouse wrote:
> On Thu, 2024-07-25 at 08:17 -0400, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > > > Do you want to just help complete virtio-rtc then? Would be easier than
> > > > trying to keep
On Thu, 2024-07-25 at 08:29 -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 25, 2024 at 01:27:49PM +0100, David Woodhouse wrote:
> > On Thu, 2024-07-25 at 08:17 -0400, Michael S. Tsirkin wrote:
> > > On Thu, Jul 25, 2024 at 10:56:05AM +0100, David Woodhouse wrote:
> > > > > Do you want to just help
On Thu, Jul 25, 2024 at 01:31:19PM +0100, David Woodhouse wrote:
> On Thu, 2024-07-25 at 08:29 -0400, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2024 at 01:27:49PM +0100, David Woodhouse wrote:
> > > On Thu, 2024-07-25 at 08:17 -0400, Michael S. Tsirkin wrote:
> > > > On Thu, Jul 25, 2024 at 10:
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Thu, Jul 25, 2024 at 01:35:21PM +0200, Markus Armbruster wrote:
> > Guoyi Tu writes:
> >
> > > In the test environment, we conducted IO stress tests on all storage disks
> > > within a virtual machine that had five storage devices mounted.Dur
On 7/18/24 1:37 AM, Alistair Francis wrote:
On Tue, Jul 9, 2024 at 3:37 AM Daniel Henrique Barboza
wrote:
From: Tomasz Jeznach
The RISC-V IOMMU specification is now ratified as-per the RISC-V
international process. The latest frozen specifcation can be found at:
https://github.com/riscv-
On Thu, 2024-07-25 at 08:33 -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 25, 2024 at 01:31:19PM +0100, David Woodhouse wrote:
> > On Thu, 2024-07-25 at 08:29 -0400, Michael S. Tsirkin wrote:
> > > On Thu, Jul 25, 2024 at 01:27:49PM +0100, David Woodhouse wrote:
> > > > On Thu, 2024-07-25 at 08:17
Open
Implementing a RamDiscardManager to notify VFIO of page conversions
causes changes in semantics: private memory is treated as discarded (or
hot-removed) memory. This isn't aligned with the expectation of current
RamDiscardManager users (e.g. VFIO or live migration) who really
expect that
On Sat, 20 Jul 2024 at 16:19, Peter Maydell wrote:
>
> On Thu, 18 Jul 2024 at 03:15, Alistair Francis wrote:
> >
> > From: Atish Patra
> >
> > The timer is setup function is invoked in both hpmcounter
> > write and mcountinhibit write path. If the OF bit set, the
> > LCOFI interrupt is disabled.
On Thu, Jul 25, 2024 at 02:50:50PM +0100, David Woodhouse wrote:
> Even if the virtio-rtc specification were official today, and I was
> able to expose it via PCI, I probably wouldn't do it that way. There's
> just far more in virtio-rtc than we need; the simple shared memory
> region is perfectly
On Tue, 19 Dec 2023 at 13:36, Peter Maydell wrote:
>
> On Thu, 2 Mar 2023 at 12:37, Paolo Bonzini wrote:
> >
> > From: David Woodhouse
> >
> > The way that Xen handles MSI PIRQs is kind of awful.
> >
> > There is a special MSI message which targets a PIRQ. The vector in the
> > low bits of data
On Tue, Jul 16, 2024 at 7:28 AM Thomas Huth wrote:
>
> The Avocado v88 that we use in QEMU is already on a life support
> system: It is not supported by upstream anymore, and with the latest
> versions of Python, it won't work anymore since it depends on the
> "imp" module that has been removed in
Hi Richard,
On 7/24/24 7:14 AM, Richard Henderson wrote:
On 7/23/24 02:07, Gustavo Romero wrote:
+ /* Find out the current translation regime for probe. */
+ mmu_index = arm_mmu_idx(env) & ARM_MMU_IDX_COREIDX_MASK;
The official interface is cpu_mmu_index().
Otherwise,
Reviewed-by: Rich
On Mon, 22 Jul 2024 at 11:35, Mostafa Saleh wrote:
>
> Coverity has spotted a possible problem with the OAS handling
> (CID 1558464), where the error return of oas2bits() -1 is not
> checked, which can cause an overflow in oas value.
>
> oas2bits() is only called with valid inputs, harden the func
On Mon, 22 Jul 2024 at 10:44, Peter Maydell wrote:
>
> [Added missing cc of qemu-devel]
>
> On Mon, 22 Jul 2024 at 07:33, Philippe Mathieu-Daudé
> wrote:
> >
> > On 21/7/24 18:13, ~fvanhovell wrote:
> > > From: Frederik van Hövell
> > >
> > > When a bare-metal application on the raspi3 board re
On Thu, 25 Jul 2024 at 14:19, Paolo Bonzini wrote:
>
> On Thu, Jul 25, 2024 at 12:14 PM Manos Pitsidianakis
> wrote:
> > >Unfortunately that's a *mut, not a &mut. A &mut must be unique, so the cast
> > >in pl011_read() is undefined behavior.
> >
> > Actually it's:
> >
> > unsafe { qemu_chr_fe_a
Loop should exit prematurely on successfully finding out the parked vCPU (struct
KVMParkedVcpu) in the 'struct KVMState' maintained 'kvm_parked_vcpus' list of
parked vCPUs.
Fixes: Coverity CID 1558552
Fixes: 08c3286822 ("accel/kvm: Extract common KVM vCPU {creation,parking} code")
Reported-by: Pet
Hi Peter,
> From: Peter Maydell
> Sent: Thursday, July 25, 2024 1:27 PM
> To: Salil Mehta
>
> On Thu, 25 Jul 2024 at 13:05, Salil Mehta wrote:
> >
> > HI Peter,
> >
> > > From: Peter Maydell
> > > Sent: Thursday, July 25, 2024 11:36 AM
> > > To: Michael S. Tsirkin
> > >
> > >
In Gitlab CI, some ppc64 multi-threaded tcg tests crash when run in the
clang-user job with an assertion failure in glibc that seems to
indicate corruption:
signals: allocatestack.c:223: allocate_stack:
Assertion `powerof2 (pagesize_m1 + 1)' failed.
Disable these tests on CI for now.
Signe
On Thu, 25 Jul 2024 at 16:00, Nicholas Piggin wrote:
>
> In Gitlab CI, some ppc64 multi-threaded tcg tests crash when run in the
> clang-user job with an assertion failure in glibc that seems to
> indicate corruption:
>
> signals: allocatestack.c:223: allocate_stack:
> Assertion `powerof2 (p
On Mon, 22 Jul 2024 at 08:00, Xingtao Yao (Fujitsu) via
wrote:
>
>
>
> > -Original Message-
> > From: Philippe Mathieu-Daudé
> > Sent: Monday, July 22, 2024 2:43 PM
> > To: Yao, Xingtao/姚 幸涛 ; qemu-devel@nongnu.org
> > Subject: Re: [PATCH 00/13] make range overlap check more readable
> >
On Thu, Jul 25, 2024 at 4:48 PM Manos Pitsidianakis
wrote:
> > pl011_receive (called by qemu_chr_fe_accept_input) creates a mutable
> > reference that *overlaps* the lifetime of the outer reference created
> > by pl011_read. This is undefined behavior. You're effectively writing:
>
> There is no o
On Thu, 2024-07-25 at 10:11 -0400, Michael S. Tsirkin wrote:
> On Thu, Jul 25, 2024 at 02:50:50PM +0100, David Woodhouse wrote:
> > Even if the virtio-rtc specification were official today, and I was
> > able to expose it via PCI, I probably wouldn't do it that way. There's
> > just far more in vir
In Gitlab CI, some ppc64 multi-threaded tcg tests crash when run in the
clang-user job with an assertion failure in glibc that seems to
indicate corruption:
signals: allocatestack.c:223: allocate_stack:
Assertion `powerof2 (pagesize_m1 + 1)' failed.
Disable these tests for now.
Signed-off-
On Thu, Jul 25, 2024 at 04:18:43PM +0100, David Woodhouse wrote:
> On Thu, 2024-07-25 at 10:11 -0400, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2024 at 02:50:50PM +0100, David Woodhouse wrote:
> > > Even if the virtio-rtc specification were official today, and I was
> > > able to expose it via
In append_stats_line(), we have an expression
l2_access ? l2_miss_rate : 0.0
But this is inside an if (l2_access && l2_misses) { ... } block,
so Coverity points out that the false part of the ?: is dead code.
Remove the unnecessary test.
Resolves: Coverity CID 1522458
Signed-off-by: Peter Mayd
On Wed, 24 Jul 2024 07:53:48 +0300
Michael Tokarev wrote:
> 05.07.2024 14:39, Jonathan Cameron via wrote:
> > From: Zhao Liu
> >
> > QEMU crashes (Segmentation fault) when getting cxl-fmw property via
> > qmp:
> >
> > (QEMU) qom-get path=machine property=cxl-fmw
> >
> > This issue is caused b
On 7/25/24 3:39 AM, David Hildenbrand wrote:
> On 25.07.24 09:35, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>>> Collin Walling writes:
>>>
On 7/24/24 3:56 AM, Markus Armbruster wrote:
> Collin Walling writes:
Let me try to explain the purpose of @deprecated-props and
1 - 100 of 278 matches
Mail list logo