From: Logan Gunthorpe <logang@deltatee.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Bates <sbates@raithlin.com>,
Andrew Maier <andrew.maier@eideticom.com>
Subject: Re: [PATCH] PCI: Fix issue with "pci=disable_acs_redir" parameter being ignored
Date: Fri, 5 Apr 2019 16:11:46 -0600 [thread overview]
Message-ID: <f7f06f17-b644-dfea-e355-f44c8e920a33@deltatee.com> (raw)
In-Reply-To: <20190405213939.GC159318@google.com>
On 2019-04-05 3:39 p.m., Bjorn Helgaas wrote:
>> -static const char *disable_acs_redir_param;
>> +static char disable_acs_redir_param[COMMAND_LINE_SIZE];
>
> I certainly acknowledge the problem, but I'm a little hesitant to add
> a static buffer of 256-4096 bytes (2048 on x86, arm64, powerpc, sparc)
> for a relatively low-usage situation. The memory usage doesn't seem
> in proportion to the value-add.
>
> Ugh, and we allocate another similar buffer for
> resource_alignment_param[], which I would guess is also rarely used.
Yeah, I was looking for a better solution and eventually decided to just
copy what was done in the past.
> Since disable_acs_redir_param[] and resource_alignment_param[] are
> both read-only and big enough to hold the entire command line, we
> should be able to share a single buffer between them if we made the
> parsers a little smarter.
That sounds like a good idea that I didn't think of. If I can't find
something better, I'll do that.
> In fact, I bet there's already a static
> copy lying around somewhere for /proc/cmdline.
There are lots of copies of cmdline around, but none that are available
for early param. I did a sampling of some of the other early params but
none seem to be anywhere near as complex as the PCI one and I haven't
yet found one that needs to keep a copy of any or all of the command line.
In any case, I'll keep digging and try to get a better patch for you
shortly.
Logan
prev parent reply other threads:[~2019-04-05 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 19:33 Logan Gunthorpe
2019-04-05 21:39 ` Bjorn Helgaas
2019-04-05 22:11 ` Logan Gunthorpe [this message]
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=f7f06f17-b644-dfea-e355-f44c8e920a33@deltatee.com \
--to=logang@deltatee.com \
--cc=andrew.maier@eideticom.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sbates@raithlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®