From: Marc Zyngier <maz@kernel.org>
To: Usama Arif <usama.arif@bytedance.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, bagasdotme@gmail.com,
fam.zheng@bytedance.com, punit.agrawal@bytedance.com,
linux@armlinux.org.uk, liangma@liangbit.com,
steven.price@arm.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [v2 0/6] KVM: arm64: implement vcpu_is_preempted check
Date: Fri, 04 Nov 2022 09:02:00 +0000 [thread overview]
Message-ID: <86edujqeif.wl-maz@kernel.org> (raw)
In-Reply-To: <20221104062105.4119003-1-usama.arif@bytedance.com>
On Fri, 04 Nov 2022 06:20:59 +0000,
Usama Arif <usama.arif@bytedance.com> wrote:
>
> This patchset adds support for vcpu_is_preempted in arm64, which allows the guest
> to check if a vcpu was scheduled out, which is useful to know incase it was
> holding a lock. vcpu_is_preempted can be used to improve
> performance in locking (see owner_on_cpu usage in mutex_spin_on_owner,
> mutex_can_spin_on_owner, rtmutex_spin_on_owner and osq_lock) and scheduling
> (see available_idle_cpu which is used in several places in kernel/sched/fair.c
> for e.g. in wake_affine to determine which CPU can run soonest):
Please refrain from reposting a series only two days after the initial
one. One week is a minimum, and only if there is enough review
comments to justify a respin (there were no valuable comments so far).
Reposting more often only results in the review process being
exponentially delayed.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Usama Arif <usama.arif@bytedance.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-doc@vger.kernel.org,
virtualization@lists.linux-foundation.org, linux@armlinux.org.uk,
yezengruan@huawei.com, catalin.marinas@arm.com, will@kernel.org,
steven.price@arm.com, mark.rutland@arm.com, bagasdotme@gmail.com,
fam.zheng@bytedance.com, liangma@liangbit.com,
punit.agrawal@bytedance.com
Subject: Re: [v2 0/6] KVM: arm64: implement vcpu_is_preempted check
Date: Fri, 04 Nov 2022 09:02:00 +0000 [thread overview]
Message-ID: <86edujqeif.wl-maz@kernel.org> (raw)
In-Reply-To: <20221104062105.4119003-1-usama.arif@bytedance.com>
On Fri, 04 Nov 2022 06:20:59 +0000,
Usama Arif <usama.arif@bytedance.com> wrote:
>
> This patchset adds support for vcpu_is_preempted in arm64, which allows the guest
> to check if a vcpu was scheduled out, which is useful to know incase it was
> holding a lock. vcpu_is_preempted can be used to improve
> performance in locking (see owner_on_cpu usage in mutex_spin_on_owner,
> mutex_can_spin_on_owner, rtmutex_spin_on_owner and osq_lock) and scheduling
> (see available_idle_cpu which is used in several places in kernel/sched/fair.c
> for e.g. in wake_affine to determine which CPU can run soonest):
Please refrain from reposting a series only two days after the initial
one. One week is a minimum, and only if there is enough review
comments to justify a respin (there were no valuable comments so far).
Reposting more often only results in the review process being
exponentially delayed.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Usama Arif <usama.arif@bytedance.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-doc@vger.kernel.org,
virtualization@lists.linux-foundation.org, linux@armlinux.org.uk,
yezengruan@huawei.com, catalin.marinas@arm.com, will@kernel.org,
steven.price@arm.com, mark.rutland@arm.com, bagasdotme@gmail.com,
fam.zheng@bytedance.com, liangma@liangbit.com,
punit.agrawal@bytedance.com
Subject: Re: [v2 0/6] KVM: arm64: implement vcpu_is_preempted check
Date: Fri, 04 Nov 2022 09:02:00 +0000 [thread overview]
Message-ID: <86edujqeif.wl-maz@kernel.org> (raw)
In-Reply-To: <20221104062105.4119003-1-usama.arif@bytedance.com>
On Fri, 04 Nov 2022 06:20:59 +0000,
Usama Arif <usama.arif@bytedance.com> wrote:
>
> This patchset adds support for vcpu_is_preempted in arm64, which allows the guest
> to check if a vcpu was scheduled out, which is useful to know incase it was
> holding a lock. vcpu_is_preempted can be used to improve
> performance in locking (see owner_on_cpu usage in mutex_spin_on_owner,
> mutex_can_spin_on_owner, rtmutex_spin_on_owner and osq_lock) and scheduling
> (see available_idle_cpu which is used in several places in kernel/sched/fair.c
> for e.g. in wake_affine to determine which CPU can run soonest):
Please refrain from reposting a series only two days after the initial
one. One week is a minimum, and only if there is enough review
comments to justify a respin (there were no valuable comments so far).
Reposting more often only results in the review process being
exponentially delayed.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-04 9:02 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 6:20 [v2 0/6] KVM: arm64: implement vcpu_is_preempted check Usama Arif
2022-11-04 6:20 ` Usama Arif
2022-11-04 6:20 ` Usama Arif
2022-11-04 6:21 ` [v2 1/6] KVM: arm64: Document PV-lock interface Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-07 17:56 ` Punit Agrawal
2022-11-07 17:56 ` Punit Agrawal
2022-11-07 17:56 ` Punit Agrawal
2022-11-07 18:05 ` Usama Arif
2022-11-07 18:05 ` Usama Arif
2022-11-07 18:05 ` Usama Arif
2022-11-04 6:21 ` [v2 2/6] KVM: arm64: Add SMCCC paravirtualised lock calls Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-07 17:58 ` Punit Agrawal
2022-11-07 17:58 ` Punit Agrawal
2022-11-07 17:58 ` Punit Agrawal
2022-11-07 18:08 ` Usama Arif
2022-11-07 18:08 ` Usama Arif
2022-11-07 18:08 ` Usama Arif
2022-11-04 6:21 ` [v2 3/6] KVM: arm64: Support pvlock preempted via shared structure Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-07 18:02 ` Punit Agrawal
2022-11-07 18:02 ` Punit Agrawal
2022-11-07 18:02 ` Punit Agrawal
2022-11-07 18:09 ` Usama Arif
2022-11-07 18:09 ` Usama Arif
2022-11-07 18:09 ` Usama Arif
2022-11-04 6:21 ` [v2 4/6] KVM: arm64: Provide VCPU attributes for PV lock Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` [v2 5/6] KVM: arm64: Support the VCPU preemption check Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` [v2 6/6] KVM: selftests: add tests for PV time specific hypercall Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 6:21 ` Usama Arif
2022-11-04 9:02 ` Marc Zyngier [this message]
2022-11-04 9:02 ` [v2 0/6] KVM: arm64: implement vcpu_is_preempted check Marc Zyngier
2022-11-04 9:02 ` Marc Zyngier
2022-11-06 16:35 ` Marc Zyngier
2022-11-06 16:35 ` Marc Zyngier
2022-11-06 16:35 ` Marc Zyngier
2022-11-07 12:00 ` [External] " Usama Arif
2022-11-07 12:00 ` Usama Arif
2022-11-07 12:00 ` Usama Arif
2022-11-18 0:20 ` Marc Zyngier
2022-11-18 0:20 ` Marc Zyngier
2022-11-18 0:20 ` Marc Zyngier
2022-11-24 13:55 ` Usama Arif
2022-11-24 13:55 ` Usama Arif
2022-11-24 13:55 ` Usama Arif
2022-12-05 13:43 ` Usama Arif
2022-12-05 13:43 ` Usama Arif
2022-12-05 13:43 ` Usama Arif
2023-01-17 10:50 ` Usama Arif
2023-01-17 10:50 ` Usama Arif
2022-11-07 18:24 ` Punit Agrawal
2022-11-07 18:24 ` Punit Agrawal
2022-11-07 18:24 ` Punit Agrawal
2022-11-09 19:38 ` Usama Arif
2022-11-09 19:38 ` Usama Arif
2022-11-09 19:38 ` Usama Arif
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86edujqeif.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=fam.zheng@bytedance.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=liangma@liangbit.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=punit.agrawal@bytedance.com \
--cc=steven.price@arm.com \
--cc=usama.arif@bytedance.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.