Searched hist:1.164 (Results 1 - 25 of 370) sorted by relevance

1234567891011>>

/src/sys/arch/x86/x86/
H A Dintr.c1.164 Wed Jan 25 15:54:53 GMT 2023 riastradh x86/intr: Work around sleazy clockintr with a secret frame argument.

PR kern/57197

/src/sys/arch/sun3/sun3/
H A Dpmap.c1.164 Fri Dec 11 13:52:57 GMT 2009 tsutsui branches: 1.164.2; 1.164.4;
Refactoring MD segment related definitions on m68k ports:
- move macro SEGSHIFT, NBSG, and SEGOFFSET from <machine/param.h>
to <machine/pmap.h> where they should belong
- don't use m68k_round_seg() and m68k_trunc_seg() in sun3 pmap sources
and instead define and use sun3_round_seg() and sun3_trunc_seg()
since they are quite pmap implementation dependent

1.164 Fri Dec 11 13:52:57 GMT 2009 tsutsui branches: 1.164.2; 1.164.4;
Refactoring MD segment related definitions on m68k ports:
- move macro SEGSHIFT, NBSG, and SEGOFFSET from <machine/param.h>
to <machine/pmap.h> where they should belong
- don't use m68k_round_seg() and m68k_trunc_seg() in sun3 pmap sources
and instead define and use sun3_round_seg() and sun3_trunc_seg()
since they are quite pmap implementation dependent

1.164 Fri Dec 11 13:52:57 GMT 2009 tsutsui branches: 1.164.2; 1.164.4;
Refactoring MD segment related definitions on m68k ports:
- move macro SEGSHIFT, NBSG, and SEGOFFSET from <machine/param.h>
to <machine/pmap.h> where they should belong
- don't use m68k_round_seg() and m68k_trunc_seg() in sun3 pmap sources
and instead define and use sun3_round_seg() and sun3_trunc_seg()
since they are quite pmap implementation dependent

/src/sys/arch/vax/vax/
H A Dmachdep.c1.164 Tue Mar 11 05:34:03 GMT 2008 matt branches: 1.164.4; 1.164.6; 1.164.8;
Rototill the vax code. Switch to devicet/PRIV_ALLOC. Cleanup vax autoconf
code. Move to prototype definitions. staticfy, constify, avoid casting.
Use device_* accessors.

1.164 Tue Mar 11 05:34:03 GMT 2008 matt branches: 1.164.4; 1.164.6; 1.164.8;
Rototill the vax code. Switch to devicet/PRIV_ALLOC. Cleanup vax autoconf
code. Move to prototype definitions. staticfy, constify, avoid casting.
Use device_* accessors.

1.164 Tue Mar 11 05:34:03 GMT 2008 matt branches: 1.164.4; 1.164.6; 1.164.8;
Rototill the vax code. Switch to devicet/PRIV_ALLOC. Cleanup vax autoconf
code. Move to prototype definitions. staticfy, constify, avoid casting.
Use device_* accessors.

1.164 Tue Mar 11 05:34:03 GMT 2008 matt branches: 1.164.4; 1.164.6; 1.164.8;
Rototill the vax code. Switch to devicet/PRIV_ALLOC. Cleanup vax autoconf
code. Move to prototype definitions. staticfy, constify, avoid casting.
Use device_* accessors.

H A Dpmap.c1.164 Wed Dec 17 20:51:32 GMT 2008 cegger branches: 1.164.2;
kill MALLOC and FREE macros.

1.164 Wed Dec 17 20:51:32 GMT 2008 cegger branches: 1.164.2;
kill MALLOC and FREE macros.

