Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)

From: Julian Elischer (julian_at_elischer.org)
Date: 08/02/03

  • Next message: Daniel Eischen: "Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)" 
    Date: Fri, 1 Aug 2003 16:20:05 -0700 (PDT)
To: deischen@freebsd.org

    On Fri, 1 Aug 2003, Daniel Eischen wrote:

    > On Fri, 1 Aug 2003, Marcel Moolenaar wrote:
    >
    > > On Fri, Aug 01, 2003 at 06:51:33PM -0400, Daniel Eischen wrote:
    > >
    > > > > LUCODE_SEL is used by kernel to load _ucodesel to user %cs
    > > > > LUDATA_SEL is used by kernel to load _udatasel to user %ds, %es, %fs, %gs.
    > > > > I didn't check other ABIs, but setting to a fixed location of LDT in userland
    > > > > is also a bad idea, I think it will conflict with thread library soon,
    > > > > it is better to use dynamic allocating facility newly added in i386_set_ldt.
    > > >
    > > > Perhaps we need to rethink the interface and disallow
    > > > specification of any ldt; only allow dynamic. We would
    > > > need a different method of setting an array of them, though.
    > >
    > > Why not allow setting a specific entry when it's currently unused
    > > and not reserved by us?
    > > We can simply fail if the process is trying to set a LDT entry that's
    > > currently being used or is reserved by us. The only case that causes
    > > problems is when an existing LDT entry is overwritten by another
    > > consumer.
    >
    > That's what I was worried about. Once an application or
    > library is written to use specific LDTs, you never know
    > how it will be affected by the use of threading libraries
    > (or other libraries using threads).
    >
    > I can see the need to keep the old behavoir for compatibility's
    > sake.

    How about we complain loudly on the console when it's done..
    (for the first few times)
    (with info on how to do it right)

    >
    > --
    > Dan Eischen
    >
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    >

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Daniel Eischen: "Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)"

    Relevant Pages

    • Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)
      ... >> Perhaps we need to rethink the interface and disallow ... > We can simply fail if the process is trying to set a LDT entry that's ... how it will be affected by the use of threading libraries ... (or other libraries using threads). ...
      (freebsd-current)
    • Re: how do static import libraries actually work?
      ... "I could create an import library called xxx.lib that contained an entry ... One thing I've never really understood are import libraries for DLLs ... Without linking to user32.lib in VS I get a link error, ... What happens when you statically link to a DLL import library (i.e. ...
      (microsoft.public.vc.language)
    • Re: ENTRY statement
      ... produce libraries that contain a Fortran77 style alias (for example I ...    end interface ... These all have some advantages and disadvantages compared to entry ... For procedures to be used by Fortran 90 and higher compilers these ...
      (comp.lang.fortran)
    • Re: how do static import libraries actually work?
      ... One thing I've never really understood are import libraries for DLLs ... What happens when you statically link to a DLL import library (i.e. ... compiler just calls, for example, CreateWindowA. ... know where that entry point will come from, it relies on the linker to fix ...
      (microsoft.public.vc.language)
    • Re: compile+link Fujitsu Linux
      ... Red Hat Linux 7.2, Locale C ... There is no Cobol syntax to specify a library name. ... It searches only the libraries named in the executable's ELF ... Libraries normally contain many programs and entry points. ...
      (comp.lang.cobol)