Searched hist:1.1309 (Results 1 - 11 of 11) sorted by relevance

/src/sys/dev/pci/
H A Dpcidevs.h1.1309 Fri Mar 02 06:41:18 GMT 2018 msaitoh Regen.
H A Dpcidevs_data.h1.1309 Sun Mar 04 13:13:18 GMT 2018 jdolecek regen
H A Dpcidevs1.1309 Sat Feb 17 00:45:14 GMT 2018 sevan grammar
/src/doc/
H A D3RDPARTY1.1309 Wed Mar 02 01:54:19 GMT 2016 christos new openssl
H A DCHANGES1.1309 Wed Oct 21 21:28:36 GMT 2009 rmind 5.99.21: removed uarea swap-out functionality.
/src/distrib/sets/lists/base/
H A Dmi1.1309 Wed Jun 08 19:27:37 GMT 2022 uwe Terminus Font: Import latin1 encoded versions from 4.49.1
/src/distrib/sets/lists/man/
H A Dmi1.1309 Fri Apr 15 18:05:44 GMT 2011 elric Upgrade Heimdal to 1.5pre1 by switching the build from crypto/dist/heimdal
to crypto/external/bsd/heimdal. The latter was just imported as the head
of the Heimdal tree as of a few days ago.
/src/distrib/sets/lists/tests/
H A Dmi1.1309 Sun Mar 03 00:50:41 GMT 2024 rillig lint: check for unreachable bits and fields in snprintb formats

While here, clean up a few existing checks.
/src/share/mk/
H A Dbsd.own.mk1.1309 Sun Apr 02 15:06:06 GMT 2023 christos switch gdb to gdb.old
/src/sys/conf/
H A Dfiles1.1309 Sun Sep 10 14:04:28 GMT 2023 abs Rework AHCISATA_EXTRA_DELAY for kern/56737

- Remove AHCI_QUIRK_EXTRA_DELAY as issue appears to be drive and
not controller related
- Replace AHCISATA_EXTRA_DELAY with AHCISATA_REMOVE_EXTRA_DELAY,
so defaulting to enabling the extra delay, as the downside of
slower probing on systems which do not need it is less than having
other systems intermittently fail to probe and attach drives
- Also allow disabling extra delay with AHCISATA_EXTRA_DELAY_MS = 0

We should return to this code to work out which of the extra delays
are needed, and how long they need to be. It may be that faster
systems are more likely to trigger the issue (I've only seen it on
a 13th gen i7-13700, though only tested on a limited set)

XXX pullup -10
/src/distrib/sets/lists/comp/
H A Dmi1.1309 Wed Sep 16 16:34:49 GMT 2009 dyoung In pmf(9), improve the implementation of device self-suspension
and make suspension by self, by drvctl(8), and by ACPI system sleep
play nice together. Start solidifying some temporary API changes.

1. Extract a new header file, <sys/device_if.h>, from <sys/device.h> and
#include it from <sys/pmf.h> instead of <sys/device.h> to break the
circular dependency between <sys/device.h> and <sys/pmf.h>.

2. Introduce pmf_qual_t, an aggregate of qualifications on a PMF
suspend/resume call. Start to replace instances of PMF_FN_PROTO,
PMF_FN_ARGS, et cetera, with a pmf_qual_t.

3. Introduce the notion of a "suspensor," an entity that holds a
device in suspension. More than one suspensor may hold a device
at once. A device stays suspended as long as at least one
suspensor holds it. A device resumes when the last suspensor
releases it.

Currently, the kernel defines three suspensors,

3a the system-suspensor: for system suspension, initiated
by 'sysctl -w machdep.sleep_state=3', by lid closure, by
power-button press, et cetera,

3b the drvctl-suspensor: for device suspension by /dev/drvctl
ioctl, e.g., drvctl -S sip0.

3c the system self-suspensor: for device drivers that suspend
themselves and their children. Several drivers for network
interfaces put the network device to sleep while it is not
administratively up, that is, after the kernel calls if_stop(,
1). The self-suspensor should not be used directly. See
the description of suspensor delegates, below.

A suspensor can have one or more "delegates". A suspensor can
release devices that its delegates hold suspended. Right now,
only the system self-suspensor has delegates. For each device
that a self-suspending driver attaches, it creates the device's
self-suspensor, a delegate of the system self-suspensor.

Suspensors stop a system-wide suspend/resume cycle from waking
devices that the operator put to sleep with drvctl before the cycle.
They also help self-suspension to work more simply, safely, and in
accord with expectations.

4. Add the notion of device activation level, devact_level_t,
and a routine for checking the current activation level,
device_activation(). Current activation levels are DEVACT_LEVEL_BUS,
DEVACT_LEVEL_DRIVER, and DEVACT_LEVEL_CLASS, which respectively
indicate that the device's bus is active, that the bus and device are
active, and that the bus, device, and the functions of the device's
class (network, audio) are active.

Suspend/resume calls can be qualified with a devact_level_t.
The power-management framework treats a devact_level_t that
qualifies a device suspension as the device's current activation
level; it only runs hooks to reduce the activation level from
the presumed current level to the fully suspended state. The
framework treats a devact_level_t qualifying device resumption
as the target activation level; it only runs hooks to raise the
activation level to the target.

5. Use pmf_qual_t, devact_level_t, and self-suspensors in several
drivers.

6. Temporarily add an unused power-management workqueue that I will
remove or replace, soon.

Completed in 1029 milliseconds