From: Balbir Singh <bsingharora@gmail.com>
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 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Wed, 06 Jul 2016 11:05:25 +0000 [thread overview]
Message-ID: <1467803125.9143.3.camel@gmail.com> (raw)
In-Reply-To: <741e7a7860e055603a311bcc6051bd88fdad1215.1467785081.git.sam.bobroff@au1.ibm.com>
On Wed, 2016-07-06 at 16:05 +1000, Sam Bobroff wrote:
> 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
> 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>
> ---
Makes sense
Acked-by: Balbir Singh <bsingharora@gmail.com>
>
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
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 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Wed, 06 Jul 2016 21:05:25 +1000 [thread overview]
Message-ID: <1467803125.9143.3.camel@gmail.com> (raw)
In-Reply-To: <741e7a7860e055603a311bcc6051bd88fdad1215.1467785081.git.sam.bobroff@au1.ibm.com>
On Wed, 2016-07-06 at 16:05 +1000, Sam Bobroff wrote:
> 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
> 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>
> ---
Makes sense
Acked-by: Balbir Singh <bsingharora@gmail.com>
>
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
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 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Wed, 06 Jul 2016 21:05:25 +1000 [thread overview]
Message-ID: <1467803125.9143.3.camel@gmail.com> (raw)
In-Reply-To: <741e7a7860e055603a311bcc6051bd88fdad1215.1467785081.git.sam.bobroff@au1.ibm.com>
On Wed, 2016-07-06 at 16:05 +1000, Sam Bobroff wrote:
> 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
> 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>
> ---
Makes sense
Acked-by: Balbir Singh <bsingharora@gmail.com>
>
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <bsingharora@gmail.com>
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: [Qemu-devel] [PATCH 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM
Date: Wed, 06 Jul 2016 21:05:25 +1000 [thread overview]
Message-ID: <1467803125.9143.3.camel@gmail.com> (raw)
In-Reply-To: <741e7a7860e055603a311bcc6051bd88fdad1215.1467785081.git.sam.bobroff@au1.ibm.com>
On Wed, 2016-07-06 at 16:05 +1000, Sam Bobroff wrote:
> 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
> 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>
> ---
Makes sense
Acked-by: Balbir Singh <bsingharora@gmail.com>
>
next prev parent reply other threads:[~2016-07-06 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 6:05 [PATCH 1/1] KVM: PPC: Introduce KVM_CAP_PPC_HTM Sam Bobroff
2016-07-06 6:05 ` [Qemu-devel] " Sam Bobroff
2016-07-06 6:05 ` Sam Bobroff
2016-07-06 6:05 ` Sam Bobroff
2016-07-06 11:05 ` Balbir Singh [this message]
2016-07-06 11:05 ` [Qemu-devel] " Balbir Singh
2016-07-06 11:05 ` Balbir Singh
2016-07-06 11:05 ` Balbir Singh
2016-07-07 0:07 ` David Gibson
2016-07-07 0:07 ` [Qemu-devel] " David Gibson
2016-07-07 0:07 ` David Gibson
2016-07-07 0:07 ` David Gibson
2016-07-08 10:49 ` [1/1] " Michael Ellerman
2016-07-08 10:49 ` [Qemu-devel] " Michael Ellerman
2016-07-08 10:49 ` Michael Ellerman
2016-07-19 3:23 ` Sam Bobroff
2016-07-19 3:23 ` [Qemu-devel] " Sam Bobroff
2016-07-19 3:23 ` Sam Bobroff
2016-07-19 9:24 ` Michael Ellerman
2016-07-19 9:24 ` Michael Ellerman
2016-07-19 9:24 ` Michael Ellerman
2016-07-19 9:24 ` [Qemu-devel] " Michael Ellerman
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=1467803125.9143.3.camel@gmail.com \
--to=bsingharora@gmail.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=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.