:You can check the stack frame for the RIP and if it is alreday in the
:kernel, you can skip the swapgs. Given that you have to do more work for
:traps from userland anyway, that's a relatively cheap change.
:
:Joerg
You can't, because not all traps to the system disable interrupts.
This means that another interrupt can occur after the stack frame has
been pushed, but before swapgs has been run the first time.
It really is a lot easier to just load a pointer from a fixed address.
-Matt
Matthew Dillon
<dillon@backplane.com>| Kok, Auke | Re: -mm merge plans for 2.6.23 - ioat/dma engine |
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Matthew Garrett | [PATCH] Remove process freezer from suspend to RAM pathway |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
git: | |
