<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/powerpc/include/asm/firmware.h, branch linux-5.17.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.17.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2021-12-02T11:57:22Z</updated>
<entry>
<title>powerpc: Remove unused FW_FEATURE_NATIVE references</title>
<updated>2021-12-02T11:57:22Z</updated>
<author>
<name>Nicholas Piggin</name>
</author>
<published>2021-12-01T14:41:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=79b74a68486765a4fe685ac4069bc71366c538f5'/>
<id>urn:sha1:79b74a68486765a4fe685ac4069bc71366c538f5</id>
<content type='text'>
FW_FEATURE_NATIVE_ALWAYS and FW_FEATURE_NATIVE_POSSIBLE are always
zero and never do anything. Remove them.

Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20211201144153.2456614-2-npiggin@gmail.com

</content>
</entry>
<entry>
<title>powerpc/pseries: Add support for FORM2 associativity</title>
<updated>2021-08-13T12:04:27Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
</author>
<published>2021-08-12T13:22:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1c6b5a7e74052768977855f95d6b8812f6e7772c'/>
<id>urn:sha1:1c6b5a7e74052768977855f95d6b8812f6e7772c</id>
<content type='text'>
PAPR interface currently supports two different ways of communicating resource
grouping details to the OS. These are referred to as Form 0 and Form 1
associativity grouping. Form 0 is the older format and is now considered
deprecated. This patch adds another resource grouping named FORM2.

Signed-off-by: Daniel Henrique Barboza &lt;danielhb413@gmail.com&gt;
Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.ibm.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20210812132223.225214-6-aneesh.kumar@linux.ibm.com

</content>
</entry>
<entry>
<title>powerpc/pseries: Rename TYPE1_AFFINITY to FORM1_AFFINITY</title>
<updated>2021-08-13T12:04:26Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
</author>
<published>2021-08-12T13:22:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0eacd06bb8adea8dd9edb0a30144166d9f227e64'/>
<id>urn:sha1:0eacd06bb8adea8dd9edb0a30144166d9f227e64</id>
<content type='text'>
Also make related code cleanup that will allow adding FORM2_AFFINITY in
later patches. No functional change in this patch.

Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.ibm.com&gt;
Reviewed-by: David Gibson &lt;david@gibson.dropbear.id.au&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20210812132223.225214-3-aneesh.kumar@linux.ibm.com

</content>
</entry>
<entry>
<title>powerpc: remove unneeded semicolons</title>
<updated>2021-02-08T13:10:50Z</updated>
<author>
<name>Chengyang Fan</name>
</author>
<published>2021-01-25T09:53:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6c6fdbb2b7002aa04e418b5d2b26df1c5ba5ab80'/>
<id>urn:sha1:6c6fdbb2b7002aa04e418b5d2b26df1c5ba5ab80</id>
<content type='text'>
Remove superfluous semicolons after function definitions.

Signed-off-by: Chengyang Fan &lt;cy.fan@huawei.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20210125095338.1719405-1-cy.fan@huawei.com
</content>
</entry>
<entry>
<title>powerpc: Refactor is_kvm_guest() declaration to new header</title>
<updated>2020-12-03T14:01:21Z</updated>
<author>
<name>Srikar Dronamraju</name>
</author>
<published>2020-12-02T05:04:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=92cc6bf01c7f4c5cfefd1963985c0064687ebeda'/>
<id>urn:sha1:92cc6bf01c7f4c5cfefd1963985c0064687ebeda</id>
<content type='text'>
Only code/declaration movement, in anticipation of doing a KVM-aware
vcpu_is_preempted(). No additional changes.

Signed-off-by: Srikar Dronamraju &lt;srikar@linux.vnet.ibm.com&gt;
Acked-by: Waiman Long &lt;longman@redhat.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20201202050456.164005-2-srikar@linux.vnet.ibm.com
</content>
</entry>
<entry>
<title>powerpc/book3s64/radix: Add kernel command line option to disable radix GTSE</title>
<updated>2020-07-29T11:09:37Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
</author>
<published>2020-07-27T08:59:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bf6b7661f41615c0815fce0a3f27acb5fc005470'/>
<id>urn:sha1:bf6b7661f41615c0815fce0a3f27acb5fc005470</id>
<content type='text'>
This adds a kernel command line option that can be used to disable GTSE support.
Disabling GTSE implies kernel will make hcalls to invalidate TLB entries.

This was done so that we can do VM migration between configs that enable/disable
GTSE support via hypervisor. To migrate a VM from a system that supports
GTSE to a system that doesn't, we can boot the guest with
radix_hcall_invalidate=on, thereby forcing the guest to use hcalls for TLB
invalidates.

