On Fri, Sep 26, 2008 at 11:31 AM, Jes Sorensen <[EMAIL PROTECTED]> wrote: > Glauber Costa wrote: >> >> On Fri, Sep 26, 2008 at 11:17 AM, Jes Sorensen <[EMAIL PROTECTED]> wrote: >>> >>> Hi, >>> >>> Looking through the KVM qemu code, I see nothing that indicates that >>> smp_cpus can be increased after qemu is initially launched? >>> >>> Does anyone see any reason why we couldn't allocate the vcpu_info >>> array at launch time based on the value of smp_cpus? Right now >>> vcpu_info is a static array and I would love to get rid of this >>> limitation if possible. >> >> it can increase in hw/apic.c. The real limitation is then in the bios. >> The APIC tables >> used to be populated based on the smp_cpus value, and now are populated >> based on >> MAX_CPUS. > > Hmmm. I don't see any reference to MAX_CPUS in hw/apic.c, any chance you > can give me a pointer?
sorry. That's not apic (damn acronyms), It's acpi. But the reference to MAX_CPUS is at bios/rombios32.c when building the tables. the acpi code just fire them out. > > Thanks, > Jes > -- Glauber Costa. "Free as in Freedom" http://glommer.net "The less confident you are, the more serious you have to act." -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
