diff options
| author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | 2011-09-01 09:48:27 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-10-03 11:40:12 -0700 |
| commit | 0b129e1ec4f63447c5467373909fa8e9d15826fd (patch) | |
| tree | 2185664fae6401dab8607ef9a254b7c88b9cd50f /drivers | |
| parent | 1f51b5d99ced3fc83ab8367e619320c08eee8a7f (diff) | |
| download | kernel_samsung_smdk4412-0b129e1ec4f63447c5467373909fa8e9d15826fd.zip kernel_samsung_smdk4412-0b129e1ec4f63447c5467373909fa8e9d15826fd.tar.gz kernel_samsung_smdk4412-0b129e1ec4f63447c5467373909fa8e9d15826fd.tar.bz2 | |
xen/smp: Warn user why they keel over - nosmp or noapic and what to use instead.
commit ed467e69f16e6b480e2face7bc5963834d025f91 upstream.
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
Acked-by: Ian Campbell <Ian.Campbell@eu.citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions