From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: yezengruan <yezengruan@huawei.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
"will@kernel.org" <will@kernel.org>,
"maz@kernel.org" <maz@kernel.org>,
joelaf@google.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
suleiman@google.com,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Wanghaibin (D)" <wanghaibin.wang@huawei.com>
Subject: Re: [RFC][PATCH 0/4] arm64:kvm: teach guest sched that VCPUs can be preempted
Date: Fri, 11 Sep 2020 17:46:13 +0900 [thread overview]
Message-ID: <20200911084613.GA562@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <fe72592c-c721-bece-1469-95eebf931299@huawei.com>
Hi,
On (20/08/17 20:03), yezengruan wrote:
> Hi Sergey,
>
> I have a set of patches similar to yours.
>
> https://lore.kernel.org/lkml/20191226135833.1052-1-yezengruan@huawei.com/
I'm sorry for the belated reply.
Right, quite similar, but not exactly, I believe. I deliberately wanted
to untangle vcpu preemption (which is a characteristics feature) from
pv-lock, which may be somewhat implementation dependent.
Perhaps vcpu_is_preempted() should not even be implemented on per-arch
basis, but instead it can be more of a "core" functionality.
-ss
prev parent reply other threads:[~2020-09-11 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 4:17 [RFC][PATCH 0/4] arm64:kvm: teach guest sched that VCPUs can be preempted Sergey Senozhatsky
2020-07-21 4:17 ` [RFC][PATCH 1/4] arm64:kvm: define pv_state SMCCC HV calls Sergey Senozhatsky
2020-07-21 4:17 ` [RFC][PATCH 2/4] arm64: add guest pvstate support Sergey Senozhatsky
2020-07-21 4:17 ` [RFC][PATCH 3/4] arm64: add host " Sergey Senozhatsky
2020-07-21 4:17 ` [RFC][PATCH 4/4] arm64: do not use dummy vcpu_is_preempted() anymore Sergey Senozhatsky
2020-08-17 2:03 ` [RFC][PATCH 0/4] arm64:kvm: teach guest sched that VCPUs can be preempted Sergey Senozhatsky
2020-08-17 12:03 ` yezengruan
2020-08-17 12:25 ` Marc Zyngier
2020-08-17 14:15 ` yezengruan
2020-09-11 8:58 ` Sergey Senozhatsky
2020-12-08 20:02 ` Joel Fernandes
2020-12-09 9:43 ` Marc Zyngier
2020-12-10 1:39 ` Joel Fernandes
2020-12-10 8:45 ` Marc Zyngier
2020-12-11 9:34 ` Quentin Perret
2020-12-16 1:45 ` Joel Fernandes
2020-09-11 8:46 ` Sergey Senozhatsky [this message]
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=20200911084613.GA562@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=joelaf@google.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=suleiman@google.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yezengruan@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).