/src/sys/sys/
H A Dsyscall.h1.164 Sat Dec 03 17:07:12 GMT 2005 christos branches: 1.164.2; 1.164.4; 1.164.6;
Regen
1.164 Sat Dec 03 17:07:12 GMT 2005 christos branches: 1.164.2; 1.164.4; 1.164.6;
Regen
1.164 Sat Dec 03 17:07:12 GMT 2005 christos branches: 1.164.2; 1.164.4; 1.164.6;
Regen
1.164 Sat Dec 03 17:07:12 GMT 2005 christos branches: 1.164.2; 1.164.4; 1.164.6;
Regen
H A Dexec_elf.h1.164 Thu Jan 02 05:18:07 GMT 2020 kamil branches: 1.164.2;
Sync the e_ident[EI_OSABI] magic values with the ELF specification

source: http://www.sco.com/developers/gabi/latest/ch4.eheader.html
1.164 Thu Jan 02 05:18:07 GMT 2020 kamil branches: 1.164.2;
Sync the e_ident[EI_OSABI] magic values with the ELF specification

source: http://www.sco.com/developers/gabi/latest/ch4.eheader.html
/src/sys/ufs/ufs/
H A Dufs_vnops.c1.164 Wed Jan 30 09:50:27 GMT 2008 ad branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
Replace struct lock on vnodes with a simpler lock object built on
krwlock_t. This is a step towards removing lockmgr and simplifying
vnode locking. Discussed on tech-kern.

1.164 Wed Jan 30 09:50:27 GMT 2008 ad branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
Replace struct lock on vnodes with a simpler lock object built on
krwlock_t. This is a step towards removing lockmgr and simplifying
vnode locking. Discussed on tech-kern.

1.164 Wed Jan 30 09:50:27 GMT 2008 ad branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
Replace struct lock on vnodes with a simpler lock object built on
krwlock_t. This is a step towards removing lockmgr and simplifying
vnode locking. Discussed on tech-kern.

1.164 Wed Jan 30 09:50:27 GMT 2008 ad branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
Replace struct lock on vnodes with a simpler lock object built on
krwlock_t. This is a step towards removing lockmgr and simplifying
vnode locking. Discussed on tech-kern.

1.164 Wed Jan 30 09:50:27 GMT 2008 ad branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
Replace struct lock on vnodes with a simpler lock object built on
krwlock_t. This is a step towards removing lockmgr and simplifying
vnode locking. Discussed on tech-kern.

/src/sys/kern/
H A Dkern_subr.c1.164 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.164.2; 1.164.4;
Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed
on tech-kern.

1.164 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.164.2; 1.164.4;
Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed
on tech-kern.

1.164 Wed Aug 15 00:07:34 GMT 2007 ad branches: 1.164.2; 1.164.4;
Changes to make ktrace LKM friendly and reduce ifdef KTRACE. Proposed
on tech-kern.

H A Dmakesyscalls.sh1.164 Tue Jan 26 23:46:37 GMT 2016 pooka branches: 1.164.2;
fix typo in previous

1.164 Tue Jan 26 23:46:37 GMT 2016 pooka branches: 1.164.2;
fix typo in previous

H A Dkern_lwp.c1.164 Wed Oct 19 10:51:47 GMT 2011 yamt branches: 1.164.2; 1.164.6;
don't forget to call kdtrace_thread_ctor for lwp0

1.164 Wed Oct 19 10:51:47 GMT 2011 yamt branches: 1.164.2; 1.164.6;
don't forget to call kdtrace_thread_ctor for lwp0

1.164 Wed Oct 19 10:51:47 GMT 2011 yamt branches: 1.164.2; 1.164.6;
don't forget to call kdtrace_thread_ctor for lwp0

H A Dinit_sysent.c1.164 Sun May 29 21:11:30 GMT 2005 christos branches: 1.164.2;
Regen

1.164 Sun May 29 21:11:30 GMT 2005 christos branches: 1.164.2;
Regen

H A Dkern_ktrace.c1.164 Mon Dec 09 16:45:23 GMT 2013 pooka branches: 1.164.4;
Put vfs bits of ktrace into kern_ktrace_vfs.c per convention.

1.164 Mon Dec 09 16:45:23 GMT 2013 pooka branches: 1.164.4;
Put vfs bits of ktrace into kern_ktrace_vfs.c per convention.

