In D15911#337606, @markj wrote:

I note that arm64 has this bug as well. I'll fix that identically if the current diff is ok.

Use git tags on GH_TUPLE.

Remove redundant ecam quirk.

Added obtaining ecam and bus number from ACPI. This allows us to remove ThunderX2 quirk connected with ecam.

In D10600#337622, @bcr wrote:

So, you're saying the we need testers for this configuration before we put it in the handbook as official instructions?

Done.

Fix the SMCCC_ARCH_WORKAROUND_2 function ID

• Only set "reclaimed" once when executing the loop.
• Fix the problem in the arm64 pmap code.

Apologies for the delay. Would anyone with a Ryzen or TR be able to test a microcode update with the updated patch applied?

Only update microcode on physical CPUs.

As I said I believe it is fine functionally.

In D15905#337248, @cem wrote:

The code may have been in-tree, but it was not used. Also, I think it did more than just that, but I don't recall. What were the ramifications of using it, and was there a good reason it was never enabled? Or just inertia? Feel free to reverse the default if it makes sense — I just want one copy of the interrupt code.

By the way, here is a "purified" variant of the interrupt handling code without all the complications of the interrupt threads, software interrupts, interactions with other subsystems, etc.
This is purely a list of handlers that can be iterated in a wait-free manner.
I think that it could be used, for example, for installing NMI handlers in a more regular fashion than what we have now.
https://reviews.freebsd.org/P185
I hope that that code makes the idea behind this change a little bit more clear.

In D15907#337807, @mat wrote:

Mmmm, what commands did you run that generated a bad distinfo file?

exp-run

Thanks for your report. Fixed along with a couple of other issues noticed.

You should start with an "svn mv" of one of the old ones, so that there still is some of the history present.

Adding maintainer and portmgr (for flavors).

In D15958#337880, @lbdm_privacychain.ch wrote:

Should CONFLICT_INSTALL be set with the old packages names?

Thanks!

Someone found that having EVDEV in the kernel config causes buildkernel to fail in if_ixl: