From: Laurent Vivier <lvivier@redhat.com>
To: Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>,
Paul Mackerras <paulus@samba.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/2] Two fixes for dynamic micro-threading
Date: Fri, 24 Jul 2015 13:45:43 +0200 [thread overview]
Message-ID: <55B22567.50102@redhat.com> (raw)
In-Reply-To: <55B0D7EB.4060608@suse.de>
On 23/07/2015 14:02, Alexander Graf wrote:
>
>
> On 20.07.15 08:49, David Gibson wrote:
>> On Thu, Jul 16, 2015 at 05:11:12PM +1000, Paul Mackerras wrote:
>>> This series contains two fixes for the new dynamic micro-threading
>>> code that was added recently for HV-mode KVM on Power servers.
>>> The patches are against Alex Graf's kvm-ppc-queue branch. Please
>>> apply.
>>
>> agraf,
>>
>> Any word on these? These appear to fix a really nasty host crash in
>> current upstream. I'd really like to see them merged ASAP.
>
> Thanks, applied to kvm-ppc-queue.
>
> The host crash should only occur with dynamic micro-threading enabled,
> which is not in Linus' tree, correct?
Yes, it only occurs with dynamic micro-threading enabled.
Yes, this is not in Linus' tree.
Laurent
next prev parent reply other threads:[~2015-07-24 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 7:11 [PATCH 0/2] Two fixes for dynamic micro-threading Paul Mackerras
2015-07-16 7:11 ` [PATCH 1/2] KVM: PPC: Book3S HV: Fix preempted vcore list locking Paul Mackerras
2015-07-16 7:11 ` [PATCH 2/2] KVM: PPC: Book3S HV: Fix preempted vcore stolen time calculation Paul Mackerras
2015-07-16 14:06 ` [PATCH 0/2] Two fixes for dynamic micro-threading Laurent Vivier
2015-07-20 6:49 ` David Gibson
2015-07-23 12:02 ` Alexander Graf
2015-07-24 11:45 ` Laurent Vivier [this message]
2015-07-24 11:45 ` Paul Mackerras
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=55B22567.50102@redhat.com \
--to=lvivier@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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).