Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Wed, 4 Aug 2010 11:25:31 +0200
- Cc: mingo@xxxxxxxxxx, hpa@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, florian@xxxxxxxxxxx, mark@xxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, hpa@xxxxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <646233.80914.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- User-agent: Mutt/1.5.20 (2009-08-17)
* bifferos <bifferos@xxxxxxxxxxx> wrote:
> I couldn't reproduce this with 2.6.35 (without Peter's change),
> I was trying on VirtualBox. If the detection code is causing a
> problem we can just skip it if the CPU has cpuid.
As i reported:
> > -tip testing found that these RDC patches cause a boot
> > crash if a X86_RDC321X=y kernel is booted on a regular PC:
Those two patches caused the crash, with the config i sent, on a regular PC.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]