Searched hist:"76148 df19cbd5437dc5358408a58c7cc6366ecf4" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/misc/sgi-gru/ |
| H A D | gru_instructions.h | diff 76148df19cbd5437dc5358408a58c7cc6366ecf4 Tue Dec 15 18:48:21 CST 2009 Jack Steiner <steiner@sgi.com> gru: send cross partition interrupts using the gru
GRU Message queue instructions are used to deliver messages to other SSIs
within the numalink domain. In most cases, a single GRU mesq instruction
will deliver both the message AND an interrupt to notify the other SSI
that a messsage is present. In some cases, however, the interrupt must be
sent explicitly.
To improve resilency, the GRU driver should send these explicit interrupts
using the GRU to write the remote chipset register. Current code sends
the interrupt using a cpu instruction to write the chipset register.
Signed-off-by: Jack Steiner <steiner@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|
| H A D | grukservices.c | diff 76148df19cbd5437dc5358408a58c7cc6366ecf4 Tue Dec 15 18:48:21 CST 2009 Jack Steiner <steiner@sgi.com> gru: send cross partition interrupts using the gru
GRU Message queue instructions are used to deliver messages to other SSIs
within the numalink domain. In most cases, a single GRU mesq instruction
will deliver both the message AND an interrupt to notify the other SSI
that a messsage is present. In some cases, however, the interrupt must be
sent explicitly.
To improve resilency, the GRU driver should send these explicit interrupts
using the GRU to write the remote chipset register. Current code sends
the interrupt using a cpu instruction to write the chipset register.
Signed-off-by: Jack Steiner <steiner@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
|