Changes in resource.c

00904bf6 - x86/PCI: Tidy E820 removal messages

Thu, 08 Dec 2022 19:03:40 +0000

x86/PCI: Tidy E820 removal messagesThese messages: clipped [mem size 0x00000000 64bit] to [mem size 0xfffffffffffa0000 64bit] for e820 entry [mem 0x0009f000-0x000fffff]aren't as useful as they could be because (a) the resource is oftenIORESOURCE_UNSET, so we print the size instead of the start/end and (b) weprint the available resource even if it is empty after removing the E820entry.Print the available space by hand to avoid the IORESOURCE_UNSET problem andonly if it's non-empty. No functional change intended.Link: https://lore.kernel.org/r/20221208190341.1560157-4-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas Acked-by: Hans de Goede List of files: /linux-6.15/arch/x86/kernel/resource.c

a2b36ffb - x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 regions"

Sun, 12 Jun 2022 14:43:25 +0000

x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 regions"This reverts commit 4c5e242d3e93.Prior to 4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820regions"), E820 regions did not affect PCI host bridge windows. We onlylooked at E820 regions and avoided them when allocating new MMIO space.If firmware PCI bridge window and BAR assignments used E820 regions, weleft them alone.After 4c5e242d3e93, we removed E820 regions from the PCI host bridgewindows before looking at BARs, so firmware assignments in E820 regionslooked like errors, and we moved things around to fit in the space left(if any) after removing the E820 regions. This unnecessary BARreassignment broke several machines.Guilherme reported that Steam Deck fails to boot after 4c5e242d3e93. Weclipped the window that contained most 32-bit BARs: BIOS-e820: [mem 0x00000000a0000000-0x00000000a00fffff] reserved acpi PNP0A08:00: clipped [mem 0x80000000-0xf7ffffff window] to [mem 0xa0100000-0xf7ffffff window] for e820 entry [mem 0xa0000000-0xa00fffff]which forced us to reassign all those BARs, for example, this NVMe BAR: pci 0000:00:01.2: PCI bridge to [bus 01] pci 0000:00:01.2: bridge window [mem 0x80600000-0x806fffff] pci 0000:01:00.0: BAR 0: [mem 0x80600000-0x80603fff 64bit] pci 0000:00:01.2: can't claim window [mem 0x80600000-0x806fffff]: no compatible bridge window pci 0000:01:00.0: can't claim BAR 0 [mem 0x80600000-0x80603fff 64bit]: no compatible bridge window pci 0000:00:01.2: bridge window: assigned [mem 0xa0100000-0xa01fffff] pci 0000:01:00.0: BAR 0: assigned [mem 0xa0100000-0xa0103fff 64bit]All the reassignments were successful, so the devices should have beenfunctional at the new addresses, but some were not.Andy reported a similar failure on an Intel MID platform. Benjaminreported a similar failure on a VMWare Fusion VM.Note: this is not a clean revert; this revert keeps the later change tomake the clipping dependent on a new pci_use_e820 bool, moving the checkingof this bool to arch_remove_reservations().[bhelgaas: commit log, add more reporters and testers]BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=216109Reported-by: Guilherme G. Piccoli Reported-by: Andy Shevchenko Reported-by: Benjamin Coddington Reported-by: Jongman Heo Fixes: 4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")Link: https://lore.kernel.org/r/20220612144325.85366-1-hdegoede@redhat.comTested-by: Guilherme G. Piccoli Tested-by: Andy Shevchenko Tested-by: Benjamin Coddington Signed-off-by: Hans de Goede Signed-off-by: Bjorn Helgaas List of files: /linux-6.15/arch/x86/kernel/resource.c

4c5e242d - x86/PCI: Clip only host bridge windows for E820 regions

Thu, 03 Mar 2022 22:00:39 +0000

