| /freebsd/sys/i386/include/ |
| H A D | pcpu.h | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| /freebsd/sys/amd64/include/ |
| H A D | pcpu.h | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| /freebsd/sys/i386/i386/ |
| H A D | sys_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | genassym.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | mp_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | vm_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| /freebsd/sys/amd64/amd64/ |
| H A D | sys_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | genassym.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | vm_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | mp_machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| H A D | machdep.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|
| /freebsd/sys/kern/ |
| H A D | subr_smp.c | diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
diff 287e61c39fb0133a57095482898b40905f19fb84 Tue Aug 18 09:47:12 CEST 1998 Mike Smith <msmith@FreeBSD.org> Presently there is only one `currentldt' variable for all cpus
in a SMP system. Unexpected things could happen if each cpu
has a different ldt setting and one cpu tries to use value
of currentldt set by another cpu.
The fix is to move currentldt to the per-cpu area. It includes
patches I filed in PR i386/6219 which are also user ldt related.
PR: i386/7591, i386/6219
Submitted by: Luoqi Chen <luoqi@watermarkgroup.com>
|