H A Dkern_lock.c1.164 Tue Dec 03 15:20:59 GMT 2019 riastradh branches: 1.164.2;
Use __insn_barrier to enforce ordering in l_ncsw loops.

(Only need ordering observable by interruption, not by other CPUs.)

1.164 Tue Dec 03 15:20:59 GMT 2019 riastradh branches: 1.164.2;
Use __insn_barrier to enforce ordering in l_ncsw loops.

(Only need ordering observable by interruption, not by other CPUs.)

/src/sys/nfs/
H A Dnfs_bio.c1.164 Sun Jul 29 13:31:12 GMT 2007 ad branches: 1.164.4; 1.164.6;
It's not a good idea for device drivers to modify b_flags, as they don't
need to understand the locking around that field. Instead of setting
B_ERROR, set b_error instead. b_error is 'owned' by whoever completes
the I/O request.

1.164 Sun Jul 29 13:31:12 GMT 2007 ad branches: 1.164.4; 1.164.6;
It's not a good idea for device drivers to modify b_flags, as they don't
need to understand the locking around that field. Instead of setting
B_ERROR, set b_error instead. b_error is 'owned' by whoever completes
the I/O request.

1.164 Sun Jul 29 13:31:12 GMT 2007 ad branches: 1.164.4; 1.164.6;
It's not a good idea for device drivers to modify b_flags, as they don't
need to understand the locking around that field. Instead of setting
B_ERROR, set b_error instead. b_error is 'owned' by whoever completes
the I/O request.

H A Dnfs_socket.c1.164 Sun Oct 21 08:23:19 GMT 2007 yamt branches: 1.164.2; 1.164.4;
remove lwp argument from nfs_reconnect and always use &lwp0
because who triggers a reconnect doesn't really matter here. PR/37145.

1.164 Sun Oct 21 08:23:19 GMT 2007 yamt branches: 1.164.2; 1.164.4;
remove lwp argument from nfs_reconnect and always use &lwp0
because who triggers a reconnect doesn't really matter here. PR/37145.

1.164 Sun Oct 21 08:23:19 GMT 2007 yamt branches: 1.164.2; 1.164.4;
remove lwp argument from nfs_reconnect and always use &lwp0
because who triggers a reconnect doesn't really matter here. PR/37145.

H A Dnfs_vfsops.c1.164 Sat Sep 02 13:37:52 GMT 2006 yamt branches: 1.164.2; 1.164.4;
nfs_fhtovp: try to detect stale or invalid handles by issuing VOP_GETATTR.

1.164 Sat Sep 02 13:37:52 GMT 2006 yamt branches: 1.164.2; 1.164.4;
nfs_fhtovp: try to detect stale or invalid handles by issuing VOP_GETATTR.

1.164 Sat Sep 02 13:37:52 GMT 2006 yamt branches: 1.164.2; 1.164.4;
nfs_fhtovp: try to detect stale or invalid handles by issuing VOP_GETATTR.

/src/sys/dev/mii/
H A Dmiidevs.h1.164 Wed Apr 08 03:01:28 GMT 2020 msaitoh Regen.

/src/sys/arch/bebox/conf/
H A DGENERIC1.164 Sun Sep 27 13:48:50 GMT 2020 roy branches: 1.164.2;
vether: Add to kernel configurations

It's only enabled if the kernel enabled bridge AND tap.
Otherwise it's commented out.

1.164 Sun Sep 27 13:48:50 GMT 2020 roy branches: 1.164.2;
vether: Add to kernel configurations

It's only enabled if the kernel enabled bridge AND tap.
Otherwise it's commented out.

/src/sys/compat/sunos/
H A Dsunos_misc.c1.164 Sun Jan 11 00:44:47 GMT 2009 tsutsui branches: 1.164.2;
Update for compat_50 stuff. (compile test only)

1.164 Sun Jan 11 00:44:47 GMT 2009 tsutsui branches: 1.164.2;
Update for compat_50 stuff. (compile test only)