x86/PCI: Clip only host bridge windows for E820 regionsACPI firmware advertises PCI host bridge resources via PNP0A03 _CRSmethods. Some BIOSes include non-window address space in _CRS, and if weallocate that non-window space for PCI devices, they don't work.4dc2287c1805 ("x86: avoid E820 regions when allocating address space")works around this issue by clipping out any regions mentioned in the E820table in the allocate_resource() path, but the implementation has a coupleissues: - The clipping is done for *all* allocations, not just those for PCI address space, and - The clipping is done at each allocation instead of being done once when setting up the host bridge windows.Rework the implementation so we only clip PCI host bridge windows, and wedo it once when setting them up.Example output changes: BIOS-e820: [mem 0x00000000b0000000-0x00000000c00fffff] reserved + acpi PNP0A08:00: clipped [mem 0xc0000000-0xfebfffff window] to [mem 0xc0100000-0xfebfffff window] for e820 entry [mem 0xb0000000-0xc00fffff] - pci_bus 0000:00: root bus resource [mem 0xc0000000-0xfebfffff window] + pci_bus 0000:00: root bus resource [mem 0xc0100000-0xfebfffff window]Link: https://lore.kernel.org/r/20220304035110.988712-3-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas Reviewed-by: Hans de Goede Reviewed-by: Mika Westerberg Acked-by: Rafael J. Wysocki List of files: /linux-6.15/arch/x86/kernel/resource.c

31bf0f43 - x86: Log resource clipping for E820 regions

Thu, 07 Apr 2022 22:42:02 +0000

x86: Log resource clipping for E820 regionsWhen remove_e820_regions() clips a resource because an E820 region overlapsit, log a note in dmesg to add in debugging.Signed-off-by: Bjorn Helgaas List of files: /linux-6.15/arch/x86/kernel/resource.c

93d256cd - x86/PCI: Eliminate remove_e820_regions() common subexpressions

Fri, 04 Mar 2022 00:04:43 +0000

x86/PCI: Eliminate remove_e820_regions() common subexpressionsAdd local variables to reduce repetition later. No functional changeintended.Link: https://lore.kernel.org/r/20220304035110.988712-2-helgaas@kernel.orgSigned-off-by: Bjorn Helgaas Reviewed-by: Hans de Goede Reviewed-by: Mika Westerberg Acked-by: Rafael J. Wysocki List of files: /linux-6.15/arch/x86/kernel/resource.c

3eb616b2 - x86/PCI: revert "Ignore E820 reservations for bridge windows on newer systems"

Wed, 09 Feb 2022 16:13:42 +0000

x86/PCI: revert "Ignore E820 reservations for bridge windows on newer systems"Commit 7f7b4236f204 ("x86/PCI: Ignore E820 reservations for bridge windowson newer systems") fixes the touchpad not working on laptops likethe Lenovo IdeaPad 3 15IIL05 and the Lenovo IdeaPad 5 14IIL05, as well asfixing thunderbolt hotplug issues on the Lenovo Yoga C940.Unfortunately it turns out that this is causing issues with suspend/resumeon Lenovo ThinkPad X1 Carbon Gen 2 laptops. So, per the no regressionspolicy, rever this. Note I'm looking into another fix for the issues thisfixed.Fixes: 7f7b4236f204 ("x86/PCI: Ignore E820 reservations for bridge windows on newer systems")BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=2029207Signed-off-by: Hans de Goede Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/arch/x86/kernel/resource.c

7f7b4236 - x86/PCI: Ignore E820 reservations for bridge windows on newer systems

Fri, 17 Dec 2021 14:13:48 +0000

