From: Paul Mackerras <paulus@samba.org>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Ravinandan Arakali <Ravinandan.Arakali@neterion.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
leonid.grossman@neterion.com, ananda.raju@neterion.com,
rapuru.sriram@neterion.com
Subject: Re: [PATCH 2.6.16.18] MSI: Proposed fix for MSI/MSI-X load failure
Date: Sat, 3 Jun 2006 12:09:05 +1000 [thread overview]
Message-ID: <17536.61249.962979.937698@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060602145512.A13024@unix-os.sc.intel.com>
Rajesh Shah writes:
> The current MSI code actually does this deliberately, not by
> accident. It's got a lot of complex code to track devices and
> vectors and make sure an enable_msi -> disable -> enable sequence
> gives a driver the same vector. It also has policies about
> reserving vectors based on potential hotplug activity etc.
> Frankly, I've never understood the need for such policies, and
> am in the process of removing all of them.
Good. We will not be able to support a policy of giving the driver
the same vector across an enable_msi/disable/enable sequence on IBM
System p machines (64-bit PowerPC), because the firmware controls the
MSI allocation, and it doesn't give us the necessary guarantees.
Paul.
next prev parent reply other threads:[~2006-06-03 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 19:21 [PATCH 2.6.16.18] MSI: Proposed fix for MSI/MSI-X load failure Ravinandan Arakali
2006-06-02 21:55 ` Rajesh Shah
2006-06-03 2:09 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-02 22:05 Ravinandan Arakali
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17536.61249.962979.937698@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=Ravinandan.Arakali@neterion.com \
--cc=ananda.raju@neterion.com \
--cc=leonid.grossman@neterion.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rajesh.shah@intel.com \
--cc=rapuru.sriram@neterion.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox