From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
"Davi E. M. Arnaut" <davi@haxent.com.br>,
davi@verdesmares.com, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
kvm@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2 1/2] sched/wait: Add add_wait_queue_priority()
Date: Wed, 28 Oct 2020 15:44:51 +0100 [thread overview]
Message-ID: <c2d63dd8-4f31-df23-2834-979a261f7653@redhat.com> (raw)
In-Reply-To: <20201028142031.GZ2628@hirez.programming.kicks-ass.net>
On 28/10/20 15:20, Peter Zijlstra wrote:
> Shall I take the waitqueue thing and stick it in a topic branch for
> Paolo so he can then merge that and the kvm bits on top into the KVM
> tree?
Topic branches are always the best solution. :)
Paolo
next prev parent reply other threads:[~2020-10-28 21:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 17:53 [RFC PATCH 1/2] sched/wait: Add add_wait_queue_priority() David Woodhouse
2020-10-26 17:53 ` [RFC PATCH 2/2] kvm/eventfd: Use priority waitqueue to catch events before userspace David Woodhouse
2020-10-27 8:01 ` Paolo Bonzini
2020-10-27 10:15 ` David Woodhouse
2020-10-27 13:55 ` [PATCH 0/3] Allow in-kernel consumers to drain events from eventfd David Woodhouse
2020-10-27 13:55 ` [PATCH 1/3] eventfd: Export eventfd_ctx_do_read() David Woodhouse
2020-10-27 13:55 ` [PATCH 2/3] vfio/virqfd: Drain events from eventfd in virqfd_wakeup() David Woodhouse
2020-11-06 23:29 ` Alex Williamson
2020-11-08 9:17 ` Paolo Bonzini
2020-10-27 13:55 ` [PATCH 3/3] kvm/eventfd: Drain events from eventfd in irqfd_wakeup() David Woodhouse
2020-10-27 18:41 ` kernel test robot
2020-10-27 21:42 ` kernel test robot
2020-10-27 23:13 ` kernel test robot
2020-10-27 14:39 ` [PATCH v2 0/2] Allow KVM IRQFD to consistently intercept events David Woodhouse
2020-10-27 14:39 ` [PATCH v2 1/2] sched/wait: Add add_wait_queue_priority() David Woodhouse
2020-10-27 19:09 ` Peter Zijlstra
2020-10-27 19:27 ` David Woodhouse
2020-10-27 20:30 ` Peter Zijlstra
2020-10-27 20:49 ` David Woodhouse
2020-10-27 21:32 ` David Woodhouse
2020-10-28 14:20 ` Peter Zijlstra
2020-10-28 14:44 ` Paolo Bonzini [this message]
2020-10-28 14:35 ` Peter Zijlstra
2020-11-04 9:35 ` David Woodhouse
2020-11-04 11:25 ` Paolo Bonzini
2020-11-06 10:17 ` Paolo Bonzini
2020-11-06 16:32 ` Alex Williamson
2020-11-06 17:18 ` David Woodhouse
2020-10-27 14:39 ` [PATCH v2 2/2] kvm/eventfd: Use priority waitqueue to catch events before userspace David Woodhouse
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=c2d63dd8-4f31-df23-2834-979a261f7653@redhat.com \
--to=pbonzini@redhat.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=davi@haxent.com.br \
--cc=davi@verdesmares.com \
--cc=davidel@xmailserver.org \
--cc=dietmar.eggemann@arm.com \
--cc=dwmw2@infradead.org \
--cc=juri.lelli@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).