From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, "Hans de Goede" <hdegoede@redhat.com>,
"Florent DELAHAYE" <kernelorg@undead.fr>,
"Konrad J Hambrick" <kjhambrick@gmail.com>,
"Matt Hansen" <2lprbe78@duck.com>,
"Benoit Grégoire" <benoitg@coeus.ca>,
"Nicholas Johnson" <nicholas.johnson-opensource@outlook.com.au>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Werner Sembach" <wse@tuxedocomputers.com>,
mumblingdrunkard@protonmail.com, linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH v2 3/4] x86/PCI: Tidy E820 removal messages
Date: Fri, 9 Dec 2022 23:33:04 +0200 [thread overview]
Message-ID: <Y5OpkCs3HjIz1ghq@smile.fi.intel.com> (raw)
In-Reply-To: <20221209203428.GA1721600@bhelgaas>
On Fri, Dec 09, 2022 at 02:34:28PM -0600, Bjorn Helgaas wrote:
> On Fri, Dec 09, 2022 at 08:42:06PM +0200, Andy Shevchenko wrote:
> > On Thu, Dec 08, 2022 at 01:03:40PM -0600, Bjorn Helgaas wrote:
...
> > > + if (avail->end > avail->start)
> > > + pr_info("resource: remaining [mem %#010llx-%#010llx] available\n",
> > > + (unsigned long long) avail->start,
> > > + (unsigned long long) avail->end);
> >
> > Is there any point why we do not use %pa for resource_size_t parameters?
>
> Only my ignorance :) Thanks for pointing that out; I changed it to
> this and added a comment about why:
> + pr_info("resource: avoiding allocation from e820 entry [mem %#010Lx-%#010Lx]\n",
> + e820_start, e820_end);
> + if (avail->end > avail->start)
> + /*
> + * Use %pa instead of %pR because "avail"
> + * is typically IORESOURCE_UNSET, so %pR
> + * shows the size instead of addresses.
> + */
> + pr_info("resource: remaining [mem %pa-%pa] available\n",
> + &avail->start, &avail->end);
LGTM, thanks!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-12-09 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 19:03 [PATCH v2 0/4] PCI: Continue E820 vs host bridge window saga Bjorn Helgaas
2022-12-08 19:03 ` [PATCH v2 1/4] efi/x86: Remove EfiMemoryMappedIO from E820 map Bjorn Helgaas
2022-12-09 8:06 ` Hans de Goede
2022-12-09 11:04 ` Hans de Goede
2022-12-09 20:10 ` Bjorn Helgaas
2023-01-13 10:46 ` Baowen Zheng
2023-01-13 13:54 ` [PATCH " Bjorn Helgaas
2022-12-08 19:03 ` [PATCH v2 2/4] PCI: Skip allocate_resource() if too little space available Bjorn Helgaas
2022-12-08 19:03 ` [PATCH v2 3/4] x86/PCI: Tidy E820 removal messages Bjorn Helgaas
2022-12-09 18:42 ` Andy Shevchenko
2022-12-09 20:34 ` Bjorn Helgaas
2022-12-09 21:33 ` Andy Shevchenko [this message]
2022-12-08 19:03 ` [PATCH v2 4/4] x86/PCI: Fix log message typo Bjorn Helgaas
2022-12-09 18:43 ` Andy Shevchenko
2022-12-09 20:51 ` Bjorn Helgaas
2022-12-09 21:35 ` Andy Shevchenko
2022-12-09 21:52 ` Bjorn Helgaas
2022-12-10 20:55 ` Andy Shevchenko
2022-12-08 20:03 ` [PATCH v2 0/4] PCI: Continue E820 vs host bridge window saga Hans de Goede
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=Y5OpkCs3HjIz1ghq@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=2lprbe78@duck.com \
--cc=benoitg@coeus.ca \
--cc=bhelgaas@google.com \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=kernelorg@undead.fr \
--cc=kjhambrick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mumblingdrunkard@protonmail.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=wse@tuxedocomputers.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.