-
I'm looking for some clarity on the Process Metrics.
Specifically, why is "process.memory.usage" defined as "physical memory"?
https://github.com/open-telemetry/semantic-conventions/blob/main/docs/s…
-
Hi,
The `Zjpm` spec mentions two different types of transformations:
1. Ignore transformation on the virtual address
2. Ignore transformation on the physical address
It also specifies that `M…
-
### systemd version the issue has been seen with
256.7
### Used distribution
NixOS 24.11 (unstable)
### Linux kernel version used
6.11.2-asahi
### CPU architectures issue was seen on…
-
Hi,
I have tried running Neothesia on Devuan but, as soon as I start it, all the 7 processons on my CPU jump to 90% usage.
Is there a way to avoid this behavior?
Thanks.
-
### Describe the bug
Filing a ticket based on a conversation in discord: https://discord.com/channels/885562378132000778/1166447479609376850/1275728622224932959
Basically, I expect that when prope…
alamb updated
2 months ago
-
Users reported a discrepancy between `get_mem_status` and `get_mem_avail`. In particular it seems that `get_mem_status` is only showing ~40% of the memory allocated to the server
-
Kernel can't boot with the physical memory larger than 128G.
Reproduce method:
Set QEMU args in `tools/qemu_args.sh`:
```rust
-m ${MEM:-128G}
```
-
So basically, when I try to read a phyiscal address (e.g. looping through physical ranges) it bsods without any reason. When I read that value using another driver and MmCopyMemory, it just works fine…
-
OVSRV6:
`C:\ProjDir\Jip\_Github_issues\2BURP_issue830\cfg\main.dms`
This item:
`/sourcedata/Physical/SnowIceCover/ReadData`
defined as:
`attribute ReadData (domain);`
The tif file is in Mo…
-
When HyperRAM is enabled, the the SRAM address bus is only 17 bits wide but `ADDR_MASK_SRAM` is still `32'h 0003ffff`, leading to reads from/writes to addresses 0x00120000-0x0013ffff being accepted b…