Re: [PATCH 0/2] hw/ufs: Add temperature event support and test cases

On 2/25/2025 3:40 PM, Keoseong Park wrote: This patch series introduces temperature event notification support in the UFS emulation and adds corresponding test cases to validate the feature. The first patch enables the UFS emulation to generate temperature-related events, including high and lo

Re: [PATCH v17 11/11] hw/vmapple/vmapple: Add vmapple machine type

On 3/3/25 21:36, Phil Dennis-Jordan wrote: On Mon, 3 Mar 2025 at 19:20, Philippe Mathieu-Daudé > wrote: On 12/1/25 22:00, Phil Dennis-Jordan wrote: > From: Alexander Graf mailto:g...@amazon.com>> > > Apple defines a new "vmapple" machine type as pa

Re: [PATCH v17 11/11] hw/vmapple/vmapple: Add vmapple machine type

On 12/1/25 22:00, Phil Dennis-Jordan wrote: From: Alexander Graf Apple defines a new "vmapple" machine type as part of its proprietary macOS Virtualization.Framework vmm. This machine type is similar to the virt one, but with subtle differences in base devices, a few special vmapple device addi

Re: [PATCH v17 11/11] hw/vmapple/vmapple: Add vmapple machine type

On Mon, 3 Mar 2025 at 19:20, Philippe Mathieu-Daudé wrote: > On 12/1/25 22:00, Phil Dennis-Jordan wrote: > > From: Alexander Graf > > > > Apple defines a new "vmapple" machine type as part of its proprietary > > macOS Virtualization.Framework vmm. This machine type is similar to the > > virt one

Re: [PATCH v17 04/11] hw/misc/pvpanic: Add MMIO interface

On Mon, 3 Mar 2025 at 18:54, Philippe Mathieu-Daudé wrote: > On 12/1/25 22:00, Phil Dennis-Jordan wrote: > > From: Alexander Graf > > > > In addition to the ISA and PCI variants of pvpanic, let's add an MMIO > > platform device that we can use in embedded arm environments. > > > > Signed-off-by:

Re: [PATCH v17 11/11] hw/vmapple/vmapple: Add vmapple machine type

On 3/3/25 19:20, Philippe Mathieu-Daudé wrote: On 12/1/25 22:00, Phil Dennis-Jordan wrote: From: Alexander Graf Apple defines a new "vmapple" machine type as part of its proprietary macOS Virtualization.Framework vmm. This machine type is similar to the virt one, but with subtle differences in

Re: [PATCH v17 11/11] hw/vmapple/vmapple: Add vmapple machine type

On 12/1/25 22:00, Phil Dennis-Jordan wrote: From: Alexander Graf Apple defines a new "vmapple" machine type as part of its proprietary macOS Virtualization.Framework vmm. This machine type is similar to the virt one, but with subtle differences in base devices, a few special vmapple device addi

Re: [PATCH v17 04/11] hw/misc/pvpanic: Add MMIO interface

On 12/1/25 22:00, Phil Dennis-Jordan wrote: From: Alexander Graf In addition to the ISA and PCI variants of pvpanic, let's add an MMIO platform device that we can use in embedded arm environments. Signed-off-by: Alexander Graf Reviewed-by: Philippe Mathieu-Daudé Tested-by: Philippe Mathieu-D

Re: [PATCH v17 03/11] hw: Add vmapple subdir

On 12/1/25 22:00, Phil Dennis-Jordan wrote: From: Alexander Graf We will introduce a number of devices that are specific to the vmapple target machine. To keep them all tidily together, let's put them into a single target directory. Signed-off-by: Alexander Graf Signed-off-by: Phil Dennis-Jor

Re: [PATCH v17 00/11] New vmapple machine type and xhci fixes

On 15/1/25 16:40, Michael S. Tsirkin wrote: On Wed, Jan 15, 2025 at 04:33:45PM +0100, Phil Dennis-Jordan wrote: On Wed, 15 Jan 2025 at 16:08, Michael S. Tsirkin wrote: On Sun, Jan 12, 2025 at 10:00:45PM +0100, Phil Dennis-Jordan wrote: > This patch set introduces a new ARM and macO

Re: [PATCH] blockdev-backup: Add error handling option for copy-before-write jobs

On Mon, Mar 03, 2025 at 02:35:10PM +0100, Raman Dzehtsiar wrote: > This patch extends the blockdev-backup QMP command to allow users to specify > how to behave when IO errors occur during copy-before-write operations. > Previously, the behavior was fixed and could not be controlled by the user. >

[PATCH] blockdev-backup: Add error handling option for copy-before-write jobs

This patch extends the blockdev-backup QMP command to allow users to specify how to behave when IO errors occur during copy-before-write operations. Previously, the behavior was fixed and could not be controlled by the user. The new 'on-cbw-error' option can be set to one of two values: - 'break-g

Re: [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers

On Mon, 3 Mar 2025, Bernhard Beschow wrote: Am 1. März 2025 16:02:05 UTC schrieb BALATON Zoltan : On Mon, 10 Feb 2025, BALATON Zoltan wrote: The interrupt enable registers are not reset to 0 on Freescale eSDHC but some bits are enabled on reset. At least some U-Boot versions seem to expect this

Re: [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers

Hi Zoltan, On 10/2/25 17:03, BALATON Zoltan wrote: The interrupt enable registers are not reset to 0 on Freescale eSDHC but some bits are enabled on reset. At least some U-Boot versions seem to expect this and not initialise these registers before expecting interrupts. Use existing vendor proper

Re: [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers

On Mon, 3 Mar 2025, Philippe Mathieu-Daudé wrote: Hi Zoltan, On 10/2/25 17:03, BALATON Zoltan wrote: The interrupt enable registers are not reset to 0 on Freescale eSDHC but some bits are enabled on reset. At least some U-Boot versions seem to expect this and not initialise these registers befo

Re: [PATCH] usb-storage: Allow manually adding SCSI device

On 3/3/25 11:28, Akihiko Odaki wrote: usb-storage automatically adds a SCSI device, but it limits configurability of the added SCSI device and causes usability problems as observed in: https://gitlab.com/libvirt/libvirt/-/issues/368 Allow manually adding SCSI device when the drive option is not

Re: [PATCH v2] iotest: Unbreak 302 with python 3.13

On Fri, Feb 28, 2025 at 09:57:08PM +0200, Nir Soffer wrote: > This test depends on TarFile.addfile() to add tar member header without > writing the member data, which we write ourself using qemu-nbd. Python > 3.13 changed the function in a backward incompatible way[1] to require a > file object for

Re: [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers

Am 1. März 2025 16:02:05 UTC schrieb BALATON Zoltan : >On Mon, 10 Feb 2025, BALATON Zoltan wrote: >> The interrupt enable registers are not reset to 0 on Freescale eSDHC >> but some bits are enabled on reset. At least some U-Boot versions seem >> to expect this and not initialise these registers