All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ego@linux.vnet.ibm.com, emmanuel.nicolet@gmail.com,
	chenzhou10@huawei.com, jniethe5@gmail.com, linuxram@us.ibm.com,
	kernelfans@gmail.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	st5pub@yandex.ru, Oliver O'Halloran <oohall@gmail.com>,
	huhai@tj.kylinos.cn,
	Markus Elfring <elfring@users.sourceforge.net>,
	rzinsly@linux.ibm.com, leobras.c@gmail.com, mikey@neuling.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	haren@linux.ibm.com, michal.simek@xilinx.com,
	mahesh@linux.ibm.com, Takashi Iwai <tiwai@suse.de>,
	kjain@linux.ibm.com, leonardo@linux.ibm.com,
	"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	ajd@linux.ibm.com, Arnd Bergmann <arnd@arndb.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	alistair@popple.id.au, Nick Piggin <npiggin@gmail.com>,
	wangxiongfeng2@huawei.com, Qian Cai <cai@lca.pw>,
	clg@kaod.org, Nathan Chancellor <natechancellor@gmail.com>,
	hbathini@linux.ibm.com,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	geoff@infradead.org, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	wsa@kernel.org, sbobroff@linux.ibm.com, fbarrat@linux.ibm.com,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-5.8-1 tag
Date: Sat, 06 Jun 2020 10:45:37 +1000	[thread overview]
Message-ID: <87a71hggy6.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CAHk-=wh5vSwYqF=YiKOOGBHE=hCwnes_ndbP4QOyjPK_Xocz7w@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, Jun 5, 2020 at 9:38 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> I've pushed the result of my resolution of the conflicts to the powerpc/merge
>> branch, if you want to look at that, though I've also tried to describe it in
>> full below.
>
> I ended up doing the machine_check_exception() differently, because I
> felt the code itself was done wrong and I wanted to add a note about
> that.
>
> Having the same function have completely different semantics depending
> on a platform issue is just fundamentally wrong, and makes not just
> for fragile code, but also means that you can't do single image
> kernels.

Yeah I agree it's not that nicely structured.

In this case CONFIG_PPC_BOOK3S_64 is one of our top-level compile time
switches anyway, so the single image thing at least isn't a concern.

> It should be two different functions, possibly just
>
>    non_nmi_fn() { ... }
>
>    nmi_fn() { nmi_enter(); non_nmi_fn(); nmi_exit(); }
>
> and now you don't have odd rules for the same function that depends on
> how the platform happens to call it.

Agreed.

> I didn't do the above. I did something that looked like the old code,
> but had a comment. Oh well.

Thanks, we can restructure it later.

> But thanks for describing the merge, I'd have missed the place where
> there was a new use of pgd_oiffset().

Yeah I missed it to begin with :}

> ..and then when I actually compared whether I otherwise got the same
> result as you, I realized that this all depends on the module tree.
>
> I'll go merge that first, and then re-do this all. Oh well.

Darn it. I figured you'd have merged that by the time you saw my pull,
will mention anything similar in future.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	ajd@linux.ibm.com, alistair@popple.id.au,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
	Arnd Bergmann <arnd@arndb.de>, Qian Cai <cai@lca.pw>,
	chenzhou10@huawei.com,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	christophe.leroy@csgroup.eu, clg@kaod.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	ego@linux.vnet.ibm.com,
	Markus Elfring <elfring@users.sourceforge.net>,
	emmanuel.nicolet@gmail.com, fbarrat@linux.ibm.com,
	geoff@infradead.org,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	haren@linux.ibm.com, hbathini@linux.ibm.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	huhai@tj.kylinos.cn, jniethe5@gmail.com, kernelfans@gmail.com,
	kjain@linux.ibm.com, leobras.c@gmail.com, leonardo@linux.ibm.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linuxram@us.ibm.com, mahesh@linux.ibm.com,
	michal.simek@xilinx.com, mikey@neuling.org,
	Nathan Chancellor <natechancellor@gmail.com>,
	"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	Nick Piggin <npiggin@gmail.com>,
	Oliver O'Halloran <oohall@gmail.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	rzinsly@linux.ibm.com, sbobroff@linux.ibm.com,
	Segher Boessenkool <segher@kernel.crashing.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	st5pub@yandex.ru, Takashi Iwai <tiwai@suse.de>,
	wangxiongfeng2@huawei.com, wsa@kernel.org
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-5.8-1 tag
Date: Sat, 06 Jun 2020 10:45:37 +1000	[thread overview]
Message-ID: <87a71hggy6.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CAHk-=wh5vSwYqF=YiKOOGBHE=hCwnes_ndbP4QOyjPK_Xocz7w@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Fri, Jun 5, 2020 at 9:38 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> I've pushed the result of my resolution of the conflicts to the powerpc/merge
>> branch, if you want to look at that, though I've also tried to describe it in
>> full below.
>
> I ended up doing the machine_check_exception() differently, because I
> felt the code itself was done wrong and I wanted to add a note about
> that.
>
> Having the same function have completely different semantics depending
> on a platform issue is just fundamentally wrong, and makes not just
> for fragile code, but also means that you can't do single image
> kernels.