x86/PCI: Ignore E820 reservations for bridge windows on newer systemsSome BIOS-es contain a bug where they add addresses which map to systemRAM in the PCI host bridge window returned by the ACPI _CRS method, seecommit 4dc2287c1805 ("x86: avoid E820 regions when allocating addressspace").To work around this bug Linux excludes E820 reserved addresses whenallocating addresses from the PCI host bridge window since 2010.Recently (2019) some systems have shown-up with E820 reservations whichcover the entire _CRS returned PCI bridge memory window, causing allattempts to assign memory to PCI BARs which have not been setup by theBIOS to fail. For example here are the relevant dmesg bits from aLenovo IdeaPad 3 15IIL 81WE: [mem 0x000000004bc50000-0x00000000cfffffff] reserved pci_bus 0000:00: root bus resource [mem 0x65400000-0xbfffffff window]The ACPI specifications appear to allow this new behavior:The relationship between E820 and ACPI _CRS is not really very clear.ACPI v6.3, sec 15, table 15-374, says AddressRangeReserved means: This range of addresses is in use or reserved by the system and is not to be included in the allocatable memory pool of the operating system's memory manager.and it may be used when: The address range is in use by a memory-mapped system device.Furthermore, sec 15.2 says: Address ranges defined for baseboard memory-mapped I/O devices, such as APICs, are returned as reserved.A PCI host bridge qualifies as a baseboard memory-mapped I/O device,and its apertures are in use and certainly should not be included inthe general allocatable pool, so the fact that some BIOS-es reportsthe PCI aperture as "reserved" in E820 doesn't seem like a BIOS bug.So it seems that the excluding of E820 reserved addresses is a mistake.Ideally Linux would fully stop excluding E820 reserved addresses,but then the old systems this was added for will regress.Instead keep the old behavior for old systems, while ignoringthe E820 reservations for any systems from now on.Old systems are defined here as BIOS year < 2018, this was chosen to makesure that E820 reservations will not be used on the currently affectedsystems, while at the same time also taking into account that the systemsfor which the E820 checking was originally added may have received BIOSupdates for quite a while (esp. CVE related ones), giving them a morerecent BIOS year then 2010.BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=206459BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1868899BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1871793BugLink: https://bugs.launchpad.net/bugs/1878279BugLink: https://bugs.launchpad.net/bugs/1931715BugLink: https://bugs.launchpad.net/bugs/1932069BugLink: https://bugs.launchpad.net/bugs/1921649Reviewed-by: Mika Westerberg Acked-by: Bjorn Helgaas Signed-off-by: Hans de Goede Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/arch/x86/kernel/resource.c

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/x86/kernel/resource.c

bf495573 - x86/boot/e820: Harmonize the 'struct e820_table' fields

Fri, 27 Jan 2017 13:06:21 +0000

x86/boot/e820: Harmonize the 'struct e820_table' fieldsSo the e820_table->map and e820_table->nr_map names are a bitconfusing, because it's not clear what a 'map' really means(it could be a bitmap, or some other data structure), nor isit clear what nr_map means (is it a current index, or someother count).Rename the fields from: e820_table->map => e820_table->entries e820_table->nr_map => e820_table->nr_entrieswhich makes it abundantly clear that these are entriesof the table, and that the size of the table is ->nr_entries.Propagate the changes to all affected files. Where necessary,adjust local variable names to better reflect the new field names.No change in functionality.Cc: Alex Thorlton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dan Williams Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Huang, Ying Cc: Josh Poimboeuf Cc: Juergen Gross Cc: Linus Torvalds Cc: Paul Jackson Cc: Peter Zijlstra Cc: Rafael J. Wysocki Cc: Tejun Heo Cc: Thomas Gleixner Cc: Wei Yang Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

61a50101 - x86/boot/e820: Rename everything to e820_table

Fri, 27 Jan 2017 12:54:38 +0000

x86/boot/e820: Rename everything to e820_tableNo change in functionality.Cc: Alex Thorlton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dan Williams Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Huang, Ying Cc: Josh Poimboeuf Cc: Juergen Gross Cc: Linus Torvalds Cc: Paul Jackson Cc: Peter Zijlstra Cc: Rafael J. Wysocki Cc: Tejun Heo Cc: Thomas Gleixner Cc: Wei Yang Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

acd4c048 - x86/boot/e820: Rename 'e820_map' variables to 'e820_array'

Fri, 27 Jan 2017 12:20:53 +0000

x86/boot/e820: Rename 'e820_map' variables to 'e820_array'In line with the rename to 'struct e820_array', harmonize the naming of common e820table variable names as well: e820 => e820_array e820_saved => e820_array_saved e820_map => e820_array initial_e820 => e820_array_initThis makes the variable names more consistent and easier to grep for.No change in functionality.Cc: Alex Thorlton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dan Williams Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Huang, Ying Cc: Josh Poimboeuf Cc: Juergen Gross Cc: Linus Torvalds Cc: Paul Jackson Cc: Peter Zijlstra Cc: Rafael J. Wysocki Cc: Tejun Heo Cc: Thomas Gleixner Cc: Wei Yang Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

8ec67d97 - x86/boot/e820: Rename the basic e820 data types to 'struct e820_entry' and 'struct e820_array'

Fri, 27 Jan 2017 11:54:38 +0000

