From: Jon Hunter <jonathanh@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
<linaro-kernel@lists.linaro.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc/tegra: pmc: Don't allocate struct tegra_powergate on stack
Date: Mon, 24 Apr 2017 11:55:55 +0100 [thread overview]
Message-ID: <d947516f-7090-d539-6a10-f8348551fc0f@nvidia.com> (raw)
In-Reply-To: <20170417055035.GI28191@vireshk-i7>
On 17/04/17 06:50, Viresh Kumar wrote:
> On 21-03-17, 16:09, Viresh Kumar wrote:
>> On 21-03-17, 10:37, Jon Hunter wrote:
>>>
>>> On 21/03/17 05:24, Viresh Kumar wrote:
>>>> The size of the struct tegra_powergate is quite big and if any more
>>>> fields are added to the internal genpd structure, following warnings are
>>>> thrown:
>>>>
>>>> drivers/soc/tegra/pmc.c:577:1: warning: the frame size of 1176 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>>>
>>> Hmmm ... AFAICT the size of the tegra_powergate struct is 312 bytes
>>> (based upon next-20170321) and so it looks like something massive needs
>>> to be added to the genpd struct to blow this up to over 1024 bytes. Are
>>> there some genpd changes in-flight that are causing this?
>>
>> https://marc.info/?l=linux-kernel&m=149000247329743&w=2
>>
>> This is up for discussion right now though and we don't know if it
>> will surely get merged or not.
>
> @Jon: Regardless of the above series, do you want this patch to be merged as it
> will still be better to avoid keeping large structures on stack.
Given that it is currently much less than the default threshold, it
seems ok to me as-is. However, if it looks like you patch to add the
device struct to the gpd struct is going to be accepted, then it is fine
with me. Maybe we should wait for you patch to be accepted then this can
be applied as a fix.
Jon
--
nvpublic
prev parent reply other threads:[~2017-04-24 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 5:24 Viresh Kumar
2017-03-21 10:37 ` Jon Hunter
2017-03-21 10:39 ` Viresh Kumar
2017-04-17 5:50 ` Viresh Kumar
2017-04-24 10:55 ` Jon Hunter [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=d947516f-7090-d539-6a10-f8348551fc0f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®