From: David Gibson <david@gibson.dropbear.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
Alexander Graf <agraf@suse.de>,
lvivier@redhat.com
Subject: Re: [PATCH 0/2] Two fixes for dynamic micro-threading
Date: Mon, 20 Jul 2015 06:49:34 +0000 [thread overview]
Message-ID: <20150720064934.GG19189@voom.fritz.box> (raw)
In-Reply-To: <1437030674-16077-1-git-send-email-paulus@samba.org>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
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.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: David Gibson <david@gibson.dropbear.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
Alexander Graf <agraf@suse.de>,
lvivier@redhat.com
Subject: Re: [PATCH 0/2] Two fixes for dynamic micro-threading
Date: Mon, 20 Jul 2015 16:49:34 +1000 [thread overview]
Message-ID: <20150720064934.GG19189@voom.fritz.box> (raw)
In-Reply-To: <1437030674-16077-1-git-send-email-paulus@samba.org>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
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.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-20 6:49 UTC|newest]
Thread overview: 16+ 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 ` 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 ` 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 7:11 ` Paul Mackerras
2015-07-16 14:06 ` [PATCH 0/2] Two fixes for dynamic micro-threading Laurent Vivier
2015-07-16 14:06 ` Laurent Vivier
2015-07-20 6:49 ` David Gibson [this message]
2015-07-20 6:49 ` David Gibson
2015-07-23 12:02 ` Alexander Graf
2015-07-23 12:02 ` Alexander Graf
2015-07-24 11:45 ` Laurent Vivier
2015-07-24 11:45 ` Laurent Vivier
2015-07-24 11:45 ` Paul Mackerras
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=20150720064934.GG19189@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.