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]
Message-ID: <86802c440910132347x1913d2a1taf35f385af50e17c@mail.gmail.com>
Date:	Tue, 13 Oct 2009 23:47:33 -0700
From:	Yinghai Lu <yhlu.kernel@...il.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Joe Perches <joe@...ches.com>, Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v2 0/9] PCI, PNP: print resources consistently

On Tue, Oct 13, 2009 at 12:21 PM, Bjorn Helgaas <bjorn.helgaas@...com> wrote:
> These enhance %pR so we can print resource types and flags more easily.
> This doesn't really add anything (other than a couple new messages
> about host bridge apertures), but hopefully it will make things more
> consistent and a bit easier to debug.  Sample change (with "pci=use_crs"):
>
>    -pci 0000:00:03.0: reg 10 32bit mmio: [0xf6000000-0xf6ffffff]
>    -pci 0000:00:03.0: reg 14 io port: [0x2400-0x24ff]
>    -pci 0000:00:03.0: reg 18 32bit mmio: [0xf5ff0000-0xf5ff0fff]
>    -pci 0000:00:03.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
>    +pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cff]
>    +pci_root PNP0A03:00: host bridge window [io  0x0000-0x2cfe]
>    +pci_root PNP0A03:00: host bridge window [io  0x03b0-0x03bb]
>    +pci_root PNP0A03:00: host bridge window [io  0x03c0-0x03df]
>    +pci_root PNP0A03:00: host bridge window [mem 0xf5d00000-0xf6ffffff]
>    +pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
>    +pci 0000:00:03.0: reg 10: [mem 0xf6000000-0xf6ffffff]
>    +pci 0000:00:03.0: reg 14: [io  0x2400-0x24ff]
>    +pci 0000:00:03.0: reg 18: [mem 0xf5ff0000-0xf5ff0fff]
>    +pci 0000:00:03.0: reg 30: [mem 0x00000000-0x0001ffff pref]

can you keep "io port" and "mmio" ?
so we can use
grep "io port" dmesg.txt or grep "mmio" dmesg.txt

also put "io" and "mmio" "pref' in the [  ], looks strange.
[0xf5ff0000-0xf5ff0fff] is correct range expression.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