[RFC/PATCH 0/16] Ops based MSI Implementation
Eric W. Biederman
ebiederm at xmission.com
Mon Jan 29 16:46:15 EST 2007
David Miller <davem at davemloft.net> writes:
> From: Benjamin Herrenschmidt <benh at kernel.crashing.org>
> Date: Mon, 29 Jan 2007 11:58:21 +1100
>> > There are specific calls into the sparc64 hypervisor for MSI vs. MSI-X
>> > configuration operations. So a type is necessary.
>> BTW. Do you have some pointers to documentation on those sparc64
>> interfaces ? I'd like to have a look as we might still try to change
>> some of our approach to match some of Eric's whishes, I want to make
>> sure I'm not going somewhere that will not work for sparc...
>> For example, I'd like to know if sparc64 HV is indeed like IBM, that is
>> a single HV call does the complete setup, or if you still have some
>> level of manual config space access to do.
> I just started reading those docs right now in fact :-)
> The sparc64 hypervisor manual is at:
> Click on "UltraSPARC T1 Hypervisor API Specification" near
> the bottom of the page. The MSI bits are in section 21.4 on
> page 105.
> BTW, I like how Banjamin is being constructive by expressing
> interest in how sparc64's hypervisor works instead of Eric's
> seeming non-interest in how or why RTAS or sparc64 work the
> way that they do :-)
My problem is that I have been asking about RTAS for six months
since before OLS. Slowly the information has trickled in. My first
impression is boy is that weird. My second impression after getting
the full details was huh? That is ridiculous, simply because they
don't need to do a
You wound up posting this sparc link before I could ask about it.
Sorry for taking a couple of hours to respond but I'm not always in
front of my computer, and to some extent responding to everything
was becoming counter productive.
More information about the Linuxppc-dev