Microsoft Technology Licensing, LLC

Ashok Cholpady Kamath

Subramanian Ramaswamy

Vance Palmer Morrison

Brian LaMacchia

Gregory Darrell Fee

Loren Kohnfelder

Jan Kotas

Feng Yuan

Bertan Aygun

Ritesh Rambhai Parikh

David J Hiniker-Roosa

Ryan Alexander Dawson

Alex Jordan Yuter

Gianting Yeh

Mohamed Abd El-Aziz

Louis Carl Pepin

Sebastien Daniel Guillemot

Sedar Gokbulut

Systems and methods for sending in-product notifications to individual users of a software product or a specifically identified subset of users of the software product selected via their previously observed interactions with the software product.

In-product notifications targeting specific users selected via data analysis

A working set profiler can monitor an execution of a program or can monitor a user-specified portion of a program to identify methods executed within the monitored execution and associate memory page accesses with each of the identified methods. Memory page accesses are categorized as shared or exclusive, where a shared page is a page that is accessed by more than one method and where an exclusive page is a page that is accessed by only one method in the monitored portion of the program. A call tree can be constructed and augmented with the collected information regarding memory page accesses. Further, for shared pages, the name of the method with which a particular method shares the page access can be collected. The augmented call tree information can be analyzed and prioritized to identify methods whose elimination would reduce program latency.

Working set profiler

Idle processor cores can be used to compile methods that are likely to be executed by a program based on profile data that is captured during one or more previous executions. Methods that are determined by the profile data to be likely to be used can be compiled eagerly on one or more background threads. Transparency can be achieved by ensuring that module load order is not altered because of the background threads by recording the state of loaded modules after each profiled compilation, persisting that data, and waiting to eagerly compile a method until the method to be compiled and all its dependencies has been loaded by the executing program.

Profile driven multicore background compilation

A system and method determine whether a called code frame has a requested permission available to it, so as to be able to execute a protected operation. A code frame is contained within a code assembly received from a remote or local resource location. A policy manager generates a permission grant set containing permission grant objects associated with the code assembly. Both the permission grant set and the code assembly are loaded into a runtime call stack for runtime execution of one or more code frames. Calls to other code frames may involve loading additional code assemblies and permission grant sets into the runtime call stack. In order for a called code frame to perform a protected operation, the code frame demands a requested permission from its calling code frame and all code frames preceding the calling code frame on the runtime call stack as part of a stack walk operation. If the calling code frame and the preceding call frames can satisfy the requested permission, the called code frame can perform the protected operation (absent stack overrides). Otherwise, a security exception is thrown and the called code frame is inhibited from performing the protected operation (absent stack overrides). Stack overrides may be employed to dynamically modify the stack walk operation. To increase performance, a stack walk may be avoided by caching an intersection of the permission grants of all code assemblies in the application.

Applying a permission grant set to a call stack during runtime

Growing community of inventors

Sammamish, WA, United States of America

Ashok Cholpady Kamath