x86/boot/e820: Rename the basic e820 data types to 'struct e820_entry' and 'struct e820_array'The 'e820entry' and 'e820map' names have various annoyances: - the missing underscore departs from the usual kernel style and makes the code look weird, - in the past I kept confusing the 'map' with the 'entry', because a 'map' is ambiguous in that regard, - it's not really clear from the 'e820map' that this is a regular C array.Rename them to 'struct e820_entry' and 'struct e820_array' accordingly.( Leave the legacy UAPI header alone but do the rename in the bootparam.h and e820/types.h file - outside tools relying on these defines should either adjust their code, or should use the legacy header, or should create their private copies for the definitions. )No change in functionality.Cc: Alex Thorlton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dan Williams Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Huang, Ying Cc: Josh Poimboeuf Cc: Juergen Gross Cc: Linus Torvalds Cc: Paul Jackson Cc: Peter Zijlstra Cc: Rafael J. Wysocki Cc: Tejun Heo Cc: Thomas Gleixner Cc: Wei Yang Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

66441bd3 - x86/boot/e820: Move asm/e820.h to asm/e820/api.h

Fri, 27 Jan 2017 09:27:10 +0000

x86/boot/e820: Move asm/e820.h to asm/e820/api.hIn line with asm/e820/types.h, move the e820 API declarations toasm/e820/api.h and update all usage sites.This is just a mechanical, obviously correct move & replace patch,there will be subsequent changes to clean up the code and to makebetter use of the new header organization.Cc: Alex Thorlton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dan Williams Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Huang, Ying Cc: Josh Poimboeuf Cc: Juergen Gross Cc: Linus Torvalds Cc: Paul Jackson Cc: Peter Zijlstra Cc: Rafael J. Wysocki Cc: Tejun Heo Cc: Thomas Gleixner Cc: Wei Yang Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

47533968 - x86/e820: Prepare e280 code for switch to dynamic storage

Sat, 17 Sep 2016 21:39:26 +0000

x86/e820: Prepare e280 code for switch to dynamic storageThis patch turns e820 and e820_saved into pointers to e820 tables,of the same size as before.Signed-off-by: Denys Vlasenko Acked-by: Thomas Gleixner Cc: Andy Lutomirski Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: H. Peter Anvin Cc: Josh Poimboeuf Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Yinghai Lu Cc: linux-kernel@vger.kernel.orgLink: http://lkml.kernel.org/r/20160917213927.1787-2-dvlasenk@redhat.comSigned-off-by: Ingo Molnar List of files: /linux-6.15/arch/x86/kernel/resource.c

cbace46a - x86: don't exclude low BIOS area when allocating address space for non-PCI cards

Wed, 16 Jul 2014 08:00:57 +0000

x86: don't exclude low BIOS area when allocating address space for non-PCI cardsCommit 30919b0bf356 ("x86: avoid low BIOS area when allocating addressspace") moved the test for resource allocations that fall within the first1MB of address space from the PCI-specific path to a generic path, suchthat all resource allocations will avoid this area. However, this breaksISA cards which need to allocate a memory region within the first 1MB. Anexample is the i82365 PCMCIA controller and derivatives like the RicohRF5C296/396 which map part of the PCMCIA socket memory address space intothe first 1MB of system memory address space. They do not work anymore asno usable memory region exists due to this change: Intel ISA PCIC probe: Ricoh RF5C296/396 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets host opts [0]: none host opts [1]: none ISA irqs (scanned) = 3,4,5,9,10 status change on irq 10 pcmcia_socket pcmcia_socket1: pccard: PCMCIA card inserted into slot 1 pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3ff: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x37f 0x3c0-0x3e7 0x3f0-0x3ff pcmcia_socket pcmcia_socket0: cs: memory probe 0x0a0000-0x0affff: excluding 0xa0000-0xaffff pcmcia_socket pcmcia_socket0: cs: memory probe 0x0b0000-0x0bffff: excluding 0xb0000-0xbffff pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcbfff pcmcia_socket pcmcia_socket0: cs: memory probe 0x0d0000-0x0dffff: clean. pcmcia_socket pcmcia_socket0: cs: memory probe 0x0e0000-0x0effff: clean. pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: clean. pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcff: excluding 0xcf8-0xcff pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean. pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3ff: excluding 0x170-0x177 0x1f0-0x1f7 0x2f8-0x2ff 0x370-0x37f 0x3c0-0x3e7 0x3f0-0x3ff pcmcia_socket pcmcia_socket1: cs: memory probe 0x0a0000-0x0affff: excluding 0xa0000-0xaffff pcmcia_socket pcmcia_socket1: cs: memory probe 0x0b0000-0x0bffff: excluding 0xb0000-0xbffff pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcbfff pcmcia_socket pcmcia_socket1: cs: memory probe 0x0d0000-0x0dffff: clean. pcmcia_socket pcmcia_socket1: cs: memory probe 0x0e0000-0x0effff: clean. pcmcia_socket pcmcia_socket1: cs: memory probe 0x60000000-0x60ffffff: clean. pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: clean. pcmcia_socket pcmcia_socket1: cs: memory probe 0x0cc000-0x0effff: excluding 0xe0000-0xeffff pcmcia_socket pcmcia_socket1: cs: unable to map card memory!If filtering out the first 1MB is reverted, everything works as expected.Tested-by: Robert Resch Signed-off-by: Christoph Schulz Signed-off-by: Bjorn Helgaas CC: stable@vger.kernel.org # v2.6.37+ List of files: /linux-6.15/arch/x86/kernel/resource.c

