09-06-2011
Looks like I am running in 64-bit then. Thanks. Does Solaris just auto-detect the hardware, and run in 32-bit or 64-bit depending on the hardware available?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear everyone:
Could you tell me where is the 64 bit's solaris v9.0. :p (2 Replies)
Discussion started by: arwang
2 Replies
2. HP-UX
Hi, I'm using HPUX 11.11 on Vizualize B180L
our productive machines have 64 bit kernel
# file vmunix
vmunix: ELF-64 executable object file - PA-RISC 2.0 (LP64)
I got one test system, which should have the same HW (i was told it is the same HW)
hpuxtest:/stand-->file... (3 Replies)
Discussion started by: funksen
3 Replies
3. Red Hat
Hi all,
I'm looking to cover a corner case for an upcoming test cycle. Is there a way to boot a RedHat Advanced Server 4 (update 3) installed on a Power PC machine to use a 32 bit kernel? This would be similar to what is done here -> https://www.unix.com/aix/26204-aix-platform.html
I've done... (0 Replies)
Discussion started by: philrau
0 Replies
4. Solaris
Hi,
I am looking for eclipse for my solaris 10 x86 64 bit. No luck and haven't found the download yet. It is required when I install WLS 10.3. Of course
one no need to use eclipse and you can always use workshop.
Does anybody please know where can I download the software.
Thanks,
... (2 Replies)
Discussion started by: aa_monster
2 Replies
5. Solaris
Hello all. I am going to build an x86 Solaris box. Sun only offers it in a 64 bit flavor.
I want to put MySQL on this box. MySQL only comes in a 32 bit version for x86 Solaris.
Can I run 32 bit apps on a 64 bit x86 Solaris machine?
Thanks! (4 Replies)
Discussion started by: RobertSubnet
4 Replies
6. Shell Programming and Scripting
In order to perform some arithmetical operations on 64 bit double I need to transform of the binary representation of a 64 bit double to a 64
bit integer do the operations and then transform back to 64 bit double.
I understand bash and bc doesn't allow to do that. I think my only tool left is... (2 Replies)
Discussion started by: Zephyr
2 Replies
7. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
Hi all,
I've got a huuuuuuge problem with understanding this new concept of multi-paging. I really tried to research but i could not find anything significant. I've been trying to understand this for 4 days and i cannot. The question... (0 Replies)
Discussion started by: snowboarder
0 Replies
8. UNIX for Dummies Questions & Answers
Hello everyone. This is an awesome forum. Glad to have joined! :)
I use Linux mostly, even for Desktop usage. I just love everything about it, all the way down to how the font looks while browsing. Its just so sleek and sexy.
But I also boot Windows for those programs I just need that only... (23 Replies)
Discussion started by: insomnia
23 Replies
9. Solaris
I have java installed on my solaris 10 as /usr/jdk/jdk1.5.0 , but i need to install Weblogic for that i need --
JDK Sun Java 2 JDK 6.0 Update 05 with the Java HotSpot™ Client and Server
VMs (32-bit) and all later service packs of 6.0
How can i upgrade my java for this. (3 Replies)
Discussion started by: jain_sharad143
3 Replies
LEARN ABOUT OPENSOLARIS
id32_alloc
id32_alloc(9F) Kernel Functions for Drivers id32_alloc(9F)
NAME
id32_alloc, id32_free, id32_lookup - 32-bit driver ID management routines
SYNOPSIS
#include <sys/ddi.h>
#include <sys/id32.h>
uint32_t id32_alloc(void *ptr, int flag);
void id32_free(uint32_t token);
void *id32_lookup(uint32_t token);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
PARAMETERS
ptr any valid 32- or 64-bit pointer
flag determines whether caller can sleep for memory (see kmem_alloc(9F) for a description)
DESCRIPTION
These routines were originally developed so that device drivers could manage 64-bit pointers on devices that save space only for 32-bit
pointers.
Many device drivers need to pass a 32-bit value to the hardware when attempting I/O. Later, when that I/O completes, the only way the
driver has to identify the request that generated that I/O is via a "token". When the I/O is initiated, the driver passes this token to the
hardware. When the I/O completes the hardware passes back this 32-bit token.
Before Solaris supported 64-bit pointers, device drivers just passed a raw 32-bit pointer to the hardware. When pointers grew to be 64 bits
this was no longer possible. The id32_*() routines were created to help drivers translate between 64-bit pointers and a 32-bit token.
Given a 32- or 64-bit pointer, the routine id32_alloc() allocates a 32-bit token, returning 0 if KM_NOSLEEP was specified and memory could
not be allocated. The allocated token is passed back to id32_lookup() to obtain the original 32- or 64-bit pointer.
The routine id32_free() is used to free an allocated token. Once id32_free() is called, the supplied token is no longer valid.
Note that these routines have some degree of error checking. This is done so that an invalid token passed to id32_lookup() will not be
accepted as valid. When id32_lookup() detects an invalid token it returns NULL. Calling routines should check for this return value so that
they do not try to dereference a NULL pointer.
CONTEXT
These functions can be called from user or interrupt context. The routine id32_alloc() should not be called from interrupt context when the
KM_SLEEP flag is passed in. All other routines can be called from interrupt or kernel context.
SEE ALSO
kmem_alloc(9F)
Writing Device Drivers
SunOS 5.11 12 Dec 2001 id32_alloc(9F)