<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/powerpc, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/'/>
<entry>
<title>powerpc64: fix builds</title>
<updated>2026-04-17T19:32:48+00:00</updated>
<author>
<name>Adrian Chadd</name>
<email>adrian@FreeBSD.org</email>
</author>
<published>2026-04-17T19:32:23+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=b4be4a7890e7f3a94acc08440e28d480434f5bb8'/>
<id>b4be4a7890e7f3a94acc08440e28d480434f5bb8</id>
<content type='text'>
Oops, I missed 'device ix' in here, and it now requires mdio.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Oops, I missed 'device ix' in here, and it now requires mdio.
</pre>
</div>
</content>
</entry>
<entry>
<title>powerpc/intr setup: Don't check intr name for IPI</title>
<updated>2026-04-16T22:37:01+00:00</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2026-04-16T22:37:01+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=a249ddf07873be97967dd83df4d098ea95d0c92a'/>
<id>a249ddf07873be97967dd83df4d098ea95d0c92a</id>
<content type='text'>
Since whether or not the irq is an IPI is passed into
powerpc_setup_intr_int(), use this as the check for IPI instead of
checking the name string.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since whether or not the irq is an IPI is passed into
powerpc_setup_intr_int(), use this as the check for IPI instead of
checking the name string.
</pre>
</div>
</content>
</entry>
<entry>
<title>mpc85xx: Support timebase sync on T-series devices</title>
<updated>2026-04-16T22:36:54+00:00</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2026-04-16T22:36:54+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=603a29b9b3126763c934afbed64fc43bf539469b'/>
<id>603a29b9b3126763c934afbed64fc43bf539469b</id>
<content type='text'>
Freescale T-series QorIQ devices use a different register to twiddle the
timebase enable.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Freescale T-series QorIQ devices use a different register to twiddle the
timebase enable.
</pre>
</div>
</content>
</entry>
<entry>
<title>powerpc/pmap: Add support for page sizes found on E6500</title>
<updated>2026-04-16T22:35:52+00:00</updated>
<author>
<name>Justin Hibbits</name>
<email>jhibbits@FreeBSD.org</email>
</author>
<published>2026-02-01T03:44:21+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=1fc50a4e68a1635f76d24694fc6ea8b94193c087'/>
<id>1fc50a4e68a1635f76d24694fc6ea8b94193c087</id>
<content type='text'>
E6500 cores (MMUv2) support all powers-of-2 page sizes from 4k to 1TB,
not just powers of 4.  By using the other page sizes (8k, 32k, etc) we
can save on TLB1 space, saving up to ~1/3 of used TLB1 entries.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
E6500 cores (MMUv2) support all powers-of-2 page sizes from 4k to 1TB,
not just powers of 4.  By using the other page sizes (8k, 32k, etc) we
can save on TLB1 space, saving up to ~1/3 of used TLB1 entries.
</pre>
</div>
</content>
</entry>
<entry>
<title>pmap: Do not use PMAP_LOCK_INIT with kernel_pmap</title>
<updated>2026-04-01T11:15:42+00:00</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2026-04-01T09:15:26+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=c6a1c1260f02e44b7f44b1e3735ce5dbd785544d'/>
<id>c6a1c1260f02e44b7f44b1e3735ce5dbd785544d</id>
<content type='text'>
The kernel_pmap lock is a bit special: it does not need the DUPOK flag,
and it really belongs to a different lock class.  If it belongs to the
same class as regular pmap locks, then witness may report warnings when
performing UMA allocations under a regular pmap lock, if the allocation
triggers a pmap_growkernel() call.

Replace instances of PMAP_LOCK_INIT(kernel_pmap) with inline mtx_init()
calls to silence some witness warnings for harmless behaviour I see with
some uncommitted test programs.

Reviewed by:	alc, kib
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D56185
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The kernel_pmap lock is a bit special: it does not need the DUPOK flag,
and it really belongs to a different lock class.  If it belongs to the
same class as regular pmap locks, then witness may report warnings when
performing UMA allocations under a regular pmap lock, if the allocation
triggers a pmap_growkernel() call.

Replace instances of PMAP_LOCK_INIT(kernel_pmap) with inline mtx_init()
calls to silence some witness warnings for harmless behaviour I see with
some uncommitted test programs.

Reviewed by:	alc, kib
MFC after:	2 weeks
Differential Revision:	https://reviews.freebsd.org/D56185
</pre>
</div>
</content>
</entry>
<entry>
<title>routing: Retire ROUTE_MPATH compile option</title>
<updated>2026-03-27T20:25:33+00:00</updated>
<author>
<name>Pouria Mousavizadeh Tehrani</name>
<email>pouria@FreeBSD.org</email>
</author>
<published>2026-03-27T11:20:05+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=254b23eb1f540844cf2a90f2781ae4231c5701ce'/>
<id>254b23eb1f540844cf2a90f2781ae4231c5701ce</id>
<content type='text'>
The ROUTE_MPATH compile option was introduced to
test the new multipath implementation.
Since compiling it has no overhead and it's enabled
by default, remove it.

