linux-kernel - Re: [PATCH] i386/x86_64: Insert HPET firmware resource after PCI enumeration has completed

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:	Fri, 6 Jul 2007 05:45:06 -0700
From:	"Aaron Durbin" <adurbin@...gle.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	linux-kernel@...r.kernel.org, akpm@...l.org, matthias.lenk@....com
Subject: Re: [PATCH] i386/x86_64: Insert HPET firmware resource after PCI enumeration has completed

On 7/6/07, Andi Kleen <ak@...e.de> 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.
>

To my knowledge, not every machine has the HPET live on a BAR in PCI space. It
is cosmetic, but it shows what devices are using what memory address space in
/proc/iomem so one doesn't need to dig through dmesg to piece things together.

I am going to work w/ Matthias to see if we can get a patch working with his
system. I think that it is beneficial to easily view where resources are being
used, but I do understand the prudence.

-Aaron
-
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/