Austin Group Minutes of the 17 March Teleconference Austin-251 Page 1 of 1
Submitted by Andrew Josey, The Open Group. March 18, 2005
Attendees
Andrew Josey, The Open Group
Nick Stoughton, USENIX, ISO/IEC OR
Loic Domaigne
Geoff Clare , The Open Group
Ulrich Drepper, Red Hat
Don Cragun , Sun, PASC OR
Mats Wichmann
Apologies
Mark Brown, IBM, TOG OR
Action item review
---------------------
Just the updates on Austin/240r1 are noted here.
ACTION AI-2005-01-09 Andrew Josey & Mats Wichmann to propose a time and place
for a joint Austin group/LSB Workgroup meeting to consider LSB/POSIX
conflicts, to be held as soon as conveniently possible.
Status: OPEN
Andrew has started to update the report and is about a third
of the way through. He reported that the LSB has now added
a section on deference to underlying standards such as POSIX.
Nick noted that the LSB specification is undergoing a lot
of changes this week, but is expected to stabilize early
next week. Andrew will hold off completing the update until
then.
Nick still has an action to prepare an agenda for a teleconference.
ACTION AI-2005-01-06: AJ to contact Jack McCann at HP for views on
getnameinfo document, and for any other networking issues that may
concern us.
Status: OPEN, Don is asking around for a contact.
ACTION AI-2005-01-11 Feedback on the Secure C Library TR
CLOSED. See Austin/250.
Defect Report Processing
-------------------------
The group picked up on the latest batch of defect reports,
which are available at the following URL:
http://www.opengroup.org/austin/aardvark/latest/
XSH ERN 52 BUG in sched_setscheduler Accept as marked below
The working group accepted the latest proposal generated
by Loic/Dave with minor changes.
This is included here:
-----------------------------------------------------------------------
Changes XSH sched_setparam()
-----------------------------------------------------------------------
@lines 39363-39382: unchanged
@lines 39383-39425: replace these lines by the following text:
See [Scheduling Policies] for a description on how this
fuction call affects the scheduling of the threads within the target
process.
If the current scheduling policy for the target process is not
SCHED_FIFO, SCHED_RR, [SS] [Option Start] or SCHED_SPORADIC, [Option End]
the result is implementation-defined; this case includes the SCHED_OTHER
policy.
[SS] [Option Start]
The specified sched_ss_repl_period shall be greater than or equal to the
specified sched_ss_init_budget for the function to succeed; if it is
not, then the function shall fail.
The value of sched_ss_max_repl shall be within the inclusive range
[1, {SS_REPL_MAX}] for the function to succeed; if not, the function
shall fail. [Option End]
@lines 39426-39464: unchanged
-----------------------------------------------------------------------
changes XSH sched_setscheduler()
-----------------------------------------------------------------------
@lines 39465-39492: unchanged
@lines 39493-39522: replace these lines by the following text
See [Scheduling Policies] for a description on how this
fuction call affects the scheduling of the threads within the target
process.
If the current scheduling policy for the target process is not
SCHED_FIFO, SCHED_RR, [SS] [Option Start] or SCHED_SPORADIC, [Option End]
the result is implementation-defined; this case includes the SCHED_OTHER
policy.
[SS] [Option Start]
The specified sched_ss_repl_period shall be greater than or equal to
the specified sched_ss_init_budget for the function to succeed;
if it is not, then the function shall fail.
The value of sched_ss_max_repl shall be within the inclusive range
[1,{SS_REPL_MAX}] for the function to succeed; if not, the function
shall fail. [Option End]
@lines 39523-39562: unchanged
-----------------------------------------------------------------------
change ยง2.8.4 "Process Scheduling"
-----------------------------------------------------------------------
@lines 1830-1845: unchanged
@lines 1846-1851: replace these lines by the following text
The POSIX model treats a "process" as an aggregation of system
resources, including one or more threads that may be scheduled by the
operating system on the processor(s) it controls. Although a process has
its own set of scheduling attributes, these have an indirect effect (if
any) on the scheduling behavior of individual threads as described below.
Each thread shall be controlled by an associated scheduling policy
and priority. These parameters may be specified by explicit application
execution of the pthread_setschedparam() function. Additionally, the
scheduling parameters of a thread (but not its scheduling policy) may be
changed by application execution of the pthread_setschedprio() function.
Each process shall be controlled by an associated scheduling policy and
priority. These parameters may be specified by explicit application
execution of the sched_setscheduler() or sched_setparam() functions.
The effect of the process scheduling attributes on individual threads
in the process is dependent on the scheduling contention scope of the
threads, see [Thread Scheduling]:
(*) For threads with system scheduling contention scope, the process
scheduling attributes shall have no effect on the scheduling attributes
or behavior either of the thread or an underlying kernel
scheduling entity dedicated to that thread.
(*) For threads with process scheduling contention scope, the process
scheduling attributes shall have no effect on the scheduling attributes
of the thread. However, any underlying kernel scheduling
entity used by these threads shall at all times behave as specified by
the scheduling attributes of the containing process, and this behavior
may affect the scheduling behavior of the process contention
scope threads. For example, a process contention scope thread with
scheduling policy SCHED_FIFO and the system maximum priority H (the
value returned by sched_get_priority_max(SCHED_FIFO)) in a process with
scheduling policy SCHED_RR and system minimum priority L (the value
returned by sched_get_priority_min(SCHED_RR)) shall be subject to
timeslicing and to preemption by any thread with an effective priority
higher than L.
@lines 1852-1928: unchanged
@line 1929 : r / "on two parameters" / "on two time parameters"
@lines 1930-1987: unchanged
@lines 1987 : add the following lines
If the scheduling policy of the target process is either SCHED_FIFO
or SCHED_RR, the sched_ss_low_priority , sched_ss_repl_period , and
sched_ss_init_budget members of the param argument shall have no effect
on the scheduling behavior. If the scheduling policy of this process is
not SCHED_FIFO, SCHED_RR, or SCHED_SPORADIC, the effects of these members
are implementation-defined; this case includes the SCHED_OTHER policy.
XBD ERN 48 fenv.h Accept as marked below
Geoff requested that we reopen XBD ERN 48 as the change proposed
was in conflict with ISO C. This also highlighted some
problems with the existing wording with respect to conflicts
with ISO C.
The following changes were agreed:
On page 226 fenv.h
Change 7943 "shall define the following" to
"shall define each of the following"
After 7952 Add
[MX]If the implementation supports the IEC 60559 Floating-Point
option, all five constants shall be defined. [/MX]
Additional implementation-defined floating-point exceptions
with constants beginning with FE_ and an uppercase letter
may also specified by the implementation.
Related change in XSH page 16 add (*cross volume change*)
after 597
Prefix column
FE_[A-Z]
XBD ERN 49 fenv.h Accept as marked below
The review of XBD ERN 48 above highlighted a problem
in that the text was ignoring implementation defined
floating-point exceptions.
The change was updated as follows
Change from:
"The header shall define the following constant, which is simply
the bitwise-inclusive OR of all floating-point exception constants
defined above:
FE_ALL_EXCEPT"
to:
"The header shall define the constant FE_ALL_EXCEPT as
the bitwise-inclusive OR of all floating-point exception constants
defined by the implementation, if any. If no such constants are defined
then the constant FE_ALL_EXCEPT shall be defined as zero."
XSH ERN 84 sigaction Accept as marked below
Change from:
This mask is formed by taking the union of the current signal mask and
the value of the sa_mask for the signal being delivered [XSI] [Option
Start] unless SA_NODEFER or SA_RESETHAND is set, [Option End] and
then including the signal being delivered.
to:
This mask is formed by taking the union of the current signal mask and
the value of the sa_mask for the signal being delivered, and [XSI] [Option
Start] unless SA_NODEFER or SA_RESETHAND is set, [Option End]
then including the signal being delivered.
XSH ERN 86 Accept html error
This is an editorial matter in the html generation.
XSH ERN 87 sem_open OPEN
It was agreed that we should defer this item until the
next meeting pending investigations of existing behavior.
-----------
Andrew will update the aardvark reports with the latest inbound
defect reports.
The next call is March 31 2005