/src/distrib/notes/common/
H A Dcontents1.164 Tue Jan 18 00:35:19 GMT 2011 jym branches: 1.164.2;
XEN2 kernels are not part of the release any more. Support was removed
with NetBSD-6.
1.164 Tue Jan 18 00:35:19 GMT 2011 jym branches: 1.164.2;
XEN2 kernels are not part of the release any more. Support was removed
with NetBSD-6.
/src/sys/dev/usb/
H A Dukbd.c1.164 Sat Sep 02 17:43:16 GMT 2023 riastradh branches: 1.164.6;
ukbd(4): Sort includes.

No functional change intended.

1.164 Sat Sep 02 17:43:16 GMT 2023 riastradh branches: 1.164.6;
ukbd(4): Sort includes.

No functional change intended.

/src/sys/arch/macppc/macppc/
H A Dmachdep.c1.164 Tue Dec 11 03:00:00 GMT 2012 macallan branches: 1.164.14;
work around a bug in some (all?) nvidia OF ROMs:
the color! method always changes only the palette registers associated with the
first, usually analog head, even if the monitor in use is on port 2, usually
DVI or ADC.
Don't enable cmap_callback when we find out we're on port 2 of an nvidia card,
that way genfb won't try to use R3G3B2 colours and assume something resembling
an ANSI palette which will at least gives us something usable, as opposed to
black on mostly black.

1.164 Tue Dec 11 03:00:00 GMT 2012 macallan branches: 1.164.14;
work around a bug in some (all?) nvidia OF ROMs:
the color! method always changes only the palette registers associated with the
first, usually analog head, even if the monitor in use is on port 2, usually
DVI or ADC.
Don't enable cmap_callback when we find out we're on port 2 of an nvidia card,
that way genfb won't try to use R3G3B2 colours and assume something resembling
an ANSI palette which will at least gives us something usable, as opposed to
black on mostly black.

/src/sys/arch/arm/arm32/
H A Dpmap.c1.164 Thu May 17 14:51:16 GMT 2007 yamt branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
merge yamt-idlelwp branch. asked by core@. some ports still needs work.

from doc/BRANCHES:

idle lwp, and some changes depending on it.

1. separate context switching and thread scheduling.
(cf. gmcgarry_ctxsw)
2. implement idle lwp.
3. clean up related MD/MI interfaces.
4. make scheduler(s) modular.

1.164 Thu May 17 14:51:16 GMT 2007 yamt branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
merge yamt-idlelwp branch. asked by core@. some ports still needs work.

from doc/BRANCHES:

idle lwp, and some changes depending on it.

1. separate context switching and thread scheduling.
(cf. gmcgarry_ctxsw)
2. implement idle lwp.
3. clean up related MD/MI interfaces.
4. make scheduler(s) modular.

1.164 Thu May 17 14:51:16 GMT 2007 yamt branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
merge yamt-idlelwp branch. asked by core@. some ports still needs work.

from doc/BRANCHES:

idle lwp, and some changes depending on it.

1. separate context switching and thread scheduling.
(cf. gmcgarry_ctxsw)
2. implement idle lwp.
3. clean up related MD/MI interfaces.
4. make scheduler(s) modular.

1.164 Thu May 17 14:51:16 GMT 2007 yamt branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
merge yamt-idlelwp branch. asked by core@. some ports still needs work.

from doc/BRANCHES:

idle lwp, and some changes depending on it.

1. separate context switching and thread scheduling.
(cf. gmcgarry_ctxsw)
2. implement idle lwp.
3. clean up related MD/MI interfaces.
4. make scheduler(s) modular.

1.164 Thu May 17 14:51:16 GMT 2007 yamt branches: 1.164.6; 1.164.8; 1.164.10; 1.164.12;
merge yamt-idlelwp branch. asked by core@. some ports still needs work.

from doc/BRANCHES:

idle lwp, and some changes depending on it.

1. separate context switching and thread scheduling.
(cf. gmcgarry_ctxsw)
2. implement idle lwp.
3. clean up related MD/MI interfaces.
4. make scheduler(s) modular.

