forked from Minki/linux
b02aae9cf5
x86: provide a DMI based port 0x80 I/O delay override.
Certain (HP) laptops experience trouble from our port 0x80 I/O delay
writes. This patch provides for a DMI based switch to the "alternate
diagnostic port" 0xed (as used by some BIOSes as well) for these.
David P. Reed confirmed that port 0xed works for him and provides a
proper delay. The symptoms of _not_ working are a hanging machine,
with "hwclock" use being a direct trigger.
Earlier versions of this attempted to simply use udelay(2), with the
2 being a value tested to be a nicely conservative upper-bound with
help from many on the linux-kernel mailinglist but that approach has
two problems.
First, pre-loops_per_jiffy calibration (which is post PIT init while
some implementations of the PIT are actually one of the historically
problematic devices that need the delay) udelay() isn't particularly
well-defined. We could initialise loops_per_jiffy conservatively (and
based on CPU family so as to not unduly delay old machines) which
would sort of work, but...
Second, delaying isn't the only effect that a write to port 0x80 has.
It's also a PCI posting barrier which some devices may be explicitly
or implicitly relying on. Alan Cox did a survey and found evidence
that additionally some drivers may be racy on SMP without the bus
locking outb.
Switching to an inb() makes the timing too unpredictable and as such,
this DMI based switch should be the safest approach for now. Any more
invasive changes should get more rigid testing first. It's moreover
only very few machines with the problem and a DMI based hack seems
to fit that situation.
This also introduces a command-line parameter "io_delay" to override
the DMI based choice again:
io_delay=<standard|alternate>
where "standard" means using the standard port 0x80 and "alternate"
port 0xed.
This retains the udelay method as a config (CONFIG_UDELAY_IO_DELAY) and
command-line ("io_delay=udelay") choice for testing purposes as well.
This does not change the io_delay() in the boot code which is using
the same port 0x80 I/O delay but those do not appear to be a problem
as David P. Reed reported the problem was already gone after using the
udelay version. He moreover reported that booting with "acpi=off" also
fixed things and seeing as how ACPI isn't touched until after this DMI
based I/O port switch I believe it's safe to leave the ones in the boot
code be.
The DMI strings from David's HP Pavilion dv9000z are in there already
and we need to get/verify the DMI info from other machines with the
problem, notably the HP Pavilion dv6000z.
This patch is partly based on earlier patches from Pavel Machek and
David P. Reed.
Signed-off-by: Rene Herman <rene.herman@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
89 lines
3.3 KiB
Plaintext
89 lines
3.3 KiB
Plaintext
#
|
|
# Makefile for the linux kernel.
|
|
#
|
|
|
|
extra-y := head_32.o init_task.o vmlinux.lds
|
|
CPPFLAGS_vmlinux.lds += -Ui386
|
|
|
|
obj-y := process_32.o signal_32.o entry_32.o traps_32.o irq_32.o \
|
|
ptrace_32.o time_32.o ioport_32.o ldt_32.o setup_32.o i8259_32.o sys_i386_32.o \
|
|
pci-dma_32.o i386_ksyms_32.o i387_32.o bootflag.o e820_32.o\
|
|
quirks.o i8237.o topology.o alternative.o i8253.o tsc_32.o io_delay.o
|
|
|
|
obj-$(CONFIG_STACKTRACE) += stacktrace.o
|
|
obj-y += cpu/
|
|
obj-y += acpi/
|
|
obj-$(CONFIG_X86_BIOS_REBOOT) += reboot_32.o
|
|
obj-$(CONFIG_MCA) += mca_32.o
|
|
obj-$(CONFIG_X86_MSR) += msr.o
|
|
obj-$(CONFIG_X86_CPUID) += cpuid.o
|
|
obj-$(CONFIG_MICROCODE) += microcode.o
|
|
obj-$(CONFIG_PCI) += early-quirks.o
|
|
obj-$(CONFIG_APM) += apm_32.o
|
|
obj-$(CONFIG_X86_SMP) += smp_32.o smpboot_32.o tsc_sync.o
|
|
obj-$(CONFIG_SMP) += smpcommon_32.o
|
|
obj-$(CONFIG_X86_TRAMPOLINE) += trampoline_32.o
|
|
obj-$(CONFIG_X86_MPPARSE) += mpparse_32.o
|
|
obj-$(CONFIG_X86_LOCAL_APIC) += apic_32.o nmi_32.o
|
|
obj-$(CONFIG_X86_IO_APIC) += io_apic_32.o
|
|
obj-$(CONFIG_X86_REBOOTFIXUPS) += reboot_fixups_32.o
|
|
obj-$(CONFIG_KEXEC) += machine_kexec_32.o relocate_kernel_32.o crash.o
|
|
obj-$(CONFIG_CRASH_DUMP) += crash_dump_32.o
|
|
obj-$(CONFIG_X86_NUMAQ) += numaq_32.o
|
|
obj-$(CONFIG_X86_SUMMIT_NUMA) += summit_32.o
|
|
obj-$(CONFIG_KPROBES) += kprobes_32.o
|
|
obj-$(CONFIG_MODULES) += module_32.o
|
|
obj-y += sysenter_32.o vsyscall_32.o
|
|
obj-$(CONFIG_ACPI_SRAT) += srat_32.o
|
|
obj-$(CONFIG_EFI) += efi_32.o efi_stub_32.o
|
|
obj-$(CONFIG_DOUBLEFAULT) += doublefault_32.o
|
|
obj-$(CONFIG_VM86) += vm86_32.o
|
|
obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
|
|
obj-$(CONFIG_HPET_TIMER) += hpet.o
|
|
obj-$(CONFIG_K8_NB) += k8.o
|
|
obj-$(CONFIG_MGEODE_LX) += geode_32.o mfgpt_32.o
|
|
|
|
obj-$(CONFIG_VMI) += vmi_32.o vmiclock_32.o
|
|
obj-$(CONFIG_PARAVIRT) += paravirt_32.o
|
|
obj-y += pcspeaker.o
|
|
|
|
obj-$(CONFIG_SCx200) += scx200_32.o
|
|
|
|
# vsyscall_32.o contains the vsyscall DSO images as __initdata.
|
|
# We must build both images before we can assemble it.
|
|
# Note: kbuild does not track this dependency due to usage of .incbin
|
|
$(obj)/vsyscall_32.o: $(obj)/vsyscall-int80_32.so $(obj)/vsyscall-sysenter_32.so
|
|
targets += $(foreach F,int80 sysenter,vsyscall-$F_32.o vsyscall-$F_32.so)
|
|
targets += vsyscall-note_32.o vsyscall_32.lds
|
|
|
|
# The DSO images are built using a special linker script.
|
|
quiet_cmd_syscall = SYSCALL $@
|
|
cmd_syscall = $(CC) -m elf_i386 -nostdlib $(SYSCFLAGS_$(@F)) \
|
|
-Wl,-T,$(filter-out FORCE,$^) -o $@
|
|
|
|
export CPPFLAGS_vsyscall_32.lds += -P -C -Ui386
|
|
|
|
vsyscall-flags = -shared -s -Wl,-soname=linux-gate.so.1 \
|
|
$(call ld-option, -Wl$(comma)--hash-style=sysv)
|
|
SYSCFLAGS_vsyscall-sysenter_32.so = $(vsyscall-flags)
|
|
SYSCFLAGS_vsyscall-int80_32.so = $(vsyscall-flags)
|
|
|
|
$(obj)/vsyscall-int80_32.so $(obj)/vsyscall-sysenter_32.so: \
|
|
$(obj)/vsyscall-%.so: $(src)/vsyscall_32.lds \
|
|
$(obj)/vsyscall-%.o $(obj)/vsyscall-note_32.o FORCE
|
|
$(call if_changed,syscall)
|
|
|
|
# We also create a special relocatable object that should mirror the symbol
|
|
# table and layout of the linked DSO. With ld -R we can then refer to
|
|
# these symbols in the kernel code rather than hand-coded addresses.
|
|
extra-y += vsyscall-syms.o
|
|
$(obj)/built-in.o: $(obj)/vsyscall-syms.o
|
|
$(obj)/built-in.o: ld_flags += -R $(obj)/vsyscall-syms.o
|
|
|
|
SYSCFLAGS_vsyscall-syms.o = -r
|
|
$(obj)/vsyscall-syms.o: $(src)/vsyscall_32.lds \
|
|
$(obj)/vsyscall-sysenter_32.o $(obj)/vsyscall-note_32.o FORCE
|
|
$(call if_changed,syscall)
|
|
|
|
|