Re: [osol-code] Local syslog messages getting dropped?

On 07/23/10 12:10, Paul Robertson wrote: Our application calls syslog(3c) to write to the local syslog daemon, and we were puzzled when some messages weren't appearing in the local /var/adm/messages file. We wrote a test program to spew 6 unique messages, and confirmed that not all syslog cal

Re: [osol-code] who call sys_rtt_common() function in the kernel?

Peter Teoh wrote: sorry..i think i know who is the caller: but the intent is still vague for me? "rtt" is "return from trap". We were peacefully executing some code - may be userland, maybe privileged - and took an exception (aka trap) such as an interrupt, page fault etc. When the ex

Re: [osol-code] About global register usage in SPARC v9

Jim Glent wrote: Although your hints helped me much to understand what going on inside there, there does remain one obscure point... As far as I can see, when resume() or _resume_from_idle() is called, the stored (gnum | cnum) context for the process is loaded from curthread->t_procp->p_as->a_

Re: [osol-code] About global register usage in SPARC v9

Hi Jim Glent wrote: Thanks for your reply. It would seem that the pointer in %g7 is a waste from other piece of code - gold to me by the way. I was able to use cpu.cpu_thread and cpu.cpu_dispthread correctly however. I have one more question.. How and when does the primary and/or secondary M

Re: [osol-code] About global register usage in SPARC v9

Jim Glent wrote: Hi, I am facing difficulties with some kernel code on SPARC v9. Specifically, most of the times it seems > that the altername %g5 register contains a pointer to the current kthread_t struct in kernel memory. Following some exceptions, for example 0x8C (spill 3 normal), %g5 is

Re: [osol-code] Kernel memory management code

Hi Ian Collins wrote: I'm looking for pointers towards kernel memory debug code. I had a system that periodically ran out of physical memory and froze. It turns out the system had kmem_flags of 0xf and kmem_bufctl_audit_cache usage was getting to about 1.3GB. I'm interested is seeing how t

Re: [osol-code] ON build in OpenSolaris 2009.06

Hi Luis Useche wrote: Hi Guys, I want to modify OpenSolaris kernel for some project. I have been struggling really hard to compile the OpenSolaris kernel 2 days now with no success. I am doing this using the last release of OpenSolaris Indiana 2009.06. My steps: 1) clone the code with hg 2)

Re: [osol-code] Timer interrupt questions

Hi, Abhishek Bhattacharjee wrote: Hi Gavin Thanks for pointing out the TRAPTRACE mechanism. It so happens at the experiment that TJ and I want to run (we are working together) involves profiling the virtual and physical addresses prompting TLB misses through the execution of a given applicat

Re: [osol-code] Timer interrupt questions

Hi TJ wrote: Thanks for the responses. I think ddi_periodic_add is what I was looking for. I have been using trapstat, but I also need information on the virtual addresses on which the TLB is missing, so trapstat falls a bit short. In that case have a look at the TRAPTRACE code that is activ

Re: [osol-code] Question about Translation Table Hash

Hi, Abhishek Bhattacharjee wrote: Hi Gavin Thanks a ton for your detailed response! I was getting at exactly the issue of > whether it is possible to have a TLB miss while already servicing a user-level miss. > I'm actually a bit surprised that all the TSB and hash-table are maintained in >

Re: [osol-code] Question about Translation Table Hash

Hi, Abhishek Bhattacharjee wrote: Hi all- I had a question on how the backend hash maintaining the translation table entries > is allocated in Solaris. Is this data structure maintained in unmapped, cacheable memory? Or is the hash itself paged by the VM system? Any info on this would be h

Re: [osol-code] workaround proposal for bug 6745357

Hi, Guy wrote: Hello I worked lately on the bug 6745357 (kernel crash during startup at page_ctr_add_internal). I have observed the following : The bug was introduced from nv_88. The changeset that breaks the boot is this one : Issues Resolved: BUG/RFE:6594519Need support for ACPI System R

