10-13-2005
I found that the knlist API is returning proper offset into the /dev/kmem file but the problem occurs when the dual core capability of the cpu is turned on the value is not getting properly updated in the /dev/kmem file. But the valu in /dev/kmem is updated properly if the dual core capability is turned -off.
Could anyone please let me know if it is a problem with the AIX 5.3??
Thanks.
10 More Discussions You Might Find Interesting
1. AIX
Machine and OS : IBM 7044-170 AIX 4.3.3
Hi, everyone
I have a question , pls help me to resolve. In IBM AIX , how to obtain the CPU Load and other infomations by System API Fuction.
Wait for your reply ......., Thanks. (0 Replies)
Discussion started by: q30
0 Replies
2. AIX
I have encountered a problem that I cannot resolve. We have two
different AIX 5.3 boxes. On one box, regardless of whether it is
booted in 32 bit mode or 64 bit mode, I can obtain kernel metrics (i.e,
using kernel symbol names sysinfo or avenrun) via the nlink or nlink64
system call. On... (0 Replies)
Discussion started by: lawrence
0 Replies
3. AIX
Hi all,
I have a AIX 5.3 Installation on the Power5 processor. I am using the knlist API for getting the details of the CPU details like user cpu, kernel cpu, idle cpu and wait cpu. My code is working fine on other Installations of AIX like PowerPC_POWER4 but it is giving wrong values on Power5... (0 Replies)
Discussion started by: rajesht
0 Replies
4. Programming
Hi,
I've just been experimenting with AIX's ldapsearch utility - I've been successfully using it to retrieve information from an Active Directory, however, I need to make similar calls from a C program.
Is there a suitable LDAP API on AIX which will give me similar capabilties to the... (3 Replies)
Discussion started by: phykell
3 Replies
5. AIX
Hi,
I am looking for just the JMS C API libraries for AIX (hopfully I don't have to install websphere!), I have found them for Sun, HP and Linux, but not for AIX. Can someone point me in the right direction? Thanks! (0 Replies)
Discussion started by: CTBlack
0 Replies
6. Programming
Hi,
I'm trying to locate the API information that is used for system programming on IBM's AIX operating system and other programming resources for AIX (language C/C++), I've had a look around the IBM website/Internet but I don't seem to be able to find anything that is up to date. This... (1 Reply)
Discussion started by: warlockuk
1 Replies
7. Programming
Hi:
Well, i need to do a program for control the labs time of the students in my university. This program that I have to do it got to be on C++ or C, and have to do a several things like, check all the process that the user execute when he star his session on KDE or console, sometime close an no... (0 Replies)
Discussion started by: leonel06033
0 Replies
8. Programming
Does anyone have any example of how to use the perl api within Build Forge (0 Replies)
Discussion started by: saku
0 Replies
9. Shell Programming and Scripting
Hi,
I need to call an API (GetUsageDetails)from inside a shell script which takes an input argument acct_nbr.
The output of API will be like :
<usageAccum accumId="450" accumCaptn="PM_125" inclUnits="1410.00" inclUnitsUsed="744.00" shared="true" pooled="false" prorated="false"... (1 Reply)
Discussion started by: rkrish
1 Replies
10. Web Development
Ref:
https://itnext.io/face-api-js-javascript-api-for-face-recognition-in-the-browser-with-tensorflow-js-bcc2a6c4cf07 (0 Replies)
Discussion started by: Neo
0 Replies
MEM(4) Linux Programmer's Manual MEM(4)
NAME
mem, kmem, port - system memory, kernel memory and system ports
DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even
patch) the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned.
Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present.
Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be
accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is.
It is typically created by:
mknod -m 660 /dev/mem c 1 1
chown root:kmem /dev/mem
The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux
2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled.
It is typically created by:
mknod -m 640 /dev/kmem c 1 2
chown root:kmem /dev/kmem
/dev/port is similar to /dev/mem, but the I/O ports are accessed.
It is typically created by:
mknod -m 660 /dev/port c 1 4
chown root:kmem /dev/port
FILES
/dev/mem
/dev/kmem
/dev/port
SEE ALSO
chown(1), mknod(1), ioperm(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2015-01-02 MEM(4)