From: Alexander Graf <agraf@suse.de>
To: Mihai Caraman <mihai.caraman@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] KVM: PPC: e500mc: Add support for single threaded vcpus on e6500 core
Date: Wed, 03 Sep 2014 10:04:58 +0000 [thread overview]
Message-ID: <5406E7CA.3040900@suse.de> (raw)
In-Reply-To: <1409562119-11090-1-git-send-email-mihai.caraman@freescale.com>
On 01.09.14 11:01, Mihai Caraman wrote:
> ePAPR represents hardware threads as cpu node properties in device tree.
> So with existing QEMU, hardware threads are simply exposed as vcpus with
> one hardware thread.
>
> The e6500 core shares TLBs between hardware threads. Without tlb write
> conditional instruction, the Linux kernel uses per core mechanisms to
> protect against duplicate TLB entries.
>
> The guest is unable to detect real siblings threads, so it can't use the
> TLB protection mechanism. An alternative solution is to use the hypervisor
> to allocate different lpids to guest's vcpus that runs simultaneous on real
> siblings threads. On systems with two threads per core this patch halves
> the size of the lpid pool that the allocator sees and use two lpids per VM.
> Use even numbers to speedup vcpu lpid computation with consecutive lpids
> per VM: vm1 will use lpids 2 and 3, vm2 lpids 4 and 5, and so on.
>
> Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>
Thanks, applied both to kvm-ppc-queue.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Mihai Caraman <mihai.caraman@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] KVM: PPC: e500mc: Add support for single threaded vcpus on e6500 core
Date: Wed, 03 Sep 2014 12:04:58 +0200 [thread overview]
Message-ID: <5406E7CA.3040900@suse.de> (raw)
In-Reply-To: <1409562119-11090-1-git-send-email-mihai.caraman@freescale.com>
On 01.09.14 11:01, Mihai Caraman wrote:
> ePAPR represents hardware threads as cpu node properties in device tree.
> So with existing QEMU, hardware threads are simply exposed as vcpus with
> one hardware thread.
>
> The e6500 core shares TLBs between hardware threads. Without tlb write
> conditional instruction, the Linux kernel uses per core mechanisms to
> protect against duplicate TLB entries.
>
> The guest is unable to detect real siblings threads, so it can't use the
> TLB protection mechanism. An alternative solution is to use the hypervisor
> to allocate different lpids to guest's vcpus that runs simultaneous on real
> siblings threads. On systems with two threads per core this patch halves
> the size of the lpid pool that the allocator sees and use two lpids per VM.
> Use even numbers to speedup vcpu lpid computation with consecutive lpids
> per VM: vm1 will use lpids 2 and 3, vm2 lpids 4 and 5, and so on.
>
> Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>
Thanks, applied both to kvm-ppc-queue.
Alex
next prev parent reply other threads:[~2014-09-03 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 9:01 [PATCH v2 1/2] KVM: PPC: e500mc: Add support for single threaded vcpus on e6500 core Mihai Caraman
2014-09-01 9:01 ` Mihai Caraman
2014-09-01 9:01 ` [PATCH v2 2/2] KVM: PPC: Book3E: Enable " Mihai Caraman
2014-09-01 9:01 ` Mihai Caraman
2014-09-03 10:04 ` Alexander Graf [this message]
2014-09-03 10:04 ` [PATCH v2 1/2] KVM: PPC: e500mc: Add support for single threaded vcpus on " 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=5406E7CA.3040900@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mihai.caraman@freescale.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.