RFC 64 bit resources
Status from this message: NAK - if the resource is 64bit then the pci_write_config_dword is also
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest10 patches 15 repliesNAK
Patches in v1
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | 64 bit resources core changesinclude/ kernel/ | +37 | 9 replies | |
| 2/10 | 64 bit resources drivers pci changesdrivers/ drivers/ drivers/ +9 more | +72 | 0 replies | |
| 3/10 | 64 bit resources drivers ide changesdrivers/ drivers/ drivers/ +2 more | +10 | 2 replies | |
| 4/10 | 64 bit resources drivers media changesdrivers/ drivers/ drivers/ +3 more | +20 | 0 replies | |
| 5/10 | 64 bit resources drivers net changesdrivers/ drivers/ drivers/ +8 more | +39 | 0 replies | |
| 6/10 | 64 bit resources drivers pcmcia changesdrivers/ drivers/ drivers/ +1 more | +21 | 0 replies | |
| 7/10 | 64 bit resources drivers others changesdrivers/ drivers/ drivers/ +21 more | +99 | 0 replies | |
| 8/10 | 64 bit resources sound changessound/ sound/ sound/ +7 more | +27 | 0 replies | |
| 9/10 | 64 bit resources arch changesarch/ arch/ arch/ +4 more | +78 | 0 replies | |
| 10/10 | i386: export memory more than 4G through /proc/iomemarch/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/10] 64 bit resources
Hi,
Here is an attempt to implement support for 64 bit resources. This will enable memory more than 4G to be exported through /proc/iomem, which is used by kexec/kdump to determine the physical memory layout of the system.
As suggested in the last week's discussion, I picked up greg's patch and made changes on top of that.
Last discussion witnessed a divided opinion upon whether to use u64 or something like dma_addr_t as data type. The argument is usage of dma_addr_t will reduce code size bloat for the people who don't want to use 64 bit resources on 32 bit platforms. But probably name dma_addr_t is not very appropriate for usage at various places.
Implementing u64 seems to be simpler and code bloat might not be significant.
This implementation is based on u64 and I have measured code bloat on i386.
- Greg's patch already had core changes. We have maninly fixed the warnings. Most of them originating from printk's().
- This patch does not try to modify the users of resources who think that on 32 bit platforms resources can be 32 bit only. They will continue to work as usual as they will silently truncate the 64 bit value to 32bit.
- We did the compilation for i386, arm, sparc, sparc64, x86_64 and ppc64 platforms and fixed the warnings.
Test Results:
------------
We used "make allyesconfig" with CONFIG_DEBUG_INFO=n on 2.6.16-mm1.
i386
----
vmlinux size without patch: 40191425
vmlinux size with path: 40244677
vmlinux size bloat: 52K (.13%)
x86_64
------
vmlinux size without patch: 42387898
vmlinux size with path: 42387945
vmlinux size bloat: 47 bytes
Thanks
Vivek