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] [day] [month] [year] [list]
Date:	Tue, 26 Dec 2006 04:01:54 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	OGAWA Hirofumi <hogawa@...aclelinux.com>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address

Arjan van de Ven <arjan@...radead.org> writes:

>> Current workaround is the following (both of linus and -mm),
>> 
>> 	if (pci_mmcfg_config_num == 1 &&
>> 		cfg->pci_segment_group_number == 0 &&
>> 		(cfg->start_bus_number | cfg->end_bus_number) == 0)
>>                 /* Assume it can access 256M range */
>> 
>> But, if the system has bus number 0 only, it's a correct table.
>> We may need to detect the broken system. blacklist?
>
> or just... not assume 256Mb but assume broken?

I see. And instead, add force enable option?
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