Back to results
US 7,849,467 B2Granted
Handling a signal at an application context that employs a remote kernel service
AssigneeHewlett-Packard Development Company, L.P.
InventorsEdward J. Sharpe, James Alan Woodward, Jenchang Ho
Life of this patent
Estimating the term…
Abstract
To handle a signal received at an application context that employs a remote kernel service implemented in a server context different from the application context, the remote kernel service receives from the application context a first signal. Using a signal action vector file associated with the server context, a first action code associated with the first signal is ascertained. If the first action code represents a pseudo-handler, the remote kernel service is aborted.
Claims21
A method, implemented in a computer, for handling a signal received at an application context, said application context employing a first remote kernel service implemented in a first server context, comprising:
- receiving at said first remote kernel service in the computer, from said application context, a first signal corresponding to the signal received at said application context, wherein said application context is different from said first server context in which said first remote kernel service resides;
- ascertaining, using a first signal action vector file associated with said first server context, a first action code associated with said first signal, wherein said first signal action vector file has entries corresponding to a plurality of pseudo-handlers that are not associated with any meaningful address;
- if said first action code represents a particular one of the pseudo-handlers, aborting said first remote kernel service;
- ascertaining, prior to sending said first signal from said application context to said first remote kernel service, a second action code associated with said first signal;
- and
- ignoring said first signal, thereby causing said first signal not to be sent from said application context to said first remote kernel service, if said second action code represents an ignore action.
3 more elements
The method of clam 1, further comprising sending said first signal from said application context to said first server context, wherein a signal number of said first signal is the same as a signal number of the signal received at said application context.
A computer system comprising:
- programmable circuits;
- and
- a computer readable storage medium storing instructions that upon execution by the programmable circuits cause the programmable circuits to:
- receive a remote procedure call at a server context, said remote procedure call representing a request to employ a kernel service in said server context on behalf of a calling entity associated with an application context that is different from said server context;
- in response to the remote procedure call, establish a first signal action vector associated with said server context, wherein said first signal action vector has plural action codes corresponding to plural respective signals, wherein multiple ones of the plural action codes correspond to pseudo-handlers, and wherein each of said pseudo-handlers mimics a handler address without corresponding to a meaningful address;
- receive, at said server context from said application context, a first signal;
- in response to said first signal, consult said first signal action vector;
- abort a wait state of said kernel service if said first signal corresponds to a particular one of the pseudo-handlers in said first signal action vector;
- over-write a given pseudo-handler in said first signal action vector with an “ignore” action code;
- receive, at said server context from said application context, a second signal;
- in response to said second signal, consult said first signal action vector;
- and
- in response to determining that said second signal corresponds to an entry that has the “ignore” action code, ignore said second signal at said server context.
10 more elements
A method, implemented in a computer, for handling a signal received at an application context, said application context employing a first remote kernel service implemented in a first server context, comprising:
- receiving at said first remote kernel service in the computer, from said application context, a first signal corresponding to the signal received at said application context, wherein said application context is different from said first server context in which said first remote kernel service resides;
- ascertaining, using a first signal action vector file associated with said first server context, a first action code associated with said first signal, wherein said first signal action vector file has entries corresponding to a plurality of pseudo-handlers that are not associated with any meaningful address;
- if said first action code represents a particular one of the pseudo-handlers, aborting said first remote kernel service;
- attempting to launch the particular pseudo-handler after the aborting, wherein no real handler is launched at said first server context as a result of the attempting;
- after the aborting of said first remote kernel service, aborting an entity in said application context, wherein the entity called said first remote kernel service;
- and
- after aborting said entity, launching, at said application context, a handler indicated by a second signal action vector file associated with said application context, wherein the launched handler is identified by an entry in said second signal action vector file corresponding to the first signal sent from said application context to said first server context.
4 more elements
A computer system comprising:
- programmable circuits;
- and
- a computer readable storage medium storing instructions that upon execution by the programmable circuits cause the programmable circuits to:
- receive a remote procedure call at a server context, said remote procedure call representing a request to employ a kernel service in said server context on behalf of a calling entity associated with an application context that is different from said server context;
- in response to the remote procedure call, establish a first signal action vector associated with said server context, wherein said first signal action vector has plural action codes corresponding to plural respective signals, wherein multiple ones of the plural action codes correspond to pseudo-handlers, and wherein each of said pseudo-handlers mimics a handler address without corresponding to a meaningful address;
- receive, at said server context from said application context, a first signal;
- in response to said first signal, consult said first signal action vector;
- abort a wait state of said kernel service if said first signal corresponds to a particular one of the pseudo-handlers in said first signal action vector;
- attempt to launch the particular pseudo-handler after the aborting, wherein no real handler is launched at said server context as a result of the attempting;
- after the aborting of the wait state of said kernel service, abort the calling entity associated with said application context;
- and
- after aborting said calling entity, launch, at said application context, a handler indicated by a second signal action vector that is associated with said application context, wherein the launched handler is identified by an entry in said second signal action vector corresponding to said first signal sent from said application context to said server context.
9 more elements
An article of manufacture comprising a computer readable storage medium storing instructions that upon execution cause a computer system to:
- receive a remote procedure call at a server context, said remote procedure call representing a request to employ a kernel service in said server context on behalf of a calling entity associated with an application context that is different from said server context;
- in response to the remote procedure call, establish a first signal action vector associated with said server context, wherein said first signal action vector has plural action codes corresponding to plural respective signals, wherein multiple ones of the plural action codes correspond to pseudo-handlers, and wherein each of said pseudo-handlers mimics a handler address without corresponding to a meaningful address;
- receive, at said server context from said application context, a first signal;
- in response to said first signal, consult said first signal action vector;
- abort said kernel service if said first signal corresponds to a particular one of the pseudo-handlers in said first signal action vector;
- attempt to launch the particular pseudo-handler after the aborting, wherein no real handler is launched at said server context as a result of the attempting;
- after aborting said kernel service, abort the calling entity associated with said application context;
- and
- after aborting said calling entity, launch, at said application context, a handler indicated by a second signal action vector that is associated with said application context, wherein the launched handler is identified by an entry in said second signal action vector corresponding to said first signal sent from said application context to said server context.
6 more elements
A computer system comprising:
- programmable circuits;
- and
- a computer readable storage medium storing instructions that upon execution by the programmable circuits cause the programmable circuits to:
- receive a remote procedure call at a server context, said remote procedure call representing a request to employ a kernel service in said server context on behalf of a calling entity associated with an application context that is different from said server context;
- in response to the remote procedure call, establish a first signal action vector associated with said server context, wherein said first signal action vector has plural action codes corresponding to plural respective signals, wherein multiple ones of the plural action codes correspond to pseudo-handlers, and wherein each of said pseudo-handlers mimics a handler address without corresponding to a meaningful address;
- receive, at said server context from said application context, a first signal;
- in response to said first signal, consult said first signal action vector;
- abort a wait state of said kernel service if said first signal corresponds to a particular one of the pseudo-handlers in said first signal action vector;
- receive a signal at said application context;
- and
- send said first signal from said application context to said server context in response to receiving the signal at said application context, wherein said second signal has a signal number that is the same as a signal number of the signal received at said application context.
8 more elements
Dependencies are inferred from the claim text.