From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@linutronix.de, pbonzini@redhat.com
Cc: bigeasy@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
torvalds@linux-foundation.org, will@kernel.org,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, dave@stgolabs.net
Subject: [PATCH -tip 0/4] kvm: Use rcuwait for vcpu blocking
Date: Mon, 23 Mar 2020 21:44:49 -0700 [thread overview]
Message-ID: <20200324044453.15733-1-dave@stgolabs.net> (raw)
Hi,
The following is an updated revision of the kvm vcpu to rcuwait conversion[0],
following the work on completions using simple waitqueues.
Changes from then:
- patch 2: Make rcuwait_wake_up() propagate the return value from
wake_up_process - Sebastian and Peter.
- patch 3:
o Added mips changes I missed.
o Fixed broken compilation on power, adding the vcore bits that
kvm-hv uses (a vcore blocking when all vcpus are blocked) - Paolo.
o Use TASK_IDLE instead of TASK_INTERRUPTIBLE - Peter.
- patch 4: fixed swait function name typo.
This has only been run tested on x86 but compile tested on mips, powerpc
and arm32.
This series applies on top of current -tip, which has the required rcuwait
api extension.
[0] https://lore.kernel.org/lkml/20200320085527.23861-3-dave@stgolabs.net/
Thanks!
Davidlohr Bueso (4):
rcuwait: Fix stale wake call name in comment
rcuwait: Let rcuwait_wake_up() return whether or not a task was awoken
kvm: Replace vcpu->swait with rcuwait
sched/swait: Reword some of the main description
arch/mips/kvm/mips.c | 6 ++----
arch/powerpc/include/asm/kvm_book3s.h | 2 +-
arch/powerpc/include/asm/kvm_host.h | 2 +-
arch/powerpc/kvm/book3s_hv.c | 22 ++++++++--------------
arch/powerpc/kvm/powerpc.c | 2 +-
arch/x86/kvm/lapic.c | 2 +-
include/linux/kvm_host.h | 10 +++++-----
include/linux/rcuwait.h | 2 +-
include/linux/swait.h | 23 +++++------------------
kernel/exit.c | 9 ++++++---
virt/kvm/arm/arch_timer.c | 2 +-
virt/kvm/arm/arm.c | 9 +++++----
virt/kvm/async_pf.c | 3 +--
virt/kvm/kvm_main.c | 31 +++++++++++--------------------
14 files changed, 49 insertions(+), 76 deletions(-)
--
2.16.4
next reply other threads:[~2020-03-24 4:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 4:44 Davidlohr Bueso [this message]
2020-03-24 4:44 ` [PATCH 1/4] rcuwait: Fix stale wake call name in comment Davidlohr Bueso
2020-03-24 4:44 ` [PATCH 2/4] rcuwait: Let rcuwait_wake_up() return whether or not a task was awoken Davidlohr Bueso
2020-03-24 4:44 ` [PATCH 3/4] kvm: Replace vcpu->swait with rcuwait Davidlohr Bueso
2020-03-24 12:07 ` kbuild test robot
2020-03-24 16:47 ` kbuild test robot
2020-03-24 17:56 ` Davidlohr Bueso
2020-03-25 17:09 ` Paolo Bonzini
2020-04-14 21:12 ` Davidlohr Bueso
2020-04-15 12:11 ` Paolo Bonzini
2020-04-20 16:41 ` [PATCH v2] " Davidlohr Bueso
2020-04-20 17:12 ` Marc Zyngier
2020-04-20 17:25 ` Paolo Bonzini
2020-04-20 20:56 ` Davidlohr Bueso
2020-04-20 21:04 ` Paolo Bonzini
2020-04-20 21:50 ` Davidlohr Bueso
2020-04-21 9:43 ` Paolo Bonzini
2020-04-21 18:07 ` Davidlohr Bueso
2020-04-21 19:52 ` Paolo Bonzini
2020-03-24 4:44 ` [PATCH 4/4] sched/swait: Reword some of the main description Davidlohr Bueso
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=20200324044453.15733-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®