[SPIRV] Handle `externally_initialized` for AMDGCN flavoured SPIRV (#175277)
SPIR-V doesn't currently have a way to encode the `externally_initialized` LLVM concept. Unfortunately, certain HIP constructs (e.g. `__managed__` or `__constant__` variables) rely on it. Hence, this patch allows AMDGCN flavoured SPIR-V to encode `externally_initialized` via the `HostAccessINTEL` decoration, which approximates some of the semantics; the decoration is handled during reverse translation. It also appears that we never fully implemented the decoration, which I intend to handle in a subsequent, independent patch.
[mlir][spirv] Allow complex element types in memref allocation checks (#175836)
Support for complex types in SPIR-V was introduced in
97f3bb73a29a566e99e33ae4338c2c3d9957e561, and memref type conversion was
updated accordingly to include them. However, the element type precheck
used during memref alloc/dealloc pattern matching in the SPIR-V lowering
was not updated to recognize complex element types. This patch resolves
this inconsistency.
Fixes: https://github.com/iree-org/iree/issues/23117
---------
Signed-off-by: Eric Feng <Eric.Feng at amd.com>
[AMDGPU] Return two MMOs for load-to-lds and store-from-lds intrinsics
Accurately represent both the load and the store part of those
intrinsics.
The test changes seem to be mostly fairly insignificant changes caused by
subtly different scheduler behavior.
commit-id:0269189c
[CodeGen] Refactor targets to override the new getTgtMemIntrinsic overload (NFC)
This is a fairly mechanical change. Instead of returning true/false,
we either keep the Infos vector empty or push one entry.
commit-id:c7770af6
[CodeGen] Add getTgtMemIntrinsic overload for multiple memory operands (NFC)
There are target intrinsics that logically require two MMOs, such as
llvm.amdgcn.global.load.lds, which is a copy from global memory to LDS,
so there's both a load and a store to different addresses.
Add an overload of getTgtMemIntrinsic that produces intrinsic info in a
vector, and implement it in terms of the existing (now protected)
overload.
GlobalISel and SelectionDAG paths are updated to support multiple MMOs.
The main part of this change is supporting multiple MMOs in
MemIntrinsicNodes.
Converting the backends to using the new overload is a fairly mechanical step
that is done in a separate change in the hope that that allows reducing merging
pains during review and for downstreams. A later change will then enable
using multiple MMOs in AMDGPU.
commit-id:b4a924aa
Remove support for validating Geofeed data
RPKI-based Geofeed authentication (RFC 9632) perhaps was a bit of a ruse
to pass IESG review. Nobody is planning on using it. Time to take it
behind the barn.
OK tb@
enc: create an interface at SI_SUB_PROTO_IF stage
Creation of enc0 before SI_SUB_PROTO_MC mangles the MLD list as well as
encounters IGMP mutex not initialized yet.
Reported & tested by: mjg
NB: the enc(4) is not a true interface indeed. In a perfect world the
module shall not create a cloner, shall not enter if_attach(), shall not
trigger ifnet_arrival_event, neither shall have any protocol attached to
it. The enc0 exists for two purposes: 1) create a bpf(9) tap; 2) to allow
injection packets in the middle of ipsec(4) processing temporarily
rewriting m_pkthdr.rcvif to point at enc0. While the problem 1 is already
solved with a recent divorce between bpf(9) and ifnet(9), the problem 2 is
harder to solve without breaking packet filter rules that use "via enc0".
[LLVM] Clean up code using [not_]equal_to (NFC) (#175824)
Use llvm::[not_]equal_to landed in d2a521750 ([ADT] Introduce
bind_{front,back}, [not_]equal_to, #175056) across LLVM for cleaner
code.
NAS-139297 / 26.04 / Add clustered SMB state (#18017)
This commit adds working configuration for stateful SMB HA failover:
* reclock helper script - determines which node holds the cluster mutex
lock based on presence of data pool system dataset.
* ctdb-related etc files. We can hard-code the nodes config based on our
known HA nodes (this significantly eases past problems with gluster that
we saw with dynamic nodes and ctdb stability).
* smbd will remain stopped on standby controller until it becomes
standby.
* keepalived will continue to manage virtual IPs
During failover events, ctdbd on the new active controller will grab the
cluster mutex after system dataset pool import and begin recovery
operation. Administrators will need to disabling stateful failover while
[7 lines not shown]
[llvm-cov] Add show-function-summary option in coverage report (#172980)
Adds a command line argument to llvm-cov to optionally disable the
function summary in the coverage report (but maintaining existing
behavior by keeping it enabled by default).
Add clustered SMB state
This commit adds working configuration for stateful SMB HA failover:
* reclock helper script - determines which node holds the cluster
mutex lock based on presence of data pool system dataset.
* ctdb-related etc files. We can hard-code the nodes config based
on our known HA nodes (this significantly eases past problems with
gluster that we saw with dynamic nodes and ctdb stability).
* smbd will remain stopped on standby controller until it becomes
standby.
* keepalived will continue to manage virtual IPs
NAS-139251 / 25.10.2 / Fix netdata plugin startup delay for disk temp and pool stats (by Qubad786) (#17994)
## Problem
Currently when netdata is restarted, for each plugin it gives data after
`2 * update every frequency` seconds. So for example, if a plugin data
is to be collected every 5 min, we get datapoints after 10 minutes which
is an unnecessary delay added by how netdata implements `SimpleService`.
## Solution
We have overridden default `SimpleService` to not sleep as soon as it
runs but rather collect data after initialization and then sleep. This
means that we now get data after every `update every frequency` which if
it is 5 min, we will get data after 5 min instead of 10.
The 5 min delay which we still see is because of how netdata dbengine
stores/aligns data and there is no good way around that as that logic
lives in core netdata.
[5 lines not shown]
NAS-139298 / 25.10.2 / Add 'limit' option to 'audit.query' call. (by mgrimesix) (#18019)
`audit.query` calls must include either a `count` or `limit` option,
else the test will fail.
Added the missing `limit` option for the `test_system_reboot` test in
`test_system_lifetime.py`
Original PR: https://github.com/truenas/middleware/pull/18018
Co-authored-by: Mark Grimes <mark.grimes at ixsystems.com>
