From: Michael Ellerman <mpe@ellerman.id.au>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: 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: [PATCH v2 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Wed, 20 Jul 2016 15:46:30 +1000 [thread overview]
Message-ID: <26225.77727675$1468993662@news.gmane.org> (raw)
In-Reply-To: <7286403003b30fc87740f1c1d6cb67d8f8eaafd7.1468986094.git.sam.bobroff@au1.ibm.com>
Sam Bobroff <sam.bobroff@au1.ibm.com> writes:
> Introduce a new KVM capability, KVM_CAP_PPC_HTM, that can be queried to
> determine if a PowerPC KVM guest should use HTM (Hardware Transactional
Minor nit, "should" should be "can" IMHO.
> Memory).
>
> This will be used by QEMU to populate the pa-features bits in the
> guest's device tree.
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
> ---
>
> v2:
>
> * Use CPU_FTR_TM_COMP instead of CPU_FTR_TM.
Thanks.
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Or do you want me to merge this before Paul gets back?
> * I didn't unbreak the line, as with the extra characters checkpatch will
> complain if I do. I did move the break to a more usual place.
I would just ignore checkpatch. But I don't mind that much.
cheers
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2016-07-20 5:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 3:41 [PATCH v2 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM Sam Bobroff
2016-07-20 3:41 ` Sam Bobroff
2016-07-20 3:41 ` [Qemu-devel] " Sam Bobroff
2016-07-20 4:20 ` Balbir Singh
2016-07-20 4:20 ` Balbir Singh
2016-07-20 4:20 ` [Qemu-devel] " Balbir Singh
2016-07-20 5:46 ` Michael Ellerman
2016-07-20 6:30 ` Paolo Bonzini
2016-07-20 6:30 ` Paolo Bonzini
2016-07-20 6:30 ` [Qemu-devel] " Paolo Bonzini
2016-07-20 10:20 ` Michael Ellerman
2016-07-20 10:20 ` [Qemu-devel] " Michael Ellerman
2016-07-20 10:20 ` Michael Ellerman
2016-07-20 10:20 ` Michael Ellerman
2016-07-20 10:20 ` Michael Ellerman
2016-08-01 18:52 ` Paolo Bonzini
2016-08-01 18:52 ` Paolo Bonzini
2016-08-01 18:52 ` [Qemu-devel] " Paolo Bonzini
2016-08-01 18:52 ` Paolo Bonzini
2016-07-20 5:46 ` Michael Ellerman [this message]
2016-07-20 5:46 ` Michael Ellerman
2016-07-20 5:46 ` Michael Ellerman
2016-07-20 5:46 ` [Qemu-devel] " Michael Ellerman
2016-07-20 9:16 ` David Gibson
2016-07-20 9:16 ` David Gibson
2016-07-20 9:16 ` [Qemu-devel] " David Gibson
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='26225.77727675$1468993662@news.gmane.org' \
--to=mpe@ellerman.id.au \
--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=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=sam.bobroff@au1.ibm.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 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.