Bug 9222
Summary: | make menuconfig vague on Xeon dual core processor | ||
---|---|---|---|
Product: | Other | Reporter: | Todd (ToddAndMargo) |
Component: | Configuration | Assignee: | Roman Zippel (zippel) |
Status: | REJECTED INVALID | ||
Severity: | normal | CC: | protasnb, shaohua.li |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | make menuconfig vague on Xeon dual core processor | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Todd
2007-10-24 15:12:29 UTC
This is not really a problem, this is still a Xeon. You can compile with any option and it will actually try to find the right one for you. But I guess a little clarification wouldn't hurt. Maybe, we'll ask Intel. yes, it's based on piii, but it itself has an optimization option in gcc. I don't know which kernel you are using, but latest kernel have a config option for 'Core 2/new Xeon', so at least it's not a upstream bug. > yes, it's based on piii, but it itself has an optimization option in gcc. I
> don't know which kernel you are using, but latest kernel have a config option
> for 'Core 2/new Xeon', so at least it's not a upstream bug.
If it is not in mainline kernel then I suggest to close the bug.
/Sam
Even you didn't select the correct optimization option for gcc, it doesn't raelly matter to me. If there are optimization space, kernel usually will do it by itself, like write some code with mmx instruction. There isn't too many space left for gcc. I'll mark this as invalid as suggested. |