From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Rik van Riel <riel@redhat.com>,
linux-rt-users@vger.kernel.org, williams@redhat.com,
srostedt@redhat.com
Subject: Re: [PATCH -rt] kvm,rt: change async pagefault code locking for rt-preempt
Date: Tue, 29 Mar 2016 18:33:42 +0200 [thread overview]
Message-ID: <20160329163342.GG13334@linutronix.de> (raw)
In-Reply-To: <56FAAD3B.2050606@redhat.com>
* Paolo Bonzini | 2016-03-29 18:28:43 [+0200]:
>> I missed that swait went upstream, but I believe Paulo fixed
>> up the patch and has it in the KVM tree already.
>
>Yes, I did. You'll get Rik's patch for free from Linus's tree. :)
great. I just picked it from his tree.
>Paolo
Sebastian
prev parent reply other threads:[~2016-03-29 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 18:20 [PATCH -rt] kvm,rt: change async pagefault code locking for rt-preempt Rik van Riel
2016-03-29 16:13 ` Sebastian Andrzej Siewior
2016-03-29 16:18 ` Rik van Riel
2016-03-29 16:28 ` Paolo Bonzini
2016-03-29 16:33 ` Sebastian Andrzej Siewior [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=20160329163342.GG13334@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=riel@redhat.com \
--cc=srostedt@redhat.com \
--cc=williams@redhat.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).