Re: sysenter patch question
- From: Scott Long <scottl@xxxxxxxxxx>
- Date: Sat, 14 Jan 2006 13:02:50 -0700
Suleiman Souhlal wrote:
Scott Long wrote:
I was the last to work on the patch, and that was about a year or so ago. It worked fine under fairly simple processes, but trying to run things like KDE and Mozilla made it blow up fairly quickly. I suspect that it has something to do with thread upcalls, but I never got around to figuring it out. If someone wants to pick it up, that would be great. Note that this only matters for i386; amd64 has always had its own version of sysenter that it uses.
As far as I know, amd64 uses the SYSCALL instruction, which I believe, should have about the same performance as SYSENTER.
--Suleiman
Actually, the AMD SYSCALL command is a heck of a lot easier to use since it doesn't make as many assumptions about segment descriptors.
Scott
_______________________________________________ freebsd-current@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- sysenter patch question
- From: Divacky Roman
- Re: sysenter patch question
- From: Scott Long
- Re: sysenter patch question
- From: Suleiman Souhlal
- sysenter patch question
- Prev by Date: Re: make or kmod.mk broken
- Next by Date: .PATH-problem [was Re: make or kmod.mk broken]
- Previous by thread: Re: sysenter patch question
- Next by thread: Re: Brief Report: IBM/Lenovo z60t notebook with FreeBSD
- Index(es):
Relevant Pages
|