All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <1205bfc10c62986b4345fa258cf37e820c08226b.camel@neuling.org>

diff --git a/a/1.txt b/N1/1.txt
index 63dc213..1a1ef5b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,8 +1,8 @@
 On Wed, 2018-07-18 at 13:42 +0530, Gautham R Shenoy wrote:
 > Hello Mikey,
-> 
+>=20
 > On Wed, Jul 18, 2018 at 09:24:19AM +1000, Michael Neuling wrote:
-> > 
+> >=20
 > > >  	DEFINE(PPC_DBELL_SERVER, PPC_DBELL_SERVER);
 > > > diff --git a/arch/powerpc/kernel/idle_book3s.S
 > > > b/arch/powerpc/kernel/idle_book3s.S
@@ -16,31 +16,38 @@ On Wed, 2018-07-18 at 13:42 +0530, Gautham R Shenoy wrote:
 > > > +
 > > > +	mfspr	r3, SPRN_SPRG3
 > > > +	std	r3, STOP_SPRG3(r13)
-> > 
-> > We don't need to save it.  Just restore it from paca->sprg_vdso which should
+> >=20
+> > We don't need to save it.  Just restore it from paca->sprg_vdso which s=
+hould
 > > never change.
-> 
+>=20
 > Ok. I will respin a patch to restore SPRG3 from paca->sprg_vdso.
-> 
-> > 
+>=20
+> >=20
 > > How can we do better at catching these missing SPRGs?
-> 
+>=20
 > We can go through the list of SPRs from the POWER9 User Manual and
 > document explicitly why we don't have to save/restore certain SPRs
 > during the execution of the stop instruction. Does this sound ok ?
-> 
+>=20
 > (Ref: Table 4-8, Section 4.7.3.4 from the POWER9 User Manual
 > accessible from
-> https://openpowerfoundation.org/?resource_lib=power9-processor-users-manual)
+> https://openpowerfoundation.org/?resource_lib=3Dpower9-processor-users-ma=
+nual)
 
-I was thinking of a boot time test case built into linux. linux has some boot
+I was thinking of a boot time test case built into linux. linux has some bo=
+ot
 time test cases which you can enable via CONFIG options.
 
 Firstly you could see if an SPR exists using the same trick xmon does in
-dump_one_spr(). Then once you have a list of usable SPRs, you could write all
-the known ones (I assume you'd have to leave out some, like the PSSCR), then set
-the appropriate stop level, make sure you got into that stop level, and then see
-if that register was changed. Then you'd have an automated list of registers you
+dump_one_spr(). Then once you have a list of usable SPRs, you could write a=
+ll
+the known ones (I assume you'd have to leave out some, like the PSSCR), the=
+n set
+the appropriate stop level, make sure you got into that stop level, and the=
+n see
+if that register was changed. Then you'd have an automated list of register=
+s you
 need to make sure you save/restore at each stop level.
 
 Could something like that work?
diff --git a/a/content_digest b/N1/content_digest
index b2666d5..57300a2 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -40,9 +40,9 @@
 [
   "On Wed, 2018-07-18 at 13:42 +0530, Gautham R Shenoy wrote:\n",
   "> Hello Mikey,\n",
-  "> \n",
+  ">=20\n",
   "> On Wed, Jul 18, 2018 at 09:24:19AM +1000, Michael Neuling wrote:\n",
-  "> > \n",
+  "> >=20\n",
   "> > >  \tDEFINE(PPC_DBELL_SERVER, PPC_DBELL_SERVER);\n",
   "> > > diff --git a/arch/powerpc/kernel/idle_book3s.S\n",
   "> > > b/arch/powerpc/kernel/idle_book3s.S\n",
@@ -56,31 +56,38 @@
   "> > > +\n",
   "> > > +\tmfspr\tr3, SPRN_SPRG3\n",
   "> > > +\tstd\tr3, STOP_SPRG3(r13)\n",
-  "> > \n",
-  "> > We don't need to save it.  Just restore it from paca->sprg_vdso which should\n",
+  "> >=20\n",
+  "> > We don't need to save it.  Just restore it from paca->sprg_vdso which s=\n",
+  "hould\n",
   "> > never change.\n",
-  "> \n",
+  ">=20\n",
   "> Ok. I will respin a patch to restore SPRG3 from paca->sprg_vdso.\n",
-  "> \n",
-  "> > \n",
+  ">=20\n",
+  "> >=20\n",
   "> > How can we do better at catching these missing SPRGs?\n",
-  "> \n",
+  ">=20\n",
   "> We can go through the list of SPRs from the POWER9 User Manual and\n",
   "> document explicitly why we don't have to save/restore certain SPRs\n",
   "> during the execution of the stop instruction. Does this sound ok ?\n",
-  "> \n",
+  ">=20\n",
   "> (Ref: Table 4-8, Section 4.7.3.4 from the POWER9 User Manual\n",
   "> accessible from\n",
-  "> https://openpowerfoundation.org/?resource_lib=power9-processor-users-manual)\n",
+  "> https://openpowerfoundation.org/?resource_lib=3Dpower9-processor-users-ma=\n",
+  "nual)\n",
   "\n",
-  "I was thinking of a boot time test case built into linux. linux has some boot\n",
+  "I was thinking of a boot time test case built into linux. linux has some bo=\n",
+  "ot\n",
   "time test cases which you can enable via CONFIG options.\n",
   "\n",
   "Firstly you could see if an SPR exists using the same trick xmon does in\n",
-  "dump_one_spr(). Then once you have a list of usable SPRs, you could write all\n",
-  "the known ones (I assume you'd have to leave out some, like the PSSCR), then set\n",
-  "the appropriate stop level, make sure you got into that stop level, and then see\n",
-  "if that register was changed. Then you'd have an automated list of registers you\n",
+  "dump_one_spr(). Then once you have a list of usable SPRs, you could write a=\n",
+  "ll\n",
+  "the known ones (I assume you'd have to leave out some, like the PSSCR), the=\n",
+  "n set\n",
+  "the appropriate stop level, make sure you got into that stop level, and the=\n",
+  "n see\n",
+  "if that register was changed. Then you'd have an automated list of register=\n",
+  "s you\n",
   "need to make sure you save/restore at each stop level.\n",
   "\n",
   "Could something like that work?\n",
@@ -88,4 +95,4 @@
   "Mikey"
 ]
 
-935de4e8249327084ae5df305cc91bfa2692d054965447cff1e6f85f5c05801b
+bb988e633c1f6dfd06e1f758c5fa7ae54047e3723b0f81a96353354887b71fe0
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.