From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Date: Mon, 10 Nov 2008 15:54:26 +0000 Subject: Re: [patch] remove vcpu_info array v5 Message-Id: <49185932.9010006@redhat.com> List-Id: References: <4909C00F.8050704@sgi.com> In-Reply-To: <4909C00F.8050704@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ia64@vger.kernel.org Jes Sorensen wrote: > If we have reasons where we actually rely on the cpu number, and thats > not counting end-user pretty-number-print concerns, then I found that > we practically never use the cpu number. If we really use it a lot, I > agree we need a fast way, I just didn't hit it in my builds. What did I > miss? > The code I mentioned only runs if the -no-kvm-irqchip option is passed. It's not the highest performing option... So this isn't used a lot. But cpus definitely use cpu numbers (as apic ids), so qemu needs to be prepared to handle this. As to scalability, that takes will take a lot more work than removing/changing arbitrary limits. Look at qemu_mutex and weep. -- error compiling committee.c: too many arguments to function