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]
Message-ID: <46924116.1080901@amd.com>
Date:	Mon, 09 Jul 2007 16:07:18 +0200
From:	"Matthias Lenk" <matthias.lenk@....com>
To:	"Andi Kleen" <ak@...e.de>
cc:	"Aaron Durbin" <adurbin@...gle.com>, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH] i386/x86_64: Insert HPET firmware resource after
 PCI enumeration has completed

Andi, Aaron,
I retested the patch with Andi's patch not reverted (that's the way it's 
meant to be I guess) and then it works! I can now boot with HPET enabled.

Thanks,

Matthias

Matthias Lenk wrote:
> Aaron, I tested the patch on my affected system and unfortunately it 
> did not work. The BAR1 resource still gets overridden and hence the 
> same effects as before.
>
> Thanks,
>
> Matthias
>
> Andi Kleen wrote:
>> On Friday 06 July 2007 00:27:24 Aaron Durbin wrote:
>>  
>>> Insert HPET resources after pci probing has been completed in order 
>>> to avoid
>>> resource conflicts with PCI resource reservation. With this change the
>>> HPET firmware resources will be identified, but it should also not 
>>> cause
>>> issues when the HPET address falls on a BAR in a PCI device, and the 
>>> PCI
>>> enumeration cannot reserve the resources.
>>>     
>>
>> But what advantage does it have when it's already reserved by PCI?
>>
>> That's only a cosmetic change, isn't it?  A lot of code for cosmetics.
>>
>> -Andi
>>
>>
>>   
>
>
>




-
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