There's no code using MTYPE, which was a concept used in older vector
implementation.
Signed-off-by: Xiao Wang
---
target/riscv/vector_helper.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/target/riscv/vector_helper.c b/target/riscv/vector_helper.c
index
On Tue, Jun 06, 2023 at 07:03:45PM +,
Ackerley Tng wrote:
> Hello,
>
> This patchset builds upon a soon-to-be-published WIP patchset that Sean
> published at https://github.com/sean-jc/linux/tree/x86/kvm_gmem_solo,
> mentioned
> at [1].
>
> The tree can be found at:
>
After suspending and resuming guest VM, you will get
a black screen, and the display can't come back.
This is because when guest did suspending, it called
into qemu to call virtio_gpu_gl_reset. In function
virtio_gpu_gl_reset, it destroyed resources and reset
renderer, which were used for
From: Hyman Huang(黄勇)
Introduce "x-vcpu-dirty-limit-period" migration experimental
parameter, which is in the range of 1 to 1000ms and used to
make dirtyrate calculation period configurable.
Currently with the "x-vcpu-dirty-limit-period" varies, the
total time of live migration changes, test
From: Hyman Huang(黄勇)
Introduce "vcpu-dirty-limit" migration parameter used
to limit dirty page rate during live migration.
"vcpu-dirty-limit" and "x-vcpu-dirty-limit-period" are
two dirty-limit-related migration parameters, which can
be set before and during live migration by qmp
Hi all,
I am working to implement virtgpu S3 function on Xen.
Currently on Xen, if we start a guest who enables virtgpu, and then
run "echo mem > /sys/power/state" to suspend guest. And run
"sudo xl trigger s3resume" to resume guest. We can find that
the guest kernel comes back, but the display
From: Hyman Huang(黄勇)
Extend query-migrate to provide throttle time and estimated
ring full time with dirty-limit capability enabled, through which
we can observe if dirty limit take effect during live migration.
Signed-off-by: Hyman Huang(黄勇)
Signed-off-by: Markus Armbruster
---
I'm awfully sorry about having not updated the patchset for a long time.
I have changed my email address to "yong.hu...@smartx.com", and
this email address will used to post the unfinished commits in the
further.
I have dropped the performance improvement data, please refer to the
following link
From: Hyman Huang(黄勇)
Implement dirty-limit convergence algo for live migration,
which is kind of like auto-converge algo but using dirty-limit
instead of cpu throttle to make migration convergent.
Enable dirty page limit if dirty_rate_high_cnt greater than 2
when dirty-limit capability
From: Hyman Huang(黄勇)
Add migration dirty-limit capability test if kernel support
dirty ring.
Migration dirty-limit capability introduce dirty limit
capability, two parameters: x-vcpu-dirty-limit-period and
vcpu-dirty-limit are introduced to implement the live
migration with dirty limit.
The
From: Hyman Huang(黄勇)
dirty_rate paraemter of hmp command "set_vcpu_dirty_limit" is invalid
if less than 0, so add parameter check for it.
Note that this patch also delete the unsolicited help message and
clean up the code.
Signed-off-by: Hyman Huang(黄勇)
Signed-off-by: Markus Armbruster
From: Hyman Huang(黄勇)
Introduce migration dirty-limit capability, which can
be turned on before live migration and limit dirty
page rate durty live migration.
Introduce migrate_dirty_limit function to help check
if dirty-limit capability enabled during live migration.
Meanwhile, refactor
From: Hyman Huang(黄勇)
Check if block migration is running before throttling
guest down in auto-converge way.
Note that this modification is kind of like code clean,
because block migration does not depend on auto-converge
capability, so the order of checks can be adjusted.
Signed-off-by: Hyman
Hi Fan,
I am implementing DCD FMAPI commands and planning to start pushing changes
to the below branch. That requires the contributions you have made. Can your
changes be pushed to the below branch ?
https://gitlab.com/jic23/qemu/-/tree/cxl-2023-05-25
From: Fan Ni
Sent: Monday, June 5,
Damien Le Moal 于2023年6月8日周四 09:29写道：
>
> On 6/8/23 03:57, Sam Li wrote:
> > If the write operation fails and the wps is NULL, then accessing it will
> > lead to data corruption.
> >
> > Solving the issue by adding a nullptr checking in get_zones_wp() where
> > the wps is used.
> >
> > This issue
On Wed, Jun 07, 2023 at 04:51:07PM +0200, Igor Mammedov wrote:
> Date: Wed, 7 Jun 2023 16:51:07 +0200
> From: Igor Mammedov
> Subject: Re: [PATCH v2 3/3] hw/smbios: Fix core count in type4
> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-redhat-linux-gnu)
>
> On Thu, 1 Jun 2023 17:29:52 +0800
On Wed, Jun 07, 2023 at 04:49:34PM +0200, Igor Mammedov wrote:
> Date: Wed, 7 Jun 2023 16:49:34 +0200
> From: Igor Mammedov
> Subject: Re: [PATCH v2 2/3] hw/smbios: Fix thread count in type4
> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-redhat-linux-gnu)
>
> On Thu, 1 Jun 2023 17:29:51
On Wed, Jun 07, 2023 at 04:35:03PM +0200, Igor Mammedov wrote:
> Date: Wed, 7 Jun 2023 16:35:03 +0200
> From: Igor Mammedov
> Subject: Re: [PATCH v2 1/3] hw/smbios: Fix smbios_smp_sockets caculation
> X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-redhat-linux-gnu)
Hi Igor,
>
> On Thu, 1 Jun
On 6/8/23 03:57, Sam Li wrote:
> If the write operation fails and the wps is NULL, then accessing it will
> lead to data corruption.
>
> Solving the issue by adding a nullptr checking in get_zones_wp() where
> the wps is used.
>
> This issue is found by Peter Maydell using the Coverity Tool (CID
On Wed, Jun 7, 2023 at 5:46 AM Thomas Huth wrote:
>
> On 07/06/2023 11.42, Thomas Huth wrote:
> >
> > Hi Paolo, hi John,
> >
> > since the recent reworks with the Python venv, building of the docs does not
> > work for me on my RHEL 8 installation anymore.
> >
> > If I just run "configure"
On 7/6/23 17:29, Marcin Juszkiewicz wrote:
W dniu 7.06.2023 o 16:33, Philippe Mathieu-Daudé pisze:
On 30/5/23 17:22, Marcin Juszkiewicz wrote:
Update prebuilt firmware images to have TF-A with FEAT_FGT support
enabled. This allowed us to enable test for "max" cpu in sbsa-ref
machine.
Currently, pc-q35 and pc-i44fx machine models are default to use SMBIOS 2.8
(32-bit entry point). Since SMBIOS 3.0 (64-bit entry point) is now fully
supported since QEMU 7.0, default to use SMBIOS 3.0 for newer machine
models. This is necessary to avoid the following message when launching
a VM
In order to support large number of vcpus, a newer 64-bit SMBIOS
entry point type is needed. Therefore, upgrade the default SMBIOS version
for PC machines to SMBIOS 3.0 for newer systems. Then increase the maximum
number of vCPUs for Q35 models to 1024, which is the limit for KVM.
Changes from
Since KVM_MAX_VCPUS is currently defined to 1024 for x86 as shown in
arch/x86/include/asm/kvm_host.h, update QEMU limits to the same number.
In case KVM could not support the specified number of vcpus, QEMU would
return the following error message:
qemu-system-x86_64: kvm_init_vcpu:
On 7/6/23 17:58, Jagannathan Raman wrote:
Signed-off-by: Jagannathan Raman
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 436b3f0afefd..4a80a385118d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3786,7 +3786,6 @@ F:
On 6/7/2023 3:11 PM, Daniel P. Berrangé wrote:
On Tue, Jun 06, 2023 at 09:49:37PM -0500, Suravee Suthikulpanit wrote:
Into a helper function pc_machine_init_smbios() in preparation for
subsequent code to upgrade default SMBIOS entry point type.
Then, call the helper function from the
On 6/7/2023 8:49 PM, Igor Mammedov wrote:
On Tue, 6 Jun 2023 21:49:38 -0500
Suravee Suthikulpanit wrote:
and use this with the rest of your patch
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index b3d826a83a..c5bab28e9c 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.c
@@ -1859,7 +1859,7 @@
On 6/7/23 10:01, Andrew Jones wrote:
On Tue, May 30, 2023 at 04:46:23PM -0300, Daniel Henrique Barboza wrote:
If we don't set a proper cbom_blocksize|cboz_blocksize in the FDT the
Linux Kernel will fail to detect the availability of the CBOM/CBOZ
extensions, regardless of the contents of the
On pegasos2 which has ACPI as part of VT8231 south bridge the board
firmware writes PM control register by accessing the second byte so
addr will be 1. This wasn't handled correctly and the write went to
addr 0 instead. Remove the acpi_pm1_cnt_write() function which is used
only once and does not
On 6/7/23 08:48, Andrew Jones wrote:
On Tue, May 30, 2023 at 04:46:20PM -0300, Daniel Henrique Barboza wrote:
Let's add KVM user properties for the multi-letter extensions that KVM
currently supports: zicbom, zicboz, zihintpause, zbb, ssaia, sstc,
svinval and svpbmt.
As with the recently
On 6/7/23 09:47, Yeqi Fu wrote:
+/* One unknown opcode for native call */
+#if defined(CONFIG_USER_ONLY) && defined(CONFIG_USER_NATIVE_CALL)
+case 0x1ff:
+uint16_t sig = x86_lduw_code(env, s);
+switch (sig) {
+case NATIVE_MEMCPY:
+
On 6/7/23 09:47, Yeqi Fu wrote:
+void helper_native_memcpy(CPUMIPSState *env)
+{
+CPUState *cs = env_cpu(env);
+NATIVE_FN_W_3W();
+void *ret;
+void *dest = g2h(cs, arg0);
+void *src = g2h(cs, arg1);
+size_t n = (size_t)arg2;
+ret = memcpy(dest, src, n);
+
On 6/7/23 09:47, Yeqi Fu wrote:
+arg0 = *(target_ulong *)g2h(cs, env->regs[R_ESP] + 4); \
+arg1 = *(target_ulong *)g2h(cs, env->regs[R_ESP] + 8); \
+arg2 = *(target_ulong *)g2h(cs, env->regs[R_ESP] + 12);
This is not correct, and will fail on big-endian hosts.
You need to use
Hi Peter, Qianfan,
On Mon, Jun 5, 2023 at 5:31 PM Peter Maydell
wrote:
> On Thu, 1 Jun 2023 at 19:48, Niek Linnenbank
> wrote:
> >
> > Hi Qianfan,
> >
> > Thanks for sending the v5. From my side, I have no further comments on
> the content.
> > So please feel free to add the following to each
If the write operation fails and the wps is NULL, then accessing it will
lead to data corruption.
Solving the issue by adding a nullptr checking in get_zones_wp() where
the wps is used.
This issue is found by Peter Maydell using the Coverity Tool (CID
1512459).
Signed-off-by: Sam Li
---
On 6/7/23 07:36, Vladimir Sementsov-Ogievskiy wrote:
The event is racy: it will not appear in the output if bitmap is
migrated during downtime period of migration and postcopy phase is not
started.
Fixes: ae00aa239847 "iotests: 194: test also migration of dirty bitmap"
Reported-by: Richard
in the Git repository at:
https://xenbits.xen.org/git-http/people/aperard/qemu-dm.git
tags/pull-xen-20230607
for you to fetch changes up to 9000666052f99ed4217e75b73636acae61e6fc2c:
xen-block: fix segv on unrealize (2023-06-07 15:07:10 +0100
at:
https://gitlab.com/jraman/qemu.git tags/pull-vfio-user-20230607
for you to fetch changes up to 7771e8b86335968ee46538d1afd44246e7a062bc:
docs: fix multi-process QEMU documentation (2023-06-07 10:21:53 -0400)
vfio-user: Fix
Please ignore this, wrong subject line. I will resend. - steve
On 6/7/2023 2:37 PM, Steve Sistare wrote:
> Extend the migration URI to support file:. This can be used for
> any migration scenario that does not require a reverse path. It can be used
> as an alternative to 'exec:cat > file' in
Extend the migration URI to support file:. This can be used for
any migration scenario that does not require a reverse path. It can be used
as an alternative to 'exec:cat > file' in minimized containers that do not
contain /bin/sh, and it is easier to use than the fd: URI. It can
be used in HMP
Extend the migration URI to support file:. This can be used for
any migration scenario that does not require a reverse path. It can be used
as an alternative to 'exec:cat > file' in minimized containers that do not
contain /bin/sh, and it is easier to use than the fd: URI. It can
be used in HMP
On Wed, Jun 07, 2023 at 06:13:01PM +, Shesha Bhushan Sreenivasamurthy wrote:
> Hi Fan,
>I am implementing DCD FMAPI commands and planning to start pushing changes
> to the below branch. That requires the contributions you have made. Can your
> changes be pushed to the below branch ?
>
>
The subject lines are confusing: 9/14 enables extended headers in the
server, while this one does not yet enable the headers but is merely a
preliminary step. I'll probably retitle one or the other in v4.
On Wed, May 31, 2023 at 06:26:17PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> On 15.05.23
On Wed, Jun 07, 2023 at 05:36:06PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> The event is racy: it will not appear in the output if bitmap is
> migrated during downtime period of migration and postcopy phase is not
> started.
>
> Fixes: ae00aa239847 "iotests: 194: test also migration of dirty
On Sun, Jun 04, 2023 at 02:16:58PM +0800, Sam Li wrote:
> If the write operation fails and the wps is NULL, then accessing it will
> lead to data corruption.
>
> Solving the issue by adding a nullptr checking in get_zones_wp() where
> the wps is used.
>
> This issue is found by Peter Maydell
On Sun, Jun 04, 2023 at 02:16:57PM +0800, Sam Li wrote:
> The g_file_get_contents() function returns a g_boolean. If it fails, the
> returned value will be 0 instead of -1. Solve the issue by skipping
> assigning ret value.
>
> This issue was found by Matthew Rosato using virtio-blk-{pci,ccw}
On Mon, Jun 05, 2023 at 10:57:00AM +0200, Kevin Wolf wrote:
> This series fixes the deadlock that was observed before commit ad128dff
> ('graph-lock: Disable locking for now'), which just disabled the graph
> lock completely as a workaround to get 8.0.1 stable.
>
> In theory the problem is
On 6/7/2023 11:55 AM, Michael Galaxy wrote:
> Another option could be to expose "-migrate-mode-disable" (instead of enable)
> and just enable all 3 modes by default,
> since we are already required to switch from "normal" mode to a CPR-specific
> mode when it is time to do a live update,
> if
07.06.2023 19:29, Christian Schoenebeck wrote:
The 9p protocol does not specifically define how server shall behave when
client tries to open a special file, however from security POV it does
make sense for 9p server to prohibit opening any special file on host side
in general. A sane Linux 9p
Add a new machine xenpvh which creates a IOREQ server to register/connect with
Xen Hypervisor.
Optional: When CONFIG_TPM is enabled, it also creates a tpm-tis-device, adds a
TPM emulator and connects to swtpm running on host machine via chardev socket
and support TPM functionalities for a guest
Replace g_malloc with g_new and perror with error_report.
Signed-off-by: Vikram Garhwal
Reviewed-by: Stefano Stabellini
Reviewed-by: Paul Durrant
---
hw/xen/xen-hvm-common.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/hw/xen/xen-hvm-common.c
From: Stefano Stabellini
On ARM it is possible to have a functioning xenpv machine with only the
PV backends and no IOREQ server. If the IOREQ server creation fails continue
to the PV backends initialization.
Also, moved the IOREQ registration and mapping subroutine to new function
Add CONFIG_XEN for aarch64 device to support build for ARM targets.
Signed-off-by: Vikram Garhwal
Signed-off-by: Stefano Stabellini
Reviewed-by: Alex Bennée
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index
From: Stefano Stabellini
have_xen_pci_passthrough is only used for Xen x86 VMs.
Signed-off-by: Stefano Stabellini
Reviewed-by: Alex Bennée
---
meson.build | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meson.build b/meson.build
index a61d3e9b06..786c69b06d 100644
--- a/meson.build
+++
From: Stefano Stabellini
This patch does following:
1. creates arch_handle_ioreq() and arch_xen_set_memory(). This is done in
preparation for moving most of xen-hvm code to an arch-neutral location,
move the x86-specific portion of xen_set_memory to arch_xen_set_memory.
Also, move
xen-mapcache.c contains common functions which can be used for enabling Xen on
aarch64 with IOREQ handling. Moving it out from hw/i386/xen to hw/xen to make it
accessible for both aarch64 and x86.
Signed-off-by: Vikram Garhwal
Signed-off-by: Stefano Stabellini
Reviewed-by: Paul Durrant
---
From: Stefano Stabellini
This is done to prepare for enabling xenpv support for ARM architecture.
On ARM it is possible to have a functioning xenpv machine with only the
PV backends and no IOREQ server. If the IOREQ server creation fails,
continue to the PV backends initialization.
From: Stefano Stabellini
In preparation to moving most of xen-hvm code to an arch-neutral location, move:
- shared_vmport_page
- log_for_dirtybit
- dirty_bitmap
- suspend
- wakeup
out of XenIOState struct as these are only used on x86, especially the ones
related to dirty logging.
Updated
Hi,
Rebased and resending the series with latest QEMU as it's been quite sometime.
There is one line code change in patch 04/10. Rest is just rebased with latest.
Also, this series has dependency on following gitlab-ci
patch: https://lists.nongnu.org/archive/html/qemu-devel/2023-06/msg01471.html.
In preparation to moving most of xen-hvm code to an arch-neutral location,
move non IOREQ references to:
- xen_get_vmport_regs_pfn
- xen_suspend_notifier
- xen_wakeup_notifier
- xen_ram_init
towards the end of the xen_hvm_init_pc() function.
This is done to keep the common ioreq functions in one
On 6/7/23 12:49, Joel Stanley wrote:
On Wed, 7 Jun 2023 at 04:40, Cédric Le Goater wrote:
Currently, a set of default flash devices is created at machine init
and drives defined on the QEMU command line are associated to the FMC
and SPI controllers in sequence :
-drive
at:
https://gitlab.com/rth7680/qemu.git tags/pull-ci-20230607
for you to fetch changes up to dcc28ab603f30df5cc8be1f759b423e94ae7d10f:
iotests: fix 194: filter out racy postcopy-active event (2023-06-07 08:36:55
-0700)
Fix TCI
Signed-off-by: Yeqi Fu
---
target/mips/helper.h| 6
target/mips/tcg/meson.build | 1 +
target/mips/tcg/native_helper.c | 55 +
target/mips/tcg/translate.c | 20 +++-
target/mips/tcg/translate.h | 12 +++
5 files changed,
Sounds good.
On Wed, Jun 7, 2023, 18:28 Peter Xu wrote:
> On Wed, Jun 07, 2023 at 09:00:14AM -0300, Fabiano Rosas wrote:
> > >> diff --git a/migration/migration.c b/migration/migration.c
> > >> index e731fc98a1..b3b8345eb2 100644
> > >> --- a/migration/migration.c
> > >> +++
The 9p protocol does not specifically define how server shall behave when
client tries to open a special file, however from security POV it does
make sense for 9p server to prohibit opening any special file on host side
in general. A sane Linux 9p client for instance would never attempt to
open a
Signed-off-by: Yeqi Fu
---
include/qemu/envlist.h | 1 +
linux-user/main.c | 23 +
util/envlist.c | 56 ++
3 files changed, 80 insertions(+)
diff --git a/include/qemu/envlist.h b/include/qemu/envlist.h
index
Signed-off-by: Yeqi Fu
---
common-user/native/libnative.c | 65 ++
include/native/libnative.h | 11 ++
include/native/native-func.h | 11 ++
3 files changed, 87 insertions(+)
create mode 100644 common-user/native/libnative.c
create mode 100644
> On Jun 7, 2023, at 12:44 PM, Stefan Hajnoczi wrote:
>
> On Wed, 7 Jun 2023 at 11:58, Jagannathan Raman wrote:
>>
>> John Johnson doesn't work at Oracle anymore. I tried to contact him to
>> get his updated email address, but I haven't heard anything from him.
>>
>> Jagannathan Raman (1):
Signed-off-by: Yeqi Fu
---
target/arm/helper.c| 47 ++
target/arm/helper.h| 6 +
target/arm/tcg/translate-a64.c | 22
target/arm/tcg/translate.c | 25 +-
target/arm/tcg/translate.h | 19
Signed-off-by: Yeqi Fu
---
Makefile| 4 +++
common-user/native/Makefile.include | 9 ++
common-user/native/Makefile.target | 22 +
configure | 50 +
docs/devel/build-system.rst | 4 +++
This patch introduces a set of feature instructions for native calls
and provides helpers to translate these instructions to corresponding
native functions. A shared library is also implemented, where native
functions are rewritten as feature instructions. At runtime, user
programs load the shared
Signed-off-by: Yeqi Fu
---
target/i386/helper.h | 6 +++
target/i386/tcg/translate.c | 20 +
target/i386/tcg/user/meson.build | 1 +
target/i386/tcg/user/native_helper.c | 65
4 files changed, 92 insertions(+)
create mode
On Wed, 7 Jun 2023 at 11:58, Jagannathan Raman wrote:
>
> John Johnson doesn't work at Oracle anymore. I tried to contact him to
> get his updated email address, but I haven't heard anything from him.
>
> Jagannathan Raman (1):
> maintainers: update maintainers list for vfio-user &
Hi Paolo,
Can I get an RB from you on this patch, since you maintain posix?
This is needed for live update, to preserve vfio device descriptors and
character device descriptors across the exec of the new qemu binary.
If yes, I will rebase to the tip and repost a V3.
- Steve
On 2/7/2023 2:03
On 2023/6/7 17:16, Xiao Wang wrote:
Commit 752614cab8e6 ("target/riscv: rvv: Add tail agnostic for vector
load / store instructions") added an extra check for LMUL fragmentation,
intended for setting the "rest tail elements" in the last register for a
segment load insn.
Actually, the
On Tue, 6 Jun 2023 21:49:37 -0500
Suravee Suthikulpanit wrote:
> Into a helper function pc_machine_init_smbios() in preparation for
> subsequent code to upgrade default SMBIOS entry point type.
>
> Then, call the helper function from the pc_machine_initfn() to eliminate
> duplicate code in
From: Vladimir Sementsov-Ogievskiy
The event is racy: it will not appear in the output if bitmap is
migrated during downtime period of migration and postcopy phase is not
started.
Fixes: ae00aa239847 "iotests: 194: test also migration of dirty bitmap"
Reported-by: Richard Henderson
On Wed, Jun 07, 2023 at 06:01:17PM +0200, Niklas Cassel wrote:
> On Mon, Jun 05, 2023 at 08:19:43PM -0400, John Snow wrote:
> > On Thu, Jun 1, 2023 at 9:46 AM Niklas Cassel wrote:
> > >
> > > From: Niklas Cassel
> > >
> > > For NCQ, PxCI is cleared on command queued successfully.
> > > For
Fixes: a0cbd2e8496 ("meson: use prefer_static option", 2023-05-18)
Signed-off-by: Paolo Bonzini
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 553c8e0b9c5..c03326c922e 100644
--- a/meson.build
+++ b/meson.build
@@ -4088,7
From: Michal Privoznik
If configure was invoked with --disable-download and git
submodules were not checked out a warning is produced and the
configure script fails. But the $download variable (which
reflects the enable/disable download argument) is checked for in
a weird fashion:
test -f
tests/fp/berkeley-softfloat-3 and tests/fp/berkeley-testfloat-3
have been replaced by subprojects, so remove the now-unnecessary
submodules.
Reported-by: Michal Privoznik
Signed-off-by: Paolo Bonzini
---
tests/fp/berkeley-softfloat-3 | 1 -
tests/fp/berkeley-testfloat-3 | 1 -
2 files changed,
Fixes the build for --disable-tcg.
This header is only needed for cross-hosting. Without CONFIG_TCG,
we know this is an AArch64 host, CONFIG_ATOMIC64 will be set, and
the TCG_OVERSIZED_GUEST block will never be compiled.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
we were copying PSW into a local variable, updated PSW.CDE in the local
and never wrote it back. So when we called save_context_upper() we were
using the non-local version of PSW which did not contain the updated
PSW.CDE.
Signed-off-by: Bastian Koppelmann
Message-Id:
Signed-off-by: Bastian Koppelmann
Message-Id: <20230526061946.54514-7-kbast...@mail.uni-paderborn.de>
---
tests/tcg/tricore/Makefile.softmmu-target | 3 ++-
tests/tcg/tricore/c/test_context_save_areas.c | 15 +++
2 files changed, 17 insertions(+), 1 deletion(-)
create mode
this allows us to exercise the startup code used by GCC to call main().
Signed-off-by: Bastian Koppelmann
Message-Id: <20230526061946.54514-4-kbast...@mail.uni-paderborn.de>
---
configure | 1 +
tests/tcg/tricore/Makefile.softmmu-target | 13 +
starting from ISA version 1.6.1 (previously known as 1.6P/E), some
bitfields in PCXI and ICR have changed. We also refactor these
registers using the register fields API.
Signed-off-by: Bastian Koppelmann
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1453
Message-Id:
tags/pull-tricore-20230607
for you to fetch changes up to e926c94171ae37397c8c4b54cef60e5c7ebbf243:
tests/tcg/tricore: Add recursion test for CSAs (2023-06-07 18:20:51 +0200)
- Refactor PCXI/ICR field handling in newer ISA versions
the linker might rearrange sections, so lets reference memory by label
name instead of addr + off.
Signed-off-by: Bastian Koppelmann
Message-Id: <20230526061946.54514-3-kbast...@mail.uni-paderborn.de>
---
tests/tcg/tricore/asm/macros.h | 1 -
tests/tcg/tricore/asm/test_ld_bu.S | 4 ++--
this seperates these tests from the upcoming tests written in C.
Also rename the compiled test to 'test_.asm.tst'.
Signed-off-by: Bastian Koppelmann
Message-Id: <20230526061946.54514-2-kbast...@mail.uni-paderborn.de>
---
tests/tcg/tricore/Makefile.softmmu-target | 35 ---
On Wed, Jun 07, 2023 at 01:13:03PM -0300, Fabiano Rosas wrote:
> Fabiano Rosas (3):
> migration/multifd: Rename threadinfo.c functions
> migration/multifd: Protect accesses to migration_threads
> tests/qtest: Re-enable multifd cancel test
Reviewed-by: Peter Xu
--
Peter Xu
v2:
- patch 1: dropped the qmp_ prefix;
- patch 2: dropped the qemu_mutex_destroy;
stopped moving the _remove functions (don't strictly need it
anymore since not destroying the mutex explicitly);
added the lock to protect the loop in
We've found the source of flakiness in this test, so re-enable it.
Reviewed-by: Juan Quintela
Signed-off-by: Fabiano Rosas
---
tests/qtest/migration-test.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
This doubly linked list is common for all the multifd and migration
threads so we need to avoid concurrent access.
Add a mutex to protect the data from concurrent access. This fixes a
crash when removing two MigrationThread objects from the list at the
same time during cleanup of multifd threads.
We're about to add more functions to this file so make it use the same
coding style as the rest of the code.
Signed-off-by: Fabiano Rosas
Reviewed-by: Juan Quintela
Reviewed-by: Philippe Mathieu-Daudé
---
migration/migration.c | 4 ++--
migration/multifd.c| 4 ++--
migration/threadinfo.c
07.06.2023 16:52, Eugenio Perez Martin wrote:
On Wed, Jun 7, 2023 at 12:11 PM Michael Tokarev wrote:
..
Again, smells like a stable material, is it not?
Please Cc: qemu-sta...@nongnu.org for other changes you think should be
applied to stable qemu series.
Sorry, I totally forgot. This one
On Mon, Jun 05, 2023 at 08:19:43PM -0400, John Snow wrote:
> On Thu, Jun 1, 2023 at 9:46 AM Niklas Cassel wrote:
> >
> > From: Niklas Cassel
> >
> > For NCQ, PxCI is cleared on command queued successfully.
> > For non-NCQ, PxCI is cleared on command completed successfully.
> > Successfully means
Signed-off-by: Jagannathan Raman
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 436b3f0afefd..4a80a385118d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3786,7 +3786,6 @@ F: tests/tcg/aarch64/system/semiheap.c
Multi-process QEMU
M: Elena
John Johnson doesn't work at Oracle anymore. I tried to contact him to
get his updated email address, but I haven't heard anything from him.
Jagannathan Raman (1):
maintainers: update maintainers list for vfio-user & multi-process
QEMU
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
--
On Wed, Jun 07, 2023 at 07:35:32AM -0700, Steve Sistare wrote:
> Modify migrate_add_blocker and migrate_del_blocker to take an Error **
> reason. This allows migration to own the Error object, so that if
> an error occurs, migration code can free the Error and clear the client
> handle,
Another option could be to expose "-migrate-mode-disable" (instead of
enable) and just enable all 3 modes by default,
since we are already required to switch from "normal" mode to a
CPR-specific mode when it is time to do a live update,
if the intention is to preserve the capability to
1 - 100 of 268 matches
Mail list logo