a2c606d5 - x86: avoid high BIOS area when allocating address space

Thu, 16 Dec 2010 17:39:02 +0000

x86: avoid high BIOS area when allocating address spaceThis prevents allocation of the last 2MB before 4GB.The experiment described here shows Windows 7 ignoring the last 1MB:https://bugzilla.kernel.org/show_bug.cgi?id=23542#c27This patch ignores the top 2MB instead of just 1MB because H. Peter Anvinsays "There will be ROM at the top of the 32-bit address space; it's a factof the architecture, and on at least older systems it was common to have ashadow 1 MiB below."Acked-by: H. Peter Anvin Signed-off-by: Bjorn Helgaas Signed-off-by: Jesse Barnes List of files: /linux-6.15/arch/x86/kernel/resource.c

4dc2287c - x86: avoid E820 regions when allocating address space

Thu, 16 Dec 2010 17:38:56 +0000

x86: avoid E820 regions when allocating address spaceWhen we allocate address space, e.g., to assign it to a PCI device, don'tallocate anything mentioned in the BIOS E820 memory map.On recent machines (2008 and newer), we assign PCI resources from thewindows described by the ACPI PCI host bridge _CRS. On many Dellmachines, these windows overlap some E820 reserved areas, e.g., BIOS-e820: 00000000bfe4dc00 - 00000000c0000000 (reserved) pci_root PNP0A03:00: host bridge window [mem 0xbff00000-0xdfffffff]If we put devices at 0xbff00000, they don't work, probably becausethat's really RAM, not I/O memory. This patch prevents that by removingthe 0xbfe4dc00-0xbfffffff area from the "available" resource.I'm not very happy with this solution because Windows solves the problemdifferently (it seems to ignore E820 reserved areas and it allocatestop-down instead of bottom-up; details at comment 45 of the bugzillabelow). That means we're vulnerable to BIOS defects that Windows would nottrip over. For example, if BIOS described a device in ACPI but didn'tmention it in E820, Windows would work fine but Linux would fail.Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228Acked-by: H. Peter Anvin Signed-off-by: Bjorn Helgaas Signed-off-by: Jesse Barnes List of files: /linux-6.15/arch/x86/kernel/resource.c

30919b0b - x86: avoid low BIOS area when allocating address space

Thu, 16 Dec 2010 17:38:51 +0000

x86: avoid low BIOS area when allocating address spaceThis implements arch_remove_reservations() so allocate_resource() canavoid any arch-specific reserved areas. This currently just avoids theBIOS area (the first 1MB), but could be used for E820 reserved areas ifthat turns out to be necessary.We previously avoided this area in pcibios_align_resource(). This patchmoves the test from that PCI-specific path to a generic path, so *all*resource allocations will avoid this area.Acked-by: H. Peter Anvin Signed-off-by: Bjorn Helgaas Signed-off-by: Jesse Barnes List of files: /linux-6.15/arch/x86/kernel/resource.c