mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Manu Abraham" <abraham.manu@gmail.com>
To: "Roland Dreier" <rdreier@cisco.com>
Cc: "Leech, Christopher" <christopher.leech@intel.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
	"Nelson, Shannon" <shannon.nelson@intel.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, jeff@garzik.org, "Williams,
	Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH 5/7] I/OAT: Add support for MSI and MSI-X
Date: Sat, 21 Jul 2007 01:49:07 +0400	[thread overview]
Message-ID: <1a297b360707201449q73637216w81859b01ab3e5b7e@mail.gmail.com> (raw)
In-Reply-To: <adaveceah8l.fsf@cisco.com>

On 7/21/07, Roland Dreier <rdreier@cisco.com> wrote:
>  > In a case where you have a device that which supports MSI-X (multiple
>  > interrupts) but the device in default is in MSI mode, ie some
>  > configuration change is needed on the device. In such a case, how
>  > would one handle between MSI-X and MSI ?
>  >
>  > ie the device initially doesn't support MSI-X
>
> I don't understand the question really.  Does the PCI spec even allow
> a device to be in MSI mode by default?  Surely the OS must initialize
> the address/message before the device can generate an MSI?
>

Sorry for being not clear. What i was asking is thus:

A device that has legacy interrupts and MSI-X. I was thinking that if
MSI-X failed one should fall back to MSI mode (single message), that's
what i was assuming.

In such a case, i do enable MSI-X mode on the device, when the request
for 2 ^ n  number of messages (where messages can be a max of 32), If
the request fails one falls into a single message mode, ie MSI ?


> What device do you have in mind?


The device that i have in mind is a SAA7160.


> I guess the interesting case is a
> PCIe device that supports MSI and MSI-X but not legacy interrupts.
> However I would assume such a device would come up with both MSI and
> MSI-X disabled.
>
>  - R.
>

  reply	other threads:[~2007-07-20 21:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20  0:44 [PATCH 0/7] I/OAT: Add support for DCA - Direct Cache Access Shannon Nelson
2007-07-20  0:44 ` [PATCH 1/7] I/OAT: New device ids Shannon Nelson
2007-07-20  0:49   ` David Miller
2007-07-20  0:44 ` [PATCH 2/7] I/OAT: Rename the source file Shannon Nelson
2007-07-20  0:49   ` David Miller
2007-07-20  0:45 ` [PATCH 3/7] I/OAT: code cleanup from checkpatch output Shannon Nelson
2007-07-20  0:49   ` David Miller
2007-07-20  0:45 ` [PATCH 4/7] I/OAT: Split PCI startup from DMA handling code Shannon Nelson
2007-07-20  0:50   ` David Miller
2007-07-20 10:53   ` Andrey Panin
2007-07-20 16:33     ` Nelson, Shannon
2007-07-20  0:45 ` [PATCH 5/7] I/OAT: Add support for MSI and MSI-X Shannon Nelson
2007-07-20  0:51   ` David Miller
2007-07-20 17:43   ` Roland Dreier
2007-07-20 18:09     ` Waskiewicz Jr, Peter P
2007-07-20 19:05       ` Roland Dreier
2007-07-20 19:19         ` Waskiewicz Jr, Peter P
2007-07-20 19:49           ` Roland Dreier
2007-07-20 21:10             ` Leech, Christopher
2007-07-20 21:21               ` Roland Dreier
2007-07-20 21:32                 ` Manu Abraham
2007-07-20 21:38                   ` Roland Dreier
2007-07-20 21:49                     ` Manu Abraham [this message]
2007-07-20 21:54                       ` Nelson, Shannon
2007-07-20 21:59                         ` Manu Abraham
2007-07-20 22:00                           ` Nelson, Shannon
2007-07-20 22:07                           ` Waskiewicz Jr, Peter P
2007-07-20 21:13             ` Nelson, Shannon
2007-07-20  0:45 ` [PATCH 6/7] DCA: Add Direct Cache Access driver Shannon Nelson
2007-07-20  0:52   ` David Miller
2007-07-20 16:35     ` Nelson, Shannon
2007-07-20  0:45 ` [PATCH 7/7] I/OAT: Add DCA services Shannon Nelson
2007-07-20  0:52   ` David Miller

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=1a297b360707201449q73637216w81859b01ab3e5b7e@mail.gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=christopher.leech@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=rdreier@cisco.com \
    --cc=shannon.nelson@intel.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

all inboxes | Powered by JetHome®