Re: [osol-code] b107 nightly build failed

Hi, A quick guess is that your build system is incomplete or missing some flag day. Is your build system a Nevada install or an OpenSolaris install? Was it able to build the 106 base? If Nevada: do you have package SUNWsmagt installed If OpenSolaris: what does pkg search SUNWsmagt say I'm guess

Re: [osol-code] Question about

Abhishek Bhattacharjee wrote: > Hi all -- > > I'm new to Solaris and am trying to understand how the kernel handles TLB > misses. > From reading the manuals, I gather that instruction and data TLB misses > cause an > interrupt to the OS. Thereafter, the miss handler uses the MMU Tag Register

Re: [osol-code] scheduler thread (t0) & Question about thread_unpin()

daidong wrote: > Thanks a lot for your help! > > I still do not quit understand the 'scheduler thread'. > >>> Throughout main the boot cpu will continue to >>> run t0 - we've stopped it looking for any other work in mlsetup. >>> Our final action in main is to call sched(): > > When t0 was stop

Re: [osol-code] scheduler thread (t0) & Question about thread_unpin()

Hi, daidong wrote: > I have several questions about the thread scheduling in OpenSolaris, and wish > you could help > me making everything clear: > > 1, in /ust/common/sys/Thread.h, there is a line of code > > "extern struct _kthread t0; /* the scheduler thread */" > >

Re: [osol-code] interleave in Sparc processors

Hi, PRDEEP KUMAR wrote: > Hi All, > > How can I find out the memory interleaving in case of Sparc processors > from Solaris. From the cmdline prtdiag normally prints the interleave factor (but prtdiag is very platform dependent in its output). Gavin __

Re: [osol-code] kernel panic no longer creates dumped core file

Joachim Worringen wrote: > But as I said, a real kernel panic says it dumps to /dev/dsk/c1t0d0s4 as > well, but savecore doesn't do anything on reboot. > > Any idea what's wrong? I tried different kinds of panics already... 'reboot -d' is a nice "controlled" panic which should always work. If

Re: [osol-code] [website-discuss] About OpenSolaris Repositories Browser

Darren J Moffat wrote: > I'm not going to log RFE's against OpenGrok because I don't want the > functionality implemented in OpenGrok - IMO it isn't actually missing > those features it is a different beast. > > What we want is plain and simply the http interface to a Mercurial repo. > As i

Re: [osol-code] eeprom: kernel panic

Jens Elkner wrote: > Hi, > > just found another way to reboot a > SunOS joker 5.10 Generic_137137-09 sun4u sparc SUNW,Sun-Fire-V240 ENOTOPENSOLARIS. > pfexec eeprom diag-level=normal > > panic[cpu1]/thread=30001645120: bad stack overflow at TL 2 > > %tl %tpc %tnpc %ts

Re: [osol-code] increase size of kernel message buffer

Hi, Joachim Worringen wrote: >> Way back, msgbuf was a buffer of fixed size like 8K. These days >> it it the console streams logging device - see the source in >> uts/common/os/printf.c and uts/common/os/logsubr.c. > > O.k., thanks, but is there a way to increase the backlog of messages in > a

Re: [osol-code] increase size of kernel message buffer

Hi, Joachim Worringen wrote: > Greetings, > > I think I read somewhere (but can no longer find) how the kernel message > buffer can be increased - would be helpful for ::msgbuf on a core dump. Way back, msgbuf was a buffer of fixed size like 8K. These days it it the console streams logging dev

Re: [osol-code] copyin/copyout under lock

Joachim Worringen wrote: > Garrett D'Amore wrote: >> I don't think the semaphore buys you anything. Additionally, it suffers >> from being subject to priority inversions, so I generally try to steer >> clear of semaphores unless I really do have a situation where the >> problem is expressed as

Re: [osol-code] What mutex type to use in clock thread?

