[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH RFC 6/6] target-i386: make cpus childs of /machi
Re: [Qemu-devel] [PATCH RFC 6/6] target-i386: make cpus childs of /machine
Mon, 21 May 2012 12:01:39 -0300
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:18.104.22.168) Gecko/20080226 SUSE/22.214.171.124-1.1 Thunderbird/126.96.36.199 Mnenhy/0.7.5.666
On 2012-05-21 11:50, Igor Mammedov wrote:
>> I've used cpu_index, but it seems cpuid_apic_id is assigned only once,
>> from cpu_index, so it should be identical. What's the difference?
> Once Jan voiced that user visible cpu id, should be apic_id in context of cpu
> (i.e. when doing: device_add xxx_cpu,id=12345,...)
> "Jan, please correct me if I've got you wrong."
> So QOM tree probably should reflect this id and not cpu_index.
> However cpu_index and apic_id are the same now and bios assumes it as well.
> What are possible benefits of using cpuid_apic_id != cpu_index for qemu?
>From my POV, cpu_index could become equal to the physical APIC ID. As
long as we can set it freely (provided it remains unique) and
non-continuously, we don't need separate indexes.
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux