| 1. | Above example shows how to setup user mode redirection debug
上面的步骤演示了如何设定核心态调试，如何重定向用户态调试。 |
| 2. | The driver which communicates to user mode does not talk directly to hardware
硬盘驱动中和用户态通讯的部分通常不会直接和硬件打交道。 |
| 3. | We can then use the returned address to access the buffer passed down from user mode
我们可以使用它的返回值来访问被用户态所传入的缓冲区。 |
| 4. | So , this simply maps the physical pages used by the user mode process into system memory
所以，这只是简单的映射被用户态使用的物理页面到系统内存中。 |
| 5. | The whole user mode page doesn ' t need to be locked in memory as with direct i / o , which is the plus side of this
整个用户态的页不需要再像直接访问输入输出那样被锁定，这是它的好的方面。 |
| 6. | The user mode buffers are locked in memory until the irp is completed which is the downside of using direct i / o
用户态的缓冲区在irp请求完成之前是被锁定的，这是使用直接输入输出的不利方面。 |
| 7. | However , the major question is not about how to do that , it is “ why we need to debug user mode application in kernel session
但是问题的关键不在于如何做，而是在于为何需要把用户态程序重定向到核心态？ |
| 8. | If you need to monitor both kernel and user mode issues , combining them into a single session is the most convenient way
如果需要同时监视用户态程序和核心态的问题，把两者合在一起显然是一种很好的办法。 |
| 9. | Finally , a strict operational experiment of axis control was carried out by implementing the user mode application and the result of the test was obtained
最后，通过编写轴控制系统用户态程序，本文完成了轴控制的实际运行实验，并给出了实验结果。 |
| 10. | The reasoning behind this is that some drivers do not always process a user mode request in the context of the thread or even the process in which it was issued
这背后的原因是某些驱动并非总是在所发请求的线程甚至是进程的上下文中来处理用户态的请求。 |
