On Tue, May 17, 2011 at 01:36:26PM +0200, Alexander Graf wrote:
>
> Just so I understand the scheme: One vcpu needs to go to MMU mode in
> KVM, it then sends IPIs to stop the other threads and finally we
> return from this wait here?
Actually, if one thread needs to get the other threads out of th
Am 17.05.2011 um 12:44 schrieb Paul Mackerras :
> On Tue, May 17, 2011 at 10:21:56AM +0200, Alexander Graf wrote:
>>
>> On 11.05.2011, at 12:46, Paul Mackerras wrote:
>>
>>> -#define KVM_MAX_VCPUS 1
>>> +#define KVM_MAX_VCPUSNR_CPUS
>>> +#define KVM_THREADS_PER_CORE4
>>
>> So what
On Tue, May 17, 2011 at 10:21:56AM +0200, Alexander Graf wrote:
>
> On 11.05.2011, at 12:46, Paul Mackerras wrote:
>
> > -#define KVM_MAX_VCPUS 1
> > +#define KVM_MAX_VCPUS NR_CPUS
> > +#define KVM_THREADS_PER_CORE 4
>
> So what if POWER8 (or whatever it will be called) comes
On 11.05.2011, at 12:46, Paul Mackerras wrote:
> This lifts the restriction that book3s_hv guests can only run one
> hardware thread per core, and allows them to use up to 4 threads
> per core on POWER7. The host still has to run single-threaded.
>
> This capability is advertised to qemu throug
On Wed, May 11, 2011 at 03:44:15PM +0200, Christoph Hellwig wrote:
> On Wed, May 11, 2011 at 08:46:56PM +1000, Paul Mackerras wrote:
> > arch/powerpc/sysdev/xics/icp-native.c.
>
> What kernel tree do I need to actually have that file?
The "next" branch of
git://git.kernel.org/pub/scm/linux/kernel
On Wed, May 11, 2011 at 08:46:56PM +1000, Paul Mackerras wrote:
> arch/powerpc/sysdev/xics/icp-native.c.
What kernel tree do I need to actually have that file?
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo
This lifts the restriction that book3s_hv guests can only run one
hardware thread per core, and allows them to use up to 4 threads
per core on POWER7. The host still has to run single-threaded.
This capability is advertised to qemu through a new KVM_CAP_PPC_SMT
capability.
To use this, the host