Yeah I agree it's not that nicely structured.

In this case CONFIG_PPC_BOOK3S_64 is one of our top-level compile time
switches anyway, so the single image thing at least isn't a concern.

> It should be two different functions, possibly just
>
>    non_nmi_fn() { ... }
>
>    nmi_fn() { nmi_enter(); non_nmi_fn(); nmi_exit(); }
>
> and now you don't have odd rules for the same function that depends on
> how the platform happens to call it.

Agreed.

> I didn't do the above. I did something that looked like the old code,
> but had a comment. Oh well.

Thanks, we can restructure it later.

> But thanks for describing the merge, I'd have missed the place where
> there was a new use of pgd_oiffset().

Yeah I missed it to begin with :}

> ..and then when I actually compared whether I otherwise got the same
> result as you, I realized that this all depends on the module tree.
>
> I'll go merge that first, and then re-do this all. Oh well.

Darn it. I figured you'd have merged that by the time you saw my pull,
will mention anything similar in future.

cheers

  parent reply	other threads:[~2020-06-06  0:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 16:38 [GIT PULL] Please pull powerpc/linux.git powerpc-5.8-1 tag Michael Ellerman
2020-06-05 16:38 ` Michael Ellerman
2020-06-05 19:01 ` Linus Torvalds
2020-06-05 19:01   ` Linus Torvalds
2020-06-05 20:39   ` Linus Torvalds
2020-06-05 20:39     ` Linus Torvalds
2020-06-06  0:50     ` Michael Ellerman
2020-06-06  0:50       ` Michael Ellerman
2020-06-06  0:45   ` Michael Ellerman [this message]
2020-06-06  0:45     ` Michael Ellerman
2020-06-05 20:40 ` pr-tracker-bot
2020-06-05 20:40   ` pr-tracker-bot

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=87a71hggy6.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=ajd@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alistair@popple.id.au \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=cai@lca.pw \
    --cc=chenzhou10@huawei.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=christophe.leroy@c-s.fr \
    --cc=clg@kaod.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ego@linux.vnet.ibm.com \
    --cc=elfring@users.sourceforge.net \
    --cc=emmanuel.nicolet@gmail.com \
    --cc=fbarrat@linux.ibm.com \
    --cc=geoff@infradead.org \
    --cc=gustavoars@kernel.org \
    --cc=haren@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=huhai@tj.kylinos.cn \
    --cc=jniethe5@gmail.com \
    --cc=kernelfans@gmail.com \
    --cc=kjain@linux.ibm.com \
    --cc=leobras.c@gmail.com \
    --cc=leonardo@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxram@us.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=michal.simek@xilinx.com \
    --cc=mikey@neuling.org \
    --cc=natechancellor@gmail.com \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=oohall@gmail.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=rzinsly@linux.ibm.com \
    --cc=sbobroff@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=st5pub@yandex.ru \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=wangxiongfeng2@huawei.com \
    --cc=wsa@kernel.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.