OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Build 101-105
      3. Builds 96-100
      4. Builds 91-95
      5. Builds 86-90
      6. Builds 81-85
      7. Builds 76-80
      8. Builds 71-75
      9. Builds 66-70
      10. Builds 61-65
      11. Builds 56-60
      12. Builds 51-55
      13. Builds 46-50
      14. Builds 41-45
      15. Builds 36-40
      16. Builds 31-35
      17. Builds 26-30
      18. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Belated build Flag-day: xVM DTrace Provider

Date: Tue, 20 May 2008 16:36:14 -0700
From: Tariq Magdon-Ismail <tariqmi at sun dot com>
To: Undisclosed recipients: ;
Subject: Belated build Flag-day: xVM DTrace Provider

If you use xVM, read on.

The putback of:

6685348 Hypervisor event provider for DTrace
6699048 XEN_SYSCTL_tbuf_op sysctl-hypercall data misaligned in 32-bit  
Solaris

into onnv-gate and:

6691660 Race condition between trace() and tb_control() in trace.c
6699048 XEN_SYSCTL_tbuf_op sysctl-hypercall data misaligned in 32-bit  
Solaris

into xvm-gate represents a flag day for those who want to use the new  
xVM DTrace provider.

For safe operation of the provider, when you update to ON bits that  
include the fix for 6685348 you must also update your xVM packages to  
include the fix for 6691660. Further, the fix for 6699048 needs to be  
in both places for use in a 32-bit dom0.


Regards,
-Tariq

-- 
Tariq Magdon-Ismail                           tariqmi at sun dot com
Performance & Applications Engineering (PAE)  ph: x68266/+1 650 3526323
Sun Microsystems, Inc.                        im: tariqmi@aim