Reviewed by:	melifaro, markj
Relnotes:	yes
Differential Revision: https://reviews.freebsd.org/D55884
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The ROUTE_MPATH compile option was introduced to
test the new multipath implementation.
Since compiling it has no overhead and it's enabled
by default, remove it.

Reviewed by:	melifaro, markj
Relnotes:	yes
Differential Revision: https://reviews.freebsd.org/D55884
</pre>
</div>
</content>
</entry>
<entry>
<title>kernel: Be clearer about what ZSTDIO is for</title>
<updated>2026-03-21T07:21:45+00:00</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2026-03-21T07:21:24+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=092687a031064dc08ac198648c6393cc50b06cee'/>
<id>092687a031064dc08ac198648c6393cc50b06cee</id>
<content type='text'>
ZSTDIO is not just for core dumps, and it is now required by ZFS, so
move it (and GZIO, which is still just for dumps) to a new “Compression
support” section in GENERIC, and add them both to MINIMAL.

MFC after:	1 week
Reviewed by:	imp
Differential Revision:	https://reviews.freebsd.org/D55940
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ZSTDIO is not just for core dumps, and it is now required by ZFS, so
move it (and GZIO, which is still just for dumps) to a new “Compression
support” section in GENERIC, and add them both to MINIMAL.

MFC after:	1 week
Reviewed by:	imp
Differential Revision:	https://reviews.freebsd.org/D55940
</pre>
</div>
</content>
</entry>
<entry>
<title>powerpc64: initial conversion of oea64 to rwlocks</title>
<updated>2026-02-22T02:22:46+00:00</updated>
<author>
<name>Adrian Chadd</name>
<email>adrian@FreeBSD.org</email>
</author>
<published>2026-02-22T02:22:46+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=19a18bb750e8ed88207664b4959e433b7e68e926'/>
<id>19a18bb750e8ed88207664b4959e433b7e68e926</id>
<content type='text'>
Convert the oea64 mmu code to rwlocks.

Reviewed by:	jhibbits
Differential Revision:	https://reviews.freebsd.org/D54936
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Convert the oea64 mmu code to rwlocks.

Reviewed by:	jhibbits
Differential Revision:	https://reviews.freebsd.org/D54936
</pre>
</div>
</content>
</entry>
<entry>
<title>bus: Document special ranges of IVARs</title>
<updated>2026-02-17T20:45:13+00:00</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2026-02-17T20:45:13+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=6cf4e30252fe48b230b9d76cac20576d5b3d2ffa'/>
<id>6cf4e30252fe48b230b9d76cac20576d5b3d2ffa</id>
<content type='text'>
Some IVAR indices are special in that they have global meaning across
multiple buses where as other IVARs are always private to the local bus.
Try to document this a bit and add constants for the various ranges to
avoid future conflicts.

This is a no-op, but IVAR indices are now generally defined as enums
as that makes it easier to define them in terms of ranges.

Reviewed by:	imp, royger, andrew
Differential Revision:	https://reviews.freebsd.org/D54159
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some IVAR indices are special in that they have global meaning across
multiple buses where as other IVARs are always private to the local bus.
Try to document this a bit and add constants for the various ranges to
avoid future conflicts.

This is a no-op, but IVAR indices are now generally defined as enums
as that makes it easier to define them in terms of ranges.

Reviewed by:	imp, royger, andrew
Differential Revision:	https://reviews.freebsd.org/D54159
</pre>
</div>
</content>
</entry>
<entry>
<title>powerpc: document the magic constants for 16MB page size</title>
<updated>2026-02-16T17:49:52+00:00</updated>
<author>
<name>Adrian Chadd</name>
<email>adrian@FreeBSD.org</email>
</author>
<published>2026-02-16T17:49:52+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=995090202cae47567cc5b0d92301692d49c1c035'/>
<id>995090202cae47567cc5b0d92301692d49c1c035</id>
<content type='text'>
After discussion with jhibbits@, we pulled out what is supported here
and how it's supported.

Reviewed by:	imp
Differential Revision:	https://reviews.freebsd.org/D55093
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
After discussion with jhibbits@, we pulled out what is supported here
and how it's supported.

Reviewed by:	imp
Differential Revision:	https://reviews.freebsd.org/D55093
</pre>
</div>
</content>
</entry>
</feed>