/src/sys/ufs/ffs/
H A Dffs_alloc.c1.164 Sun Apr 14 15:55:24 GMT 2019 kardel branches: 1.164.4; 1.164.6;
PR/53990, PR/52380, PR/52102: UFS2 cylinder group inode allocation botch

Fix rare allocation botch in ffs_nodealloccg().

Conditions:
a) less than
#_of_initialized_inodes(cg->cg_initediblk)
- inodes_per_filesystem_block
are allocated in the cylinder group
b) cg->cg_irotor points to a uninterupted run of
allocated inodes in the inode bitmap up to the
end of dynamically initialized inodes
(cg->cg_initediblk)

In this case the next inode after this run was returned
without initializing the respective inode block. As the
block is not initialized these inodes could trigger panics
on inode consistency due to old (uninitialized) disk data.

In very rare cases data loss could occur when
the uninitialized inode block is initialized via the
normal mechanism.
Further conditions to occur after the above:
c) no panic
d) no (forced) fsck
e) and more than cg->cg_initediblk - inodes_per_filesystem_block
allocated inodes.

Fix:
Always insure allocation always in initialized inode range
extending the initialized inode range as needed.

Add KASSERTMSG() safeguards.

ok hannken@

1.164 Sun Apr 14 15:55:24 GMT 2019 kardel branches: 1.164.4; 1.164.6;
PR/53990, PR/52380, PR/52102: UFS2 cylinder group inode allocation botch

Fix rare allocation botch in ffs_nodealloccg().

Conditions:
a) less than
#_of_initialized_inodes(cg->cg_initediblk)
- inodes_per_filesystem_block
are allocated in the cylinder group
b) cg->cg_irotor points to a uninterupted run of
allocated inodes in the inode bitmap up to the
end of dynamically initialized inodes
(cg->cg_initediblk)

In this case the next inode after this run was returned
without initializing the respective inode block. As the
block is not initialized these inodes could trigger panics
on inode consistency due to old (uninitialized) disk data.

In very rare cases data loss could occur when
the uninitialized inode block is initialized via the
normal mechanism.
Further conditions to occur after the above:
c) no panic
d) no (forced) fsck
e) and more than cg->cg_initediblk - inodes_per_filesystem_block
allocated inodes.

Fix:
Always insure allocation always in initialized inode range
extending the initialized inode range as needed.

Add KASSERTMSG() safeguards.

ok hannken@

1.164 Sun Apr 14 15:55:24 GMT 2019 kardel branches: 1.164.4; 1.164.6;
PR/53990, PR/52380, PR/52102: UFS2 cylinder group inode allocation botch

Fix rare allocation botch in ffs_nodealloccg().

Conditions:
a) less than
#_of_initialized_inodes(cg->cg_initediblk)
- inodes_per_filesystem_block
are allocated in the cylinder group
b) cg->cg_irotor points to a uninterupted run of
allocated inodes in the inode bitmap up to the
end of dynamically initialized inodes
(cg->cg_initediblk)

In this case the next inode after this run was returned
without initializing the respective inode block. As the
block is not initialized these inodes could trigger panics
on inode consistency due to old (uninitialized) disk data.

In very rare cases data loss could occur when
the uninitialized inode block is initialized via the
normal mechanism.
Further conditions to occur after the above:
c) no panic
d) no (forced) fsck
e) and more than cg->cg_initediblk - inodes_per_filesystem_block
allocated inodes.

Fix:
Always insure allocation always in initialized inode range
extending the initialized inode range as needed.

Add KASSERTMSG() safeguards.

ok hannken@

/src/sys/arch/vax/conf/
H A DGENERIC1.164 Fri May 30 20:10:03 GMT 2008 tsutsui branches: 1.164.4;
Add options COMPAT_40 to files which have options COMPAT_30.

1.164 Fri May 30 20:10:03 GMT 2008 tsutsui branches: 1.164.4;
Add options COMPAT_40 to files which have options COMPAT_30.

Completed in 229 milliseconds

1234567891011>>