会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明申请
    • Switching user mode thread context
    • 切换用户模式线程上下文
    • US20080320475A1
    • 2008-12-25
    • US11820422
    • 2007-06-19
    • Matthew D. KleinPaul England
    • Matthew D. KleinPaul England
    • G06F9/46
    • G06F9/461
    • Various technologies and techniques are disclosed for switching user mode thread context. A user mode portion of a thread can be switched without entering a kernel by using execution context directly based on registers. Upon receiving a request to switch a user mode part of a thread to a new thread, user mode register contexts are switched, as well as a user mode thread block by changing an appropriate register to point at the user mode thread block of the new thread. Switching is available in environments using segment registers with offsets. Each user mode thread block in a process has a descriptor in a local descriptor table. When switching a user mode thread context to a new thread, a descriptor is located for a user mode thread block of the new thread. A shadow register is updated with a descriptor base address of the new thread.
    • 公开了用于切换用户模式线程上下文的各种技术和技术。 线程的用户模式部分可以通过直接基于寄存器使用执行上下文来切换而不进入内核。 在接收到将线程的用户模式部分切换到新线程的请求时,通过将适当的寄存器改变为指向新线程的用户模式线程块来切换用户模式注册上下文以及用户模式线程块 。 在使用带偏移量的段寄存器的环境中可以进行切换。 进程中的每个用户模式线程块在本地描述符表中都有描述符。 当将用户模式线程上下文切换到新线程时,将为新线程的用户模式线程块定位描述符。 影子寄存器用新线程的描述符基地址更新。
    • 2. 发明申请
    • Notifying user mode scheduler of blocking events
    • 通知用户模式调度程序阻塞事件
    • US20080313652A1
    • 2008-12-18
    • US11818627
    • 2007-06-15
    • Matthew D. KleinPaul England
    • Matthew D. KleinPaul England
    • G06F13/00
    • G06F9/485G06F9/524
    • Various technologies and techniques are disclosed for detecting and handling blocking events. A user mode thread is assigned a dedicated backing thread. System calls are made on the dedicated backing thread. The kernel detects when a system call results in a blocking event. A core that the dedicated backing thread is currently running on is observed. An entry in a per process table that maps cores to a currently associated primary thread waiting to be woken is consulted. The currently associated primary thread for the core is woken with a special result code to indicate that it was woken due to the blocking system call. The primary thread is released back to the application. A user mode scheduler is notified of the blocking event so a core can continue to be utilized.
    • 公开了用于检测和处理阻塞事件的各种技术和技术。 用户模式线程被分配一个专用的背衬线程。 系统调用在专用后备线上进行。 内核检测系统调用何时导致阻塞事件。 观察到专用背衬线程正在运行的核心。 在每个进程表中,将核心映射到等待被唤醒的当前关联的主线程中的一个条目。 用于核心的当前关联的主线程用特殊结果代码唤醒,以指示由于阻塞系统调用而唤醒它。 主线程被释放回应用程序。 通知用户模式调度器阻塞事件,以便核心可以继续被利用。
    • 3. 发明申请
    • Thread virtualization techniques
    • 线程虚拟化技术
    • US20080313647A1
    • 2008-12-18
    • US11820065
    • 2007-06-18
    • Matthew D. KleinPaul England
    • Matthew D. KleinPaul England
    • G06F13/00
    • G06F9/545G06F9/45537
    • Various technologies and techniques are disclosed for virtualizing threads. An operating system thread is virtualized by intercepting accesses of the operating system thread state and emulating a normal operating system behavior. A kernel mode thread state is virtualized by intercepting kernel accesses of the kernel mode thread state and emulating a normal kernel mode behavior. A user mode thread state is virtualized by intercepting user mode accesses of the user mode thread state and emulating a normal user mode behavior. If the access is a write access, then the write access is applied to a virtual thread structure. If the access is a read access, then the read access is applied to the virtual thread structure.
    • 公开了用于虚拟化线程的各种技术和技术。 通过拦截操作系统线程状态的访问并仿真正常的操作系统行为来虚拟化操作系统线程。 内核模式线程状态通过截取内核模式线程状态的内核访问并模拟正常内核模式行为进行虚拟化。 通过拦截用户模式线程状态的用户模式访问并模拟正常的用户模式行为来虚拟化用户模式线程状态。 如果访问是写入访问,则写访问被应用于虚拟线程结构。 如果访问是读访问,则读访问被应用于虚拟线程结构。
    • 4. 发明申请
    • Lazy kernel thread binding
    • 懒惰的内核线程绑定
    • US20080307419A1
    • 2008-12-11
    • US11810649
    • 2007-06-06
    • Matthew D. KleinPaul England
    • Matthew D. KleinPaul England
    • G06F9/46
    • G06F9/4881
    • Various technologies and techniques are disclosed for providing lazy kernel thread binding. User mode and kernel mode portions of thread scheduling are decoupled so that a particular user mode thread can be run on any one of multiple kernel mode threads. A dedicated backing thread is used whenever a user mode thread wants to perform an operation that could affect the kernel mode thread, such as a system call. For example, a notice is received that a particular user mode thread running on a particular kernel mode thread wants to make a system call. A dedicated backing thread that has been assigned to the particular user mode thread is woken. State is shuffled from the user mode thread to the dedicated backing thread using a state shuffling process. The particular kernel mode thread is put to sleep. The system call is executed using the dedicated backing thread.
    • 公开了各种技术和技术来提供延迟的内核线程绑定。 线程调度的用户模式和内核模式部分被解耦,使得特定用户模式线程可以在多个内核模式线程中的任何一个上运行。 只要用户模式线程想要执行可能影响内核模式线程的操作(如系统调用),就使用专用的后备线程。 例如,接收到在特定内核模式线程上运行的特定用户模式线程想要进行系统调用的通知。 已分配给特定用户模式线程的专用后退线程被唤醒。 状态从用户模式线程被洗牌到使用状态洗牌过程的专用后备线程。 特定的内核模式线程进入睡眠状态。 系统调用使用专用的后备线程执行。
    • 5. 发明申请
    • User mode stack disassociation
    • 用户模式堆栈解除关联
    • US20080313656A1
    • 2008-12-18
    • US11820164
    • 2007-06-18
    • Matthew D. KleinPaul England
    • Matthew D. KleinPaul England
    • G06F9/44
    • G06F9/545G06F9/544
    • Various technologies and techniques are disclosed for allowing a user mode stack to be shared by multiple contexts. A user mode stack can be shared between execution contexts that are guaranteed to not need the user mode stack at the same time. For example, each user mode portion of a kernel thread is provided with a dedicated backing thread. When a respective dedicated backing thread is sleeping and not using a respective user mode stack, the user mode stack is allowed to float with a respective user mode portion to other kernel threads. The user mode stack is disassociated from the kernel portion of the thread. The kernel is notified of an address of a user mode thread context. The kernel mode portion of the converted thread becomes a backing thread that waits. The user mode portion of the converted thread can be switched without entering the kernel.
    • 公开了允许用户模式堆栈由多个上下文共享的各种技术和技术。 用户模式堆栈可以在保证不需要用户模式堆栈的执行上下文之间共享。 例如,内核线程的每个用户模式部分被提供有专用背衬线程。 当相应的专用后备线程正在休眠而不使用相应的用户模式堆栈时,允许用户模式堆栈以相应的用户模式部分浮动到其他内核线程。 用户模式堆栈与线程的内核部分取消关联。 内核被通知用户模式线程上下文的地址。 转换的线程的内核模式部分成为等待的后备线程。 可以切换转换后的线程的用户模式部分而不进入内核。
    • 7. 发明授权
    • Coupled symbiotic operating system
    • 耦合共生操作系统
    • US08738890B2
    • 2014-05-27
    • US13178908
    • 2011-07-08
    • Paul EnglandJork LoeserLuis Irun-Briz
    • Paul EnglandJork LoeserLuis Irun-Briz
    • G06F9/52G06F12/08
    • G06F12/1036G06F9/545G06F12/109G06F2212/656
    • A single application can be executed across multiple execution environments in an efficient manner if at least a relevant portion of the virtual memory assigned to the application was equally accessible by each of the multiple execution environments. A request by a process in one execution environment can, thereby, be directed to an operating system, or other core software, in another execution environment and can be made by a shadow of the requesting process in the same manner as the original request was made by the requesting process itself. Because of the memory invariance between the execution environments, the results of the request will be equally accessible to the original requesting process even though the underlying software that responded to the request may be executing in a different execution environment. A similar thread invariance can be maintained to provide for accurate translation of requests between execution environments.
    • 如果分配给应用的虚拟存储器的至少相关部分可以被多个执行环境中的每个执行环境同等地访问,则可以以有效的方式在多个执行环境中执行单个应用。 一个执行环境中的进程的请求可以由此被引导到另一执行环境中的操作系统或其他核心软件,并且可以以与原始请求相同的方式通过请求进程的阴影来进行 通过请求过程本身。 由于执行环境之间的内存不变性,即使响应请求的底层软件可能在不同的执行环境中执行,原始请求进程的请求结果也可以同样访问。 可以维护类似的线程不变性,以便在执行环境之间提供精确的请求转换。
    • 10. 发明授权
    • Secure execution environment on external device
    • 外部设备上的安全执行环境
    • US08352740B2
    • 2013-01-08
    • US12125929
    • 2008-05-23
    • Paul England
    • Paul England
    • G06F21/00
    • H04L9/0897H04L9/3234H04L9/3263H04L9/3271H04L2209/76
    • A device, such as a smartcard, may be externally-connected to a host platform and may be used to enhance or extend security services provided by the host platform's Trusted Platform Module (TPM). The device and the platform exchange keys in order to facilitate reliable identification of the platform by the device and vice versa, and to support cryptographic tunneling. A proxy component on the host device tunnels information between the platform and the device, and also provides the device with access to the TPM's services such as sealing and attestation. The device can provide secure services to the platform, and may condition provision of these services on conditions such as confirming the platform's identity through the exchanged keys, or platform state measurements reported by the TPM.
    • 诸如智能卡的设备可以被外部连接到主机平台,并且可以用于增强或扩展由主机平台的可信平台模块(TPM)提供的安全服务。 设备和平台交换密钥,以便于设备对平台的可靠识别,反之亦然,并支持加密隧道。 主机上的代理组件可以在平台和设备之间隧道传输信息,还可以让设备访问TPM的服务,如密封和认证。 该设备可以向平台提供安全服务,并且可以在诸如通过交换的密钥确认平台的身份或由TPM报告的平台状态测量的条件下对这些服务的提供进行调节。