summaryrefslogtreecommitdiffstats
path: root/arch/x86/xen/irq.c
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-09-01 09:48:27 -0400
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-09-01 12:54:49 -0400
commited467e69f16e6b480e2face7bc5963834d025f91 (patch)
treecfb1d21b4365da95678d8fe1f0e012230cef7eb0 /arch/x86/xen/irq.c
parentd198d499148a0c64a41b3aba9e7dd43772832b91 (diff)
downloadop-kernel-dev-ed467e69f16e6b480e2face7bc5963834d025f91.zip
op-kernel-dev-ed467e69f16e6b480e2face7bc5963834d025f91.tar.gz
xen/smp: Warn user why they keel over - nosmp or noapic and what to use instead.
We have hit a couple of customer bugs where they would like to use those parameters to run an UP kernel - but both of those options turn of important sources of interrupt information so we end up not being able to boot. The correct way is to pass in 'dom0_max_vcpus=1' on the Xen hypervisor line and the kernel will patch itself to be a UP kernel. Fixes bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637308 CC: stable@kernel.org Acked-by: Ian Campbell <Ian.Campbell@eu.citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'arch/x86/xen/irq.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud