diff options
| author | Vivek Goyal <vgoyal@in.ibm.com> | 2006-12-07 02:14:04 +0100 |
|---|---|---|
| committer | Andi Kleen <andi@basil.nowhere.org> | 2006-12-07 02:14:04 +0100 |
| commit | e69f202d0a1419219198566e1c22218a5c71a9a6 (patch) | |
| tree | 16bb59505500797e1ea7e09ee9c3b495ce65b76a /Documentation/firmware_class/firmware_sample_driver.c | |
| parent | 6a044b3a0a1829ef19bb29548ffe553f48e8d80c (diff) | |
| download | blackbird-op-linux-e69f202d0a1419219198566e1c22218a5c71a9a6.tar.gz blackbird-op-linux-e69f202d0a1419219198566e1c22218a5c71a9a6.zip | |
[PATCH] i386: Implement CONFIG_PHYSICAL_ALIGN
o Now CONFIG_PHYSICAL_START is being replaced with CONFIG_PHYSICAL_ALIGN.
Hardcoding the kernel physical start value creates a problem in relocatable
kernel context due to boot loader limitations. For ex, if somebody
compiles a relocatable kernel to be run from address 4MB, but this kernel
will run from location 1MB as grub loads the kernel at physical address
1MB. Kernel thinks that I am a relocatable kernel and I should run from
the address I have been loaded at. So somebody wanting to run kernel
from 4MB alignment location (for improved performance regions) can't do
that.
o Hence, Eric proposed that probably CONFIG_PHYSICAL_ALIGN will make
more sense in relocatable kernel context. At run time kernel will move
itself to a physical addr location which meets user specified alignment
restrictions.
Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Diffstat (limited to 'Documentation/firmware_class/firmware_sample_driver.c')
0 files changed, 0 insertions, 0 deletions
