From: Marc Zyngier <maz@kernel.org>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, yj226063@alibaba-inc.com
Subject: Re: 3 preempted variables in kvm
Date: Mon, 25 Jan 2021 08:46:20 +0000 [thread overview]
Message-ID: <cb8ee83260dd9cc60acbab5e33c2b6db@kernel.org> (raw)
In-Reply-To: <c14cac63-6a4c-1b5d-6a32-e16117141e94@linux.alibaba.com>
On 2021-01-25 05:49, Alex Shi wrote:
> Hi Sean,
>
> Thanks a lot for the detailed explanations.
> Yes, they are all meaningful variables on x86. But for more archs,
> guess the lock
> issue on different arch's guest are similar. Maybe a abstraction on
> the point would
> be very helpful. Any comments?
It depends on what you have in mind. The whole "yield to another
vcpu" mechanism is already abstracted behind kvm_vcpu_on_spin(),
which at arm64, s390 and x86 are using. You could investigate
whether this is a valid approach for Power and MIPS.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2021-01-26 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 15:11 3 preempted variables in kvm Alex Shi
2021-01-22 19:30 ` Sean Christopherson
2021-01-25 5:49 ` Alex Shi
2021-01-25 8:46 ` Marc Zyngier [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=cb8ee83260dd9cc60acbab5e33c2b6db@kernel.org \
--to=maz@kernel.org \
--cc=alex.shi@linux.alibaba.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yj226063@alibaba-inc.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