All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	linux-kernel@vger.kernel.org, "kernel test robot" <lkp@intel.com>,
	"Dengcheng Zhu" <dzhu@wavecomp.com>,
	"John Crispin" <john@phrozen.org>,
	linux-mips@vger.kernel.org, "Qais Yousef" <qyousef@layalina.io>
Subject: Re: [PATCH] MIPS: vpe-mt: provide a default 'physical_memsize'
Date: Fri, 17 Feb 2023 12:57:13 +0100	[thread overview]
Message-ID: <20230217115713.GA7701@alpha.franken.de> (raw)
In-Reply-To: <a2a7806b-ba53-9f37-938b-d3f48ea217f2@infradead.org>

On Wed, Feb 15, 2023 at 10:59:35PM -0800, Randy Dunlap wrote:
> > I agree this is where this variable has be be declared / initialized,
> > but having this dependent on CONFIG_MIPS_MALTA/CONFIG_LANTIQ machines
> > doesn't seem right.
> 
> So far I have been able to consolidate the LANTIQ code into a general
> patch, but not MALTA.

if I didn't miss something physical_memory is always 0 for LANTIQ 
and something for MALTA depending on command line/DT. Now

arch/mips/kernel/vpe-mt.c contains

        /*
         * The sde-kit passes 'memsize' to __start in $a3, so set something
         * here...  Or set $a3 to zero and define DFLT_STACK_SIZE and
         * DFLT_HEAP_SIZE when you compile your program
         */
        mttgpr(6, v->ntcs);
        mttgpr(7, physical_memsize);

so the 0 for LANTIQ is fine with the correct VPE payload. But for
MALTA could cause major problems, if the VPE payload uses the top
of memory for it's stack. So I would guess nobody uses this "mode".
Therefore let's get rid of physical_memory in vpe.c completly.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-02-17 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  1:09 [PATCH] MIPS: vpe-mt: provide a default 'physical_memsize' Randy Dunlap
2023-02-14  7:40 ` Philippe Mathieu-Daudé
2023-02-14 18:29   ` Randy Dunlap
2023-02-16  6:59   ` Randy Dunlap
2023-02-17 11:57     ` Thomas Bogendoerfer [this message]
2023-02-17 20:04       ` Randy Dunlap
2023-02-17 23:24       ` Randy Dunlap
2023-02-19  8:40         ` Thomas Bogendoerfer

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=20230217115713.GA7701@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=dzhu@wavecomp.com \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=philmd@linaro.org \
    --cc=qyousef@layalina.io \
    --cc=rdunlap@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 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.