From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
aik@ozlabs.ru, agraf@suse.de, kvm-ppc@vger.kernel.org,
qemu-devel@nongnu.org, paulus@samba.org,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Tue, 19 Jul 2016 13:23:25 +1000 [thread overview]
Message-ID: <20160719032325.GA14519@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <3rmB8G0Wkxz9s9Z@ozlabs.org>
On Fri, Jul 08, 2016 at 08:49:49PM +1000, Michael Ellerman wrote:
> On Wed, 2016-06-07 at 06:05:54 UTC, Sam bobroff wrote:
> > diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
> > index 02416fe..06d79bc 100644
> > --- a/arch/powerpc/kvm/powerpc.c
> > +++ b/arch/powerpc/kvm/powerpc.c
> > @@ -588,6 +588,10 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
> > r = 1;
> > break;
> > #endif
> > + case KVM_CAP_PPC_HTM:
> > + r = cpu_has_feature(CPU_FTR_TM)
> > + && is_kvmppc_hv_enabled(kvm);
>
> I think it should be using CPU_FTR_TM_COMP.
Oh, why is that? I'm happy to respin the patch I'm just curious.
(I did it that way becuase that seems to be the way the other flags are used,
e.g. CPU_FTR_ALTIVEC).
If I read the code correctly, using CPU_FTR_TM_COMP will work fine: it should
cause the cpu_has_feature() test to always return false if CPU_FTR_TM_COMP is
0.
> And AFAICS you don't need to break that line.
Sure, I'll un-split it when I respin.
> cheers
Cheers,
Sam.
next prev parent reply other threads:[~2016-07-19 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 6:05 [Qemu-devel] [PATCH 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM Sam Bobroff
2016-07-06 11:05 ` Balbir Singh
2016-07-07 0:07 ` David Gibson
2016-07-08 10:49 ` [Qemu-devel] [1/1] " Michael Ellerman
2016-07-19 3:23 ` Sam Bobroff [this message]
2016-07-19 9:24 ` Michael Ellerman
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=20160719032325.GA14519@tungsten.ozlabs.ibm.com \
--to=sam.bobroff@au1.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.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).