The attached diff makes the spec_node table implementation private
to sys/miscfs/specfs/spec_vnops.c. To retrieve a spec_node, two new
lookup functions (by device or by mount) are implemented. Both return
a referenced vnode, for an opened block device the opened vnode is
returned so further diagn
In article <79da22d1-8cc4-4354-ade3-99820650e...@eis.cs.tu-bs.de>,
J. Hannken-Illjes wrote:
>-=-=-=-=-=-
>
>The attached diff makes the spec_node table implementation private
>to sys/miscfs/specfs/spec_vnops.c. To retrieve a spec_node, two new
>lookup functions (by device or by mount) are impleme
The xcall(9) manual page says,
xcall provides a mechanism for making ``low priority'' cross calls. The
function to be executed runs on the remote CPU within a thread context,
and not from a software interrupt, so it can ensure that it is not inter-
rupting other code running o
"J. Hannken-Illjes" wrote:
> The attached diff makes the spec_node table implementation private
> to sys/miscfs/specfs/spec_vnops.c. To retrieve a spec_node, two new
> lookup functions (by device or by mount) are implemented. Both return
> a referenced vnode, for an opened block device the opene
David Young wrote:
> I take that last sentence to mean that a low-priority cross call *may*
> preempt a thread on the remote CPU. Is that correct?
>
> In other words, can we rephrase that, "A low-priority cross call may
> preempt a thread running on the remote CPU unless preemption is disabled
>