Hi, Alexandra (Sasha) Fedorova wrote: > Eric, > > Thanks for the explanation. What I don't understand is this statement: > >> The clock thread >> can block (for example, in trying to grab a lock that's already held), >> but that's different from being preempted > > If the clock thread is block

Re: [osol-code] WARNING: failed to program mem space [0/31/3] [EMAIL PROTECTED] length 0x100

Patrick Ale wrote: > On Fri, Aug 1, 2008 at 1:34 AM, Dan Mick <[EMAIL PROTECTED]> wrote: >> >> Not surprising, since that's not the message you posted: >> >> Jul 31 16:15:55 nemesis pci_autoconfig: [ID 516285 kern.warning] >> WARNING: failed to program mem space [0/31/3] [EMAIL PROTECTED] length

Re: [osol-code] Performance bug in thread scheduler on AMD64?

On 04/16/08 11:37, Zeljko Vrba wrote: Prompted by my experiments with extreme number of threads, which show that the number of ITLB misses increases proportionally with the number of threads (even though all threads execute the same code), I dug into the kernel code. Full-text search for CR3 l

Re: [osol-code] memory segment base address and size

On 03/27/08 15:01, PRDEEP KUMAR wrote: Hi Experts, I need the info how to see the memory segments size and the base address of each segment(Bank) in solaris using the command/API. There are no formal APIs for this, but much of the information is available (in platform-dependent ways). What

Re: [osol-code] timeout

On 02/28/08 16:12, Garrett D'Amore wrote: I don't believe that new threads are created, but there are architecturally no guarantees that one invocation of a timeout function run on the same thread as another. And on an SMP system, it is entirely possible for two timeout functions to run at

Re: [osol-code] Solaris TRAP question

On 02/27/08 05:55, Hugh McIntyre wrote: Peter Damron wrote: I don't know many of the details of this topic, but I think I can answer some of the high-level issues. The MMU is mapping pages from virtual to physical addresses. The minimum page size on SPARC is 8 KBytes, so the lowest 13 bits of t

Re: [osol-code] Quick question about thread blocking

