> On 23 Jan 2025, at 9:57 PM, Peter Xu wrote:
>
> !---|
> CAUTION: External Email
>
> |---!
>
> On Thu, Jan 23, 2025 at 09:53:16AM +
> On 22 Jan 2025, at 10:10 PM, Peter Xu wrote:
>
> !---|
> CAUTION: External Email
>
> |---!
>
> Hi, Shivam,
>
> On Wed, Jan 22, 20
On 13 Jan 2025, at 9:59 PM, Peter Xu wrote:
!---|
CAUTION: External Email
|---!
On Fri, Jan 10, 2025 at 10:09:38AM -0300, Fabiano Rosas wrote:
Shivam Kumar writes
capabilities affecting old migration's
cleanup. Hence, set the status to 'failing' when a migration failure
happens and once the cleanup is complete, set the migration status to
MIGRATION_STATUS_FAILED.
Signed-off-by: Shivam Kumar
---
migration/m
11:20:03AM -0300, Fabiano Rosas wrote:
Peter Xu writes:
On Mon, Oct 07, 2024 at 03:44:51PM +, Shivam Kumar wrote:
If the client calls the QMP command to reset the migration
capabilities after the migration status is set to failed or cancelled
Is cancelled ok?
Asked because I think migrate_fd_c
On 7 Oct 2024, at 9:56 PM, Peter Xu wrote:
!---|
CAUTION: External Email
|---!
On Mon, Oct 07, 2024 at 03:44:51PM +, Shivam Kumar wrote:
If the client calls
QEMU crashing due to the following
assertion failure:
yank_unregister_instance: Assertion `QLIST_EMPTY(&entry->yankfns)`
failed
Check multifd state to determine whether multifd was used or not for
the migration rather than checking the state of multifd migration
capability.
Signed-off-by:
> On 04-Jan-2024, at 6:14 AM, Hao Xiang wrote:
>
> From: Juan Quintela
>
> This implements the zero page dection and handling.
>
> Signed-off-by: Juan Quintela
> ---
> migration/multifd.c | 41 +++--
> migration/multifd.h | 5 +
> 2 files changed, 44
> On 04-Jan-2024, at 6:14 AM, Hao Xiang wrote:
>
> 1. Refactor multifd_send_thread function.
> 2. Implement buffer_is_zero_use_cpu to handle CPU based zero page
> checking.
> 3. Introduce the batch task structure in MultiFDSendParams.
>
> Signed-off-by: Hao Xiang
> ---
> include/qemu/dsa.h |
> On 04-Jan-2024, at 6:14 AM, Hao Xiang wrote:
>
> From: Juan Quintela
>
> We have to enable it by default until we introduce the new code.
>
> Signed-off-by: Juan Quintela
> ---
> migration/options.c | 15 +++
> migration/options.h | 1 +
> qapi/migration.json | 8 +++-
> 3
On 22/11/22 9:30 am, Shivam Kumar wrote:
On 21/11/22 5:05 pm, Philippe Mathieu-Daudé wrote:
Hi,
On 20/11/22 23:54, Shivam Kumar wrote:
+
+void dirty_quota_migration_start(void)
+{
+ if (!kvm_state->dirty_quota_supported) {
You are accessing an accelerator-specific variable in
On 06/12/22 10:59 pm, Hyman Huang wrote:
在 2022/12/7 0:00, Peter Xu 写道:
Hi, Shivam,
On Tue, Dec 06, 2022 at 11:18:52AM +0530, Shivam Kumar wrote:
[...]
Note
--
--
We understand that there is a good scope of improvement in the current
implementation. Here is a list of
On 21/11/22 4:24 am, Shivam Kumar wrote:
This patchset is the QEMU-side implementation of a (new) dirty "quota"
based throttling algorithm that selectively throttles vCPUs based on their
individual contribution to overall memory dirtying and also dynamically
adapts the throttle ba
On 21/11/22 5:05 pm, Philippe Mathieu-Daudé wrote:
Hi,
On 20/11/22 23:54, Shivam Kumar wrote:
+
+void dirty_quota_migration_start(void)
+{
+ if (!kvm_state->dirty_quota_supported) {
You are accessing an accelerator-specific variable in an
accelerator-agnostic file, this doesn'
back to current auto-converge based throttling in cases where dirty
quota throttling can overthrottle.
Please stay tuned for the next patchset.
Shivam Kumar (1):
Dirty quota-based throttling of vcpus
accel/kvm/kvm-all.c | 91 +++
include/exec/memory.h
limit.
Suggested-by: Shaju Abraham
Suggested-by: Manish Mishra
Co-developed-by: Anurag Madnawat
Signed-off-by: Anurag Madnawat
Signed-off-by: Shivam Kumar
---
accel/kvm/kvm-all.c | 91 +++
include/exec/memory.h | 3 ++
include/hw/core/cpu.h | 5
16 matches
Mail list logo
