From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Cye Borg <cyborgyn@gmail.com>
Cc: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>,
"Jonathan Corbet" <corbet@lwn.net>,
"Federico Vaga" <federico.vaga@vaga.pv.it>,
"Alex Shi" <alexs@kernel.org>,
"Yanteng Si" <siyanteng@loongson.cn>,
"Hu Haowen" <src.res@email.cn>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc-tw-discuss@lists.sourceforge.net,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 08/15] MIPS: IP27: remove KV_MAGIC
Date: Fri, 11 Nov 2022 14:02:16 +0100 [thread overview]
Message-ID: <20221111130216.GA11187@alpha.franken.de> (raw)
In-Reply-To: <CAD4NMuYU6+JYGwCwDqGW5bTN8Rgg4SwseH9JKzjPAzsujBuCEw@mail.gmail.com>
On Fri, Nov 11, 2022 at 06:39:10AM +0100, Cye Borg wrote:
> Just asking:
> This code in SGI seems to help bring online other CPUs.
> - Does it use the firmware to do it?
> - Is there a possibility that the magic number in this case is used by the
> firmware?
> - If yes: do we break multiprocessing on SGI if we delete this "useless
> relic", which is not referenced in the linux code elsewhere?
this magic is just for a internal struct not used by firmware. It came
from IRIX code, but there is no point in keeping it
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2022-11-11 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 1:13 [PATCH v3 00/15] magic-number.rst funeral rites Ahelenia Ziemiańska
2022-11-11 1:14 ` [PATCH v3 08/15] MIPS: IP27: remove KV_MAGIC Ahelenia Ziemiańska
2022-11-11 5:40 ` Cye Borg
[not found] ` <CAD4NMuYU6+JYGwCwDqGW5bTN8Rgg4SwseH9JKzjPAzsujBuCEw@mail.gmail.com>
2022-11-11 13:02 ` Thomas Bogendoerfer [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=20221111130216.GA11187@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexs@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=cyborgyn@gmail.com \
--cc=federico.vaga@vaga.pv.it \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc-tw-discuss@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=siyanteng@loongson.cn \
--cc=src.res@email.cn \
/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;
as well as URLs for NNTP newsgroup(s).