I fixed the first problem which I would consider legitimate (specifying
NULL explicitly is better), but now I'm having the same problem with a
parameter I -have- provided a default value for. I'm assuming when I get
the message:
fatal: root.family without default or user set value
that it's complaining about the following from my Intel MP table stuff:
class X86IntelMPProcessor(X86IntelMPBaseConfigEntry):
type = 'X86IntelMPProcessor'
cxx_class = 'X86ISA::IntelMP::Processor'
local_apic_id = Param.UInt8(0, 'local APIC id')
local_apic_version = Param.UInt8(0,
'bits 0-7 of the local APIC version register')
enable = Param.Bool(True, 'if this processor is usable')
bootstrap = Param.Bool(False, 'if this is the bootstrap processor')
stepping = Param.UInt8(0)
model = Param.UInt8(0)
family = Param.UInt8(0)
feature_flags = Param.UInt32(0, 'flags returned by the CPUID
instruction')
That's the only occurrence of the string "family" in any .py file in the
repository. It does have a default value of 0, so I'm not sure what the
problem is. Maybe the check is getting a false positive? If you want to
try this yourself, just stick a default NULL on line 97 of
arch/x86/bios/ACPI.py. The kernel I use is on zizzer at
/dist/m5/system/binaries/x86_64-vmlinux-2.6.22.9. I'm uploading the disk
image to /dist/m5/system/disks/x86root.img, but that will be a while
yet. You probably won't get far enough to need those anyway, though.
Gabe
nathan binkert wrote:
>> What's the syntax to set something to NULL by default? That's actually
>> what I want in this case, I think. I tried using "None" but apparently
>> that's not right.
>>
>
> There's actually a special parameter called NULL. :) Just use it.
>
> Nate
> _______________________________________________
> m5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/m5-dev
>
_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev
