From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 3/4] pci: improve debug output
Date: Sat, 14 Apr 2018 01:58:15 +0200 [thread overview]
Message-ID: <20180413235815.h4zgmhhweqexqbcx@pengutronix.de> (raw)
In-Reply-To: <20180413233053.15570-3-u.kleine-koenig@pengutronix.de>
Hello,
On Sat, Apr 14, 2018 at 01:30:52AM +0200, Uwe Kleine-König wrote:
> if (ALIGN(*last, size) + size > dev->bus->resource[restype]->end) {
> - pr_debug("BAR does not fit within bus %s res\n", type);
> + pr_debug(" pbar%d: !! type=%s allocbase=0x%08x + size=0x%08x > resource_end=%pa (barval=%08x)\n",
> + bar, type, ALIGN(*last, size), size, &dev->bus->resource[restype]->end, barval);
slightly related: I have a machine where this new line results in:
pci: pbar0: !! type=NP allocbase=0x01800000 + size=0x00800000 > resource_end=0x01efffff (barval=ff800000)
This makes me wonder if the LHS of the check needs to read
ALIGN(*last, size) + size - 1
. I will think about this after sleeping, and then probably send a patch
for that.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-04-13 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 23:30 [PATCH 1/4] pci: rename variable mask -> barval Uwe Kleine-König
2018-04-13 23:30 ` [PATCH 2/4] pci: refactor bar configuration Uwe Kleine-König
2018-04-13 23:30 ` [PATCH 3/4] pci: improve debug output Uwe Kleine-König
2018-04-13 23:58 ` Uwe Kleine-König [this message]
2018-04-13 23:30 ` [PATCH 4/4] pci: don't hide hard to understand sanity check in size calculation Uwe Kleine-König
2018-04-14 16:25 ` Andrey Smirnov
2018-04-15 18:27 ` Uwe Kleine-König
2018-04-16 13:42 ` Andrey Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180413235815.h4zgmhhweqexqbcx@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox