On Mon, 30 May 2011 14:12:34 +0300 Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > On Mon, 2011-05-30 at 20:11 +0900, Takuya Yoshikawa wrote: > > On Mon, 30 May 2011 11:54:51 +0200 > > Ingo Molnar <mingo@xxxxxxx> wrote: > > > > > > > > * Pekka Enberg <penberg@xxxxxxxxxx> wrote: > > > > > > > On Mon, May 30, 2011 at 12:46 PM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > > > > > I'm just saying that we're limited to as many VCPU threads as we can > > > > > create. br_read_lock() won't do anything on a non-VCPU thread, which > > > > > makes it impossible to test it on non-VCPUs. > > > > > > > > It sure would be useful to be able to fire up 4096 VCPUs... ;-) > > > > > > > > But lets start out with 64 VCPUs, OK? It's better than nothing. > > > > > > In practice 64 VPUs ought to be able to find a good deal of bugs > > > already. > > > > Does kvm tools allow users to start more VCPUs than the actual cores? > > > Yes. > > > IIRC, qemu rejects such settings. > > > qemu also allows having more VCPUs than cores. I have to check again, then :) Thank you! I will try both with many VCPUs. Takuya -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
