hotsolaris的专栏

PCI device identification and driver binding in Solaris

Allen Lu — Thu, 09 Jul 2009 13:28:00 GMT

This is a blog article written by Dan Mick, http://blogs.sun.com/dmick/entry/title_pci_device_identification_and

A PCI device has a bunch of device identification numbers associated with it, which generic code can retrieve. I've listed them here in most-specific to least-specific order, by their Solaris property name (shown in the prtconf -pv output, which is why we always always always ask for that when diagnosing driver-binding problems): revision (not useful on its ow

Locking and Synchronization in Solaris kernel

Allen Lu — Thu, 02 Jul 2009 13:31:00 GMT

1. Parallel System Architecture
        SMP - Symmetric multiprocessor with a shared memory model; single kernel image
        MPP - Message-based model; multiple kernel images
        NUMA/ccNUMA - Shared memory model; single kernel images

2. Hardware Considerations for Locks and Syncronization
        Consideration:
        (1) need For an automatic test-and-set instruction for locking primitives
        (2) Data global visibility is

How to dump, extract and iasl acpi tables on x86 platform

Allen Lu — Fri, 26 Jun 2009 16:47:00 GMT

You need the following packages to install on your Nevada:

acpidump - acpi power management utilities
iasl - Intel ASL compiler/decompiler

If you are using OpenSolaris200906, IPS can help you to install these tools.

The binary files are installed under

[allen@blu-nhm:~]which acpidump
/opt/csw/bin/acpidump

# acpidump > acpi.bin

# acpixtract -a acpi.bin
Acpi table [DSDT] - 26643 bytes written to DSDT

disable graphic login

Allen Lu — Wed, 24 Jun 2009 14:40:00 GMT

Run the following two commands and reboot.

svcadm disable cde-login
svcadm disable gdm

panic or panick?

Allen Lu — Fri, 19 Jun 2009 18:37:00 GMT

If English is not your native language, you may misused panic and panick in code comment. Keep this in mind, panic is a noun and panick is it's correspoding verb.

how to convert a virutal address to physical address in Solaris driver

Allen Lu — Fri, 19 Jun 2009 18:33:00 GMT

Below discussion posted in osol-code mailing list tells how to use ddi interface to convert virtual address to physical address in Solaris driver.

====

If you are writing a device driver, or porting one, then you're going about this entirely the wrong way. These APIs should only be used by low level platform code, not from within device drivers. In fact, hat_getkpfnum generates warnings if you use it!

Assuming that this is an ordinary device driver, and n

videos and foils for Community One event

Allen Lu — Thu, 18 Jun 2009 16:00:00 GMT

http://wikis.sun.com/display/OpenSolaris/OpenSolaris+at+C1+West+-+Schedule

Have fun.

A brief introduction to XenStore: Format and Interface

Allen Lu — Thu, 18 Jun 2009 10:25:00 GMT

About

This document describes the format of the entries in XenStore, how and what they're used for, and how third-party apps should use XenStore as a management interface.
Overview

XenStore is a hierarchical namespace (similar to sysfs or Open Firmware) which is shared between domains. The interdomain communication primitives exposed by Xen are very low-level (virtual IRQ and shared memory). XenStore is implemented on top of these primitives and provides some h

A brief introduction to XenBus from the perspective of the driver

Allen Lu — Thu, 18 Jun 2009 10:09:00 GMT

Writing Xen Drivers: Using XenBus and XenStore

XenBus provides a bus abstraction for paravirtualized drivers to communicate between domains. In practice, the bus is used for configuration negotiation, leaving most data transfer to be done via an interdomain channel composed of a shared page and an event channel.

Xenstore is a centralized configuration database that is accessible by all domains. Management tools configure and control virtual devices by writing val

Utilize OpenSolaris beadm to test unstable bits

Allen Lu — Wed, 17 Jun 2009 17:05:00 GMT

If you need to test an dev kernel binarie. Try the following best practice.

One thing you can do is to use beadm(1M) to create one or more alternate boot environments (BE). This way you can keep 2009.06 but also experiment with the newer
bits in the dev tree.

There are various ways to do this... This is what I usually do to ensure that the stock bits remained absolutely unchanged. What we'll do it to create a tree of cloned disk images..

Creat

Physical device interrupt handling in XEN

Allen Lu — Wed, 17 Jun 2009 14:38:00 GMT

In Xen, only the Hypervisor has an access to the hardware so that to achieve isolation (it is dangerous to share the hardware and let other domains access directly hardware devices simultaneously).
Let's take a little walkthrough dealing with Xen interrupts:
Handling interrupts in Xen is done by using event channels. Each domain can hold up to 1024 events. An event channel can have 2 flags associated with it : pending and mask. The mask flag can be updated only by guests.

how to prevent ZFS from eating too much memory

Allen Lu — Tue, 16 Jun 2009 15:28:00 GMT

See this guide:http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Limiting_the_ARC_Cache This syntax is provided starting in the Solaris 10 8/07 release and Nevada (build 51) release.
For example, if an application needs 5 GBytes of memory on a system with 36-GBytes of memory, you could set the arc maximum to 30 GBytes, (0x780000000 or 32212254720 bytes). Set the zfs:zfs_arc_max parameter in the /etc/system file:
set zfs:zfs_arc_max = 0x780000000

Best Practice to Set OpenSolaris 200906 as xvm domain 0

Allen Lu — Tue, 16 Jun 2009 15:15:00 GMT

See this blog:

http://blogs.sun.com/levon/entry/opensolaris_2008_11_as_a1

But you should add a limit to dom0_mem on the kernel line in the
grub menu.lst entry... e.g.

title xvm
findroot (pool_rpool,0,a)
bootfs rpool/ROOT/xvm
kernel$ /boot/$ISADIR/xen.gz dom0_mem=2g
module$ /platform/i86xpv/kernel/$ISADIR/unix /platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=text
module$ /platform/i86pc/$ISADIR/boot_archive

How domain 0 works on xen hypervisor

Allen Lu — Tue, 16 Jun 2009 14:49:00 GMT

A tour of the Mini-OS kernel Satya Popuri
Graduate Student
University of Illinois at Chicago
Chicago, IL 60607
spopur2 [at] uic [dot] edu
Introduction Mini-OS is a small OS kernel distributed with the Xen hypervisor sources. I have documented some of the basic parts of this kernel for the reference of people trying to port their OSes to Xen (also for people writing new OSes for Xen). This work is not completed yet. The present document includes a discussion of in

Xen Memory Management

Allen Lu — Fri, 12 Jun 2009 15:28:00 GMT

Below was cited from https://wiki.cs.dartmouth.edu/nihal/doku.php/xen:memory. Changes subject to this site.

All low-level memory operations go through Xen.Guest OSes are responsible for allocating and initializing PTs for processes (restricted to read only access)allocates and initialize a page and register it with Xen to serve as the new PTDirect page writes are intercepted, validated and applied by the Xen VMMupdate can be batched into a single hypercall (reduce cost of enter