linux-kernel - Re: [PATCH] x86: Allow MMCONFIG above 4GB on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Jul 2008 14:02:33 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"John Keller" <jpk@....com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	takayoshi.kochi@...il.com
Subject: Re: [PATCH] x86: Allow MMCONFIG above 4GB on x86_64

On Wed, Jul 9, 2008 at 1:41 PM, John Keller <jpk@....com> wrote:
> SGI UV will have MMCFG base addresses that are greater than 4GB (32 bits).
>
> Signed-off-by: John Keller <jpk@....com>
> ---
>
> A similar patch was submitted over a year ago, but apparently was not
> merged in.
>
>   http://marc.info/?l=linux-acpi&m=117283388212912&w=2
>
>
> Index: linux-2.6/arch/x86/kernel/acpi/boot.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/acpi/boot.c  2008-07-09 13:02:54.000000000 -0500
> +++ linux-2.6/arch/x86/kernel/acpi/boot.c       2008-07-09 15:25:32.000000000 -0500
> @@ -200,6 +200,7 @@ int __init acpi_parse_mcfg(struct acpi_t
>        }
>
>        memcpy(pci_mmcfg_config, &mcfg[1], config_size);
> +#ifndef CONFIG_X86_64
>        for (i = 0; i < pci_mmcfg_config_num; ++i) {
>                if (pci_mmcfg_config[i].address > 0xFFFFFFFF) {
>                        printk(KERN_ERR PREFIX
> @@ -209,6 +210,7 @@ int __init acpi_parse_mcfg(struct acpi_t
>                        return -ENODEV;
>                }
>        }
> +#endif
>
>        return 0;
>  }

CONFIG_RESOURCES_64BIT ?

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/