From: Michael Ellerman <michael@ellerman.id.au>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, agraf@suse.de, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] kvm/powerpc: Handle errors in secondary thread grabbing
Date: Tue, 16 Oct 2012 17:00:35 +1100 [thread overview]
Message-ID: <1350367235.32704.1.camel@concordia> (raw)
In-Reply-To: <20121016031352.GK1218@drongo>
On Tue, 2012-10-16 at 14:13 +1100, Paul Mackerras wrote:
> Michael,
>
> On Tue, Oct 16, 2012 at 11:15:50AM +1100, Michael Ellerman wrote:
> > In the Book3s HV code, kvmppc_run_core() has logic to grab the secondary
> > threads of the physical core.
> >
> > If for some reason a thread is stuck, kvmppc_grab_hwthread() can fail,
> > but currently we ignore the failure and continue into the guest. If the
> > stuck thread is in the kernel badness ensues.
> >
> > Instead we should check for failure and bail out.
> >
> > I've moved the grabbing prior to the startup of runnable threads, to simplify
> > the error case. AFAICS this is harmless, but I could be missing something
> > subtle.
>
> Thanks for looking at this - but in fact this is fixed by my patch
> entitled "KVM: PPC: Book3S HV: Fix some races in starting secondary
> threads" submitted back on August 28.
OK thanks. It seems that patch didn't make 3.7 ?
I don't see it in kvm-ppc-next either.
cheers
next prev parent reply other threads:[~2012-10-16 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 0:15 [PATCH] kvm/powerpc: Handle errors in secondary thread grabbing Michael Ellerman
2012-10-16 3:13 ` Paul Mackerras
2012-10-16 6:00 ` Michael Ellerman [this message]
2012-10-16 19:33 ` Benjamin Herrenschmidt
2012-10-17 6:25 ` Alexander Graf
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=1350367235.32704.1.camel@concordia \
--to=michael@ellerman.id.au \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).