micke wrote: In OpenSolaris, when a real-time thread gets blocked it calls rt_yield(..) correct? or is there any other/more function that a thread "calls" when it gets blocked and put on a sleep queue? Follow something like cv_wait code to work this out: void cv_wait(kcondvar_t *cvp, kmute

Re: [osol-code] Bit confguration of solaris 10 OS ??

Hi, prakash bedge wrote: Hi all I just want to confirm the bit configuration of the solaris OS installed on my system. Here is result what I get when I type below command on soalris 10 OS. *Command: uname -a* *Output:* SunOS pc-p45502 5.10 Generic_118855-33 i86pc i386 i86pc

Re: [osol-code] kmdb not included?

Hi, Robin du wrote: Recently I build the kernel and use Install to make a kernel image, Install command told me: "kmdb isn't built, and won't be included" Who's wrong? Have a look at the Install script to decipher: In function copy_kmdb: # A kmdb-less workspace isn't fatal, but it

Re: [osol-code] shutdown functions

Mladen Nikitovic wrote: Hi, My question relates to the issue with shutting down a processor. It seems there are several functions that could be used when disabling a processor (or several states to choose from when migrating to another state). My understanding is that using cpu_offline functio

Re: [osol-code] power-aware idle thread

Hi, Mladen Nikitovic wrote: Hi, I've been informed that there is a "power-aware" version of the original idle-thread in OpenSolaris. My understanding is that this version should execute the halt-instruction, which in turn disables the clock-tree of the processor. In the original version, the

Re: [osol-code] What happens when a real-time thread wakes up?

Hi, On 11/14/07 12:18, micke wrote: Assumed: a real-time thread When a thread gets blocked, for example waiting for a condvar, this happens: 1. cv_block() is called, this places the thread on a sleepQ. 2. When the codvar is true the thread get off the sleepQ by a call to: cv_signal(), cv_bro

Re: [osol-code] page_get_{free,cache}list

Rafael Vanoni wrote: Hi everyone I'm using page_get_{free,cache}list() to get pages from specific lgroups, during boot - after lgrp_plat_probe() on main(). But I don't fully understand the implications of using those calls outside page_create_va(). I've read it, but it's not an easy one to

Re: [osol-code] My experience compiling onnv_74 with Sun Studio 12

On 10/01/07 09:07, Patrick Ale wrote: I don't have a ~/.make.machines file. When I look in the opensolaris.sh environmental file I see there is some calculation done, CPUs + 2 or something (which comes to 4 in my case). I think I fixed it though, outcome is I really needed more swap.. I BFU-e

Re: [osol-code] My experience compiling onnv_74 with Sun Studio 12

On 09/29/07 21:14, Patrick Ale wrote: On 9/29/07, Rafael Vanoni <[EMAIL PROTECTED]> wrote: Do you get that same result when you compile with Studio 11 ? Rafael, Either there is a gigantic memory leak somewhere in combination of the onnv_74 compiled operating environment and Sun Studio 11, or

Re: [osol-code] "main" scheduling function, real-time, FIFO and RR

On 09/27/07 17:15, [EMAIL PROTECTED] wrote: Each CPU has a disp_t which contains a pointer to the first and last dispq_t for that cpu. There is one dispq_t allocated for each possible priority (see disp_cpu_init() in common/disp/disp.c) Real time threads will use priorities between 100 and 15

Re: [osol-code] OpenSolaris Kernel & SPARC Register Windows OTHERWIN

On 09/26/07 18:01, Haris wrote: Let me clarify something about nucleus context and traps that are short and don't need C code. > Such traps are limited on what they use. They just use the alternate globals in SPARC and cannot > use register windows (otherwise implies C code/stack). Therefore t

Re: [osol-code] OpenSolaris Kernel & SPARC Register Windows OTHERWIN

On 09/21/07 18:18, Haris wrote: Hey - In OpenSolaris on SPARC when we are running a process the register windows' register OTHERWIN marks > the register windows used by the kernel. The opposite happens when we are in kernel, i.e OTHERWIN > marks the register windows used by the process. Yes,

Re: [osol-code] nop instruction generated by sun cc

On 09/11/07 16:40, ?? TaoJie wrote: Dear all: there's no sun studio mailling list in opensolaris.org , i raise my problem here :) a simple piece of code, 2 nested while loops, and some if statements inside each while loop. i compiled this program in Solaris with s

Re: [osol-code] A puzzle about the NULL Dereference

Hi, On 08/22/07 09:58, liujun wrote: ! 2641! "mppLnx_remove_proxyRequest_from_list() MPPLNX_QUEUE_QUEUED_LIS ! 2641>T LockAddress:%p\n", &mppLnx_queuedProxyRequestQ.queueLock)); ! 2642!OSP_LockKmutexSaveIrq ( &mppLn

Re: [osol-code] length alignment for device driver devmap()

Hi, On 08/09/07 22:46, Joachim Worringen wrote: [cut] Why does map_len have to be page-aligned? devmap(9E) doesn't mention this (says it has to be <= the mmap() len), and the example there does no alignment, too. Also, I tried and returned ptob(btopr((len)), but it did not fix the problem (and

Re: [osol-code] how to access Global structure?

On 08/03/07 07:49, Aubrey Li wrote: On 8/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Once you have the address (from the driver cmn_err() call), you could just open /dev/kmem, lseek to the address, and print the contents of the structure, something like: fd = open("/dev/kmem", O_RD

Re: [osol-code] how to access Global structure?

On 08/02/07 14:18, Aubrey Li wrote: Hi all, I can access a Global structure by mdb-> Global_struct=X, it prints the address of that structure. Now I want to access it from user space, so I wrote a driver and put it in the read op. cmn_err(CE_NOTE, "Global structure = 0x%x\n", (unsigned int)&Glo

Re: [osol-code] kernel makefiles

On 06/26/07 00:42, Danek Duvall wrote: I thought Sasha would jump in at some point, but http://opensolaris.org/os/project/onnv/onnv_build/faster_builds/ I notice that in the build results there, eg, http://opensolaris.org/os/project/onnv/onnv_build/faster_builds/times/x86/ the DMAKE_MAX

Re: [osol-code] Questions about softints and x-calls

On 06/22/07 16:21, Neale Ferguson wrote: 1. For cross-system calls System z uses the SIGP instruction which allows you to send signal to another CPU and pass it a 32-bit parameter (which makes the Sparc way of passing a function pointer and up to two arg pointers not possible). I'm interested

Re: [osol-code] What is the solaris kernel entry point?

On 06/20/07 10:05, borun_fu wrote: I'm learning solaris kernel bootup code. My source code version is b63. I think it is _locore_start, but I can't make sure. Are there any martials or docs about solaris kernel startup process? I wan to know how the kernel get the cpu info during the startup.

Re: [osol-code] thread creation/switching/termination functions

Hi On 05/21/07 19:05, Thomas De Schampheleire wrote: [cut] In parts of our log which 'seems' normal, we see: 1. a bunch of lwp_create (equal to the number of threads used) 2. a lot of calls to dispdeq() (which seems to be the actual execution) 3. lwp_exits for each thread (one less than the act

Re: [osol-code] KSTAT_FLAG_PERSISTENT considered harmful

On 05/08/07 16:38, Garrett D'Amore wrote: [snip] This sounds like an "edge" case to me. I.e. using kstats to attempt to locate a kernel bug. (Kstats are unlikely to explain the "why" for a failure-to-detach, or at least, they are for a driver that is detaching, since the kstats of interest

Re: [osol-code] KSTAT_FLAG_PERSISTENT considered harmful

On 05/08/07 16:11, Garrett D'Amore wrote: Gavin Maltby wrote: On 05/03/07 20:04, Garrett D'Amore wrote: If the device isn't in use, then probably the historical data simply is not interesting. They could be useful in post-mortem debugging where they represent a small handle

Re: [osol-code] Re: usable kernel symbols [was Re: Executing a kernel thread periodically]

On 05/08/07 10:38, Thomas De Schampheleire wrote: But see cmi_load_module(), where we load up per-vendor CPU modules, and the existing files under /platform/i86pc/kernel/cpu/. I should mention that I am using UltraSPARC, and there doesn't seem to be such cmi_* functions there. Are there oth

Re: [osol-code] KSTAT_FLAG_PERSISTENT considered harmful

On 05/03/07 20:04, Garrett D'Amore wrote: If the device isn't in use, then probably the historical data simply is not interesting. They could be useful in post-mortem debugging where they represent a small handle on past history relative to the snapshot-in-time which the system crash dump repr

Re: [osol-code] sfmmu spinning

Hi On 05/07/07 21:48, Peter Tribble wrote: [cut] So there is a small chance that back in sfmmu_shadow_hcleanup we could still see the hblk_cnt and hblk_hmecnt non-zero, which is the comment you have highlighted. In that case we do not remove the block from the hash chain, and proceed on to the

Re: [osol-code] sfmmu spinning

Hi Peter, On 05/02/07 13:37, Peter Tribble wrote: There's this interesting comment about line 3235 of hat_sfmmu.c /* * Hblk_hmecnt and hblk_vcnt could be non zero * since hblk_unload() does not gurantee that. * * XXX - this could c

Re: [osol-discuss] Re: [osol-code] where are atomic_read(), atomic_set() APIs?

Hi, On 05/01/07 11:52, Gavin Maltby wrote ... ... total nonsense! For example, Studio 11 with -xarch=sparcv8plus can generate two separate 32-bit ld instructions to load a single 64-bit value. An atomic_load_64(3C) function would be useful to ensure that a single ldx instruction is used

Re: [osol-discuss] Re: [osol-code] where are atomic_read(), atomic_set() APIs?

On 04/30/07 22:01, Chris Elving wrote: [EMAIL PROTECTED] wrote: If those APIs do what their names suggests, what is the point in having them? "Atomic set" can hardly be anything other than a normal store nor can "Atomic read" be much different from an ordinary read. I'd find them useful.

Re: [osol-code] Re: [ksh93-integration-discuss] Building ksh93 prototype005 - error

On 04/26/07 10:25, Darren J Moffat wrote: Danek Duvall wrote: On Wed, Apr 25, 2007 at 08:33:36AM +0200, Roland Mainz wrote: (you're using dmake which means that an error long before this point may cause this build failure (and dmake just unrolls all the output of the pending jobs)) ? Usefu

Re: [osol-code] SPARC instruction formats

Hi, On 03/23/07 14:07, [EMAIL PROTECTED] wrote: |op | fcn | op3 |--- | 31 30 29 25 24 19 180 |op | rd | op3 |--- |

Re: [osol-code] SPARC instruction formats

Hi, On 03/23/07 02:00, [EMAIL PROTECTED] wrote: Hi, in the UltraSPARC III user's manual, section 7.11 on page 175 describes instruction formats. On page 176 the last two instructions are exactly the same, i.e. |op| fcn | op3 |---|

Re: [osol-code] Re: Does the dmake do incremental building?

On 02/19/07 18:01, Thomas De Schampheleire wrote: On http://opensolaris.org/os/community/on/devref_toc/devref_4/ I read that it is possible to compile only parts of the kernel using make/dmake directly. This would speed up compilation in test phases. However, when I modify a file, for exampl

Re: [osol-code] Call path at a Context Switch event

Hi, On 02/12/07 18:41, Haris wrote: Hi - Relating to my previous post about g7, It would be nice if someone could give me an idea of the call path followed at a context switch. Suppose we are a user thread and our quantum expires; which functions will be invoked? (timer interrupt, get into k

Re: [osol-code] Context switch and %g7 register

On 02/10/07 09:11, [EMAIL PROTECTED] wrote: The %g7 register is setup by the trap code. On sun4u, user_trap() determines the CPU->cpu_thread, stashes it in %l6 and calls utl0(). The code in utl0() moves %l6 to THREAD_REG which is defined as %g7. In the syscall case, the utl0() code then invoke

Re: [osol-code] Re: Re: Re: slow fopen

On 01/16/07 10:06, Frank Hofmann wrote: With your original "ftime" code, the clock resolution could falsify your results. With "gethrtime", zero time taken means a bug on the OS where that is reported. Two consecutive gethrtime() calls, even with nothing in-between, may not report the same val

Re: [osol-code] disable processor(s)

Mladen Nikitovic wrote: Hi, I would like to disable one or several processors dynamically in a SMP system running openSolaris 10. My experience so far (using a full system simulator) is that disabling the processor (from the simulator-side) causes "kernel panic" in the OS - probably because it i

Re: [osol-code] Re: freemem

Hi, On 11/16/06 17:42, Neale Ferguson wrote: Actually, this question is redundant and arises because of a lack of understanding of the way memlists work. I wonder if someone could step me through the way things work here... I'm trying to get my mind around the use of memlists in the startup c

Re: [osol-code] how to only build lib/usr dirs in onnv source tree ?

Hi On 11/16/06 08:22, Xiao-Hai Ivan Shi wrote: Hi all, I don't want to build all onnv source, which need too long time. If I only want to build the following dirs, how to make it? It will take you longer to work out how to build a limited subset, and the procedure may changes as new code is in

Re: [osol-code] Queries regarding crash dump .....

Hi, On 10/29/06 08:54, Gaurav Dhiman wrote: Hi, I am studing the crash dump routines of opensoalris now days, mainly the flow of panic() funcion. Can someone let me know the answers of following questions. - What all can be configured as dump device ? - Swap partition on local disk is ok,

Re: [osol-code] reg. booting sequence on source code level

Hi On 10/23/06 14:16, Ashok Kumar wrote: Hi, can you tell me the name of the file, which are involved in booting from "grub" to "startup.c"(now this is well know file for me, that is why i am preferring this)? We can start you in the right place and you can use cvs.opensolaris.org to see who

Re: [osol-code] reg. booting sequence on source code level

Hi On 10/23/06 09:20, Ashok Kumar wrote: On 10/16/06, Victor Latushkin <[EMAIL PROTECTED]> wrote: Hi Ashok, Ashok Kumar wrote: > Hi all, > > i am newbie to open solaris. i have installed soalris 10 on my computer. > i want to understand solaris booting sequence on source level, so i > enabl

Re: [osol-code] Re: Questions about OpenSol page allocation?

On 09/28/06 18:21, Bart Smaalders wrote: One easy way to experiment with alternate page coloring algorithms is to use meminfo to get the physical adress of pages in an mmaped file from userland, and then remap the pages to get the coloring you want to run your algorithm against Do you ne

Re: [osol-code] Inline assembly in dispatcher code

On 08/12/06 11:46, Marcus Spangenberg wrote: I doing some modifications to the dispatcher code in usr/src/uts/common/disp.c and need to add some inline assembly (sparc), though doing so causes the compilation to fail with an error message saying that using assembly inline makes optimizations

Re: [osol-code] building on non-native solaris releases....

Garrett D'Amore wrote: Has anyone given any thought to convincing OpenSolaris to use its own proto area (populated by the install_h target or somesuch) instead of assuming local system headers? What about libraries? Startup code? Tools? I have s story of a brute-force approach to a related

Re: [osol-code] building on non-native solaris releases....

Joerg Schilling wrote: This would make OpenSolaris more stable even in the non-cross compilation case. Note that OpenSolaris does use /usr/include from the host system instead of using the include files that are specific to the current build Where that happens for ON it is a bug either in ma

Re: [osol-code] vmstat -i nearly totally useless

Garrett D'Amore wrote: I'm trying to do some debugging related to interrupts, and I thought I would try getting the interrupt counts (I'm especially interested in knowing what Schizo thinks.) So I thought I would try vmstat -i. I know this doesn't help with vmstat -i but you may find /usr/sbin

Re: [osol-code] root privilege required for /dev/openprom?

On 08/04/06 18:00, Garrett D'Amore wrote: I propose that /dev/openprom be changed to be mode 644, allowing any user to access it. This would allow ordinary users to run prtconf -vp (as well as a few other things like prtconf -F and prtconf -V) without becoming root. Last I knew there was a di

Re: [osol-code] How is priority inversion managed in Solaris kernel?

On 07/19/06 09:10, xxx wrote: Hello everybody, let's consider such a situation: you have a priority 10 thread that's running, preventing a priority 6 thread from receiving CPU time; however, a priority 3 thread is waiting for some resource that the priority 6 thread has locked. Since priority 10

Re: [osol-code] A question about KMEM_CPU_CACHE

Hi On 07/11/06 07:19, Oliver Yang wrote: I have a question about last member of kmem_cache structure. Why the elements number of cache_cpu is 1 as below definition, but on SMP system, it's actual elements number is equal to the cpu numbers? 233 struct kmem_cache { .

Re: [osol-code] usr/src/uts/sun4u/ml files

mbler. Unless you really want to understand the guts of sun4u I'd stay away from those! You'll find a few similar bits in places like uts/sun4u/cpu/*.s and uts/sfmmu/ml - all low-level support code. Gavin -- Gavin Maltby, Solaris Ker

Re: [osol-code] context switch tracking

Hi On 04/11/06 10:13, Mladen Nikitovic wrote: Hi, I'm doing an experiment using a full-system simulator running a simulated sparc machine with solaris 10. I would like to detect context switches and print out processs-specific information such as the pid, the command name, etc. If it's just

Re: [osol-code] Scheduling/Descheduling of kernel threads & Scheduler Activations

Hi On 04/02/06 04:50, Haris wrote: Hey, what I want to do is to signal a thread after is scheduled and before is descheduled. Do you know in which function the scheduling/descheduling of kernel threads takes place? Is there any other way to notify a thread that is scheduled/descheduled? I am

Re: [osol-code] A question about x86's user preemption code

Hi On 03/27/06 07:45, Oliver Yang wrote: Gavin Maltby wrote: The call to preempt from sparc interrupt.s is to avoid interrupts running endlessly on a cpu while pinning an interrupted thread (which could run on another cpu if only we'd unpin it). In sparc new interrupts can be queued a

Re: [osol-code] Debugging

On 03/23/06 20:52, Matty wrote: If Sun puts together an opensolaris conference (which I hope they do), debugging crash dumps would be an awesome topic to cover. Also, Kimberly Brown put a poll up on her website to see if people would like an updated version of Panic! I am not sure if she decid

Re: [osol-code] Several problems with SUNWonbld

Hi, On 03/22/06 22:01, Rainer Orth wrote: I've recently started doing builds of OpenSolaris again, and noticed a whole bunch of problems with SUNWonbld in the process. Stephen Lau suggested I post a summary here before filing bug reports at bugs.opensolaris.org, so here we go: Couldn't agree

Re: [osol-code] A question about x86's user preemption code

Hi, The call to preempt from sparc interrupt.s is to avoid interrupts running endlessly on a cpu while pinning an interrupted thread (which could run on another cpu if only we'd unpin it). In sparc new interrupts can be queued at the pil we're servicing even while we are serviving preexisting re

Re: [osol-code] Re: [osol-discuss] Building an (almost completely) non-debug OpenSolaris

On 12/20/05 20:31, Bill Rushmore wrote: Compiling non-debug gets rid of this overhead. Wow, I have been running OpenSolaris for a few months now thinking how fast it felt compared to that popular Unix like open source OS I replaced it with. Viva OpenSolaris! libmicro (which you can find i

Re: [osol-code] How to flush syslog buffer?

Solange wrote On 12/06/05 18:08,: > I am doing kernel development, and I would like to print lots of messages to > the console. I use vstrlog(), which eventually calls cprintf(). > > This is problematic, because syslog message queue becomes overflown, and some > of my messages get lost. Does any

Re: [osol-code] Simple q (cud be naive)

On 08/30/05 14:53, Adil Rajput wrote: For thoise questioning my sanity, I am about to teach an undergrad course in OS and would like to give my students assignments based on the code. Since it is an undergrad class, I want them to be able to do simple things without getting into make issues. A

Re: [osol-code] kernel stacks pageable?

On 08/11/05 00:21, Robert W. Fuller wrote: I'm not sure if this is the right venue for this question. Does anybody know off-hand if kernel stacks are pageable? I don't think kernel stacks (for kernel threads or those supporting lwps) are pageable. They are allocated from segkp (seg kernel p

Re: [osol-code] Re: /proc filesystem enhancements

On 07/13/05 01:49, Shawn Walker wrote: On 7/12/05, Random <[EMAIL PROTECTED]> wrote: Eliminating tuneables is a *silly* thing to do, even if the process of tuning is 'automatic'. As OS kernels and the systems they control become *far* more complex, giving the system access to dynamic tuning

Re: [osol-code] /proc filesystem enhancements

On 07/12/05 13:10, Joerg Schilling wrote: It is wrong to put these parameters into /proc anyway because they don't beling there even in a read-only way. - Solaris supports tuneables in /etc/system since ~ 1992. True, but /etc/system is not an "interface" that we're proud of. I'm not su

Re: [osol-code] Some shabby code

Random wrote: Some of the Solaris code really leaves a lot to be desired. I had a brief look over some of the code and wondered how the other team members didn't slap some of the developers in the back of the head due to the extreme hackiness of some code. I strongly recommend weekly Friday