The check for hcall availability is done in pSeries_setup_arch so that
the panic message appears on the console. This should only happen on
a hypervisor that doesn't force the guest to hash translation even
though it can't handle the radix GTSE=0 request via CAS. With
radix_hcall_invalidate=on if the hypervisor doesn't support hcall_rpt_invalidate
hcall it should force the LPAR to hash translation.

Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.ibm.com&gt;
Tested-by: Bharata B Rao &lt;bharata@linux.ibm.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20200727085908.420806-1-aneesh.kumar@linux.ibm.com
</content>
</entry>
<entry>
<title>powerpc/pseries: Add KVM guest doorbell restrictions</title>
<updated>2020-07-29T11:02:10Z</updated>
<author>
<name>Nicholas Piggin</name>
</author>
<published>2020-07-26T03:51:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=107c55005fbd5243ee31fb13b6f166cde9e3ade1'/>
<id>urn:sha1:107c55005fbd5243ee31fb13b6f166cde9e3ade1</id>
<content type='text'>
KVM guests have certain restrictions and performance quirks when using
doorbells. This patch moves the EPAPR KVM guest test so it can be shared
with PSERIES, and uses that in doorbell setup code to apply the KVM
guest quirks and  improves IPI performance for two cases:

 - PowerVM guests may now use doorbells even if they are secure.

 - KVM guests no longer use doorbells if XIVE is available.

There is a valid complaint that "KVM guest" is not a very reasonable
thing to test for, it's preferable for the hypervisor to advertise
particular behaviours to the guest so they could change if the
hypervisor implementation or configuration changes. However in this case
we were already assuming a KVM guest worst case, so this patch is about
containing those quirks. If KVM later advertises fast doorbells, we
should test for that and override the quirks.

Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;
Tested-by: Cédric Le Goater &lt;clg@kaod.org&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20200726035155.1424103-4-npiggin@gmail.com
</content>
</entry>
<entry>
<title>powerpc/pseries/ras: Avoid calling rtas_token() in NMI paths</title>
<updated>2020-05-18T11:58:45Z</updated>
<author>
<name>Nicholas Piggin</name>
</author>
<published>2020-05-08T04:33:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7368b38b21bfa39df637701a480262c15ab1a49e'/>
<id>urn:sha1:7368b38b21bfa39df637701a480262c15ab1a49e</id>
<content type='text'>
In the interest of reducing code and possible failures in the
machine check and system reset paths, grab the "ibm,nmi-interlock"
token at init time.

Signed-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Reviewed-by: Christophe Leroy &lt;christophe.leroy@c-s.fr&gt;
Reviewed-by: Mahesh Salgaonkar &lt;mahesh@linux.ibm.com&gt;
Link: https://lore.kernel.org/r/20200508043408.886394-6-npiggin@gmail.com
</content>
</entry>
<entry>
<title>powerpc/pseries/iommu: Separate FW_FEATURE_MULTITCE to put/stuff features</title>
<updated>2020-01-06T05:25:30Z</updated>
<author>
<name>Alexey Kardashevskiy</name>
</author>
<published>2019-12-16T04:19:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=17a0364cb07c173f64cefe973a93b8dbd9c61795'/>
<id>urn:sha1:17a0364cb07c173f64cefe973a93b8dbd9c61795</id>
<content type='text'>
H_PUT_TCE_INDIRECT allows packing up to 512 TCE updates into a single
hypercall; H_STUFF_TCE can clear lots in a single hypercall too.

However, unlike H_STUFF_TCE (which writes the same TCE to all entries),
H_PUT_TCE_INDIRECT uses a 4K page with new TCEs. In a secure VM
environment this means sharing a secure VM page with a hypervisor which
we would rather avoid.

This splits the FW_FEATURE_MULTITCE feature into FW_FEATURE_PUT_TCE_IND
and FW_FEATURE_STUFF_TCE. "hcall-multi-tce" in
the "/rtas/ibm,hypertas-functions" device tree property sets both;
the "multitce=off" kernel command line parameter disables both.

This should not cause behavioural change.

Signed-off-by: Alexey Kardashevskiy &lt;aik@ozlabs.ru&gt;
Reviewed-by: Thiago Jung Bauermann &lt;bauerman@linux.ibm.com&gt;
Tested-by: Thiago Jung Bauermann &lt;bauerman@linux.ibm.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20191216041924.42318-4-aik@ozlabs.ru
</content>
</entry>
<entry>
<title>powerpc/powernv: Introduce FW_FEATURE_ULTRAVISOR</title>
<updated>2019-08-29T23:40:15Z</updated>
<author>
<name>Claudio Carvalho</name>
</author>
<published>2019-08-22T03:48:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb04ffe85eebebd64d5e673a9434d968e80f3aa1'/>
<id>urn:sha1:bb04ffe85eebebd64d5e673a9434d968e80f3aa1</id>
<content type='text'>
In PEF enabled systems, some of the resources which were previously
hypervisor privileged are now ultravisor privileged and controlled by
the ultravisor firmware.

This adds FW_FEATURE_ULTRAVISOR to indicate if PEF is enabled.

The host kernel can use FW_FEATURE_ULTRAVISOR, for instance, to skip
accessing resources (e.g. PTCR and LDBAR) in case PEF is enabled.

Signed-off-by: Claudio Carvalho &lt;cclaudio@linux.ibm.com&gt;
[ andmike: Device node name to "ibm,ultravisor" ]
Signed-off-by: Michael Anderson &lt;andmike@linux.ibm.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Link: https://lore.kernel.org/r/20190822034838.27876-4-cclaudio@linux.ibm.com
</content>
</entry>
</feed>
