linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	grundler@parisc-linux.org, mingo@elte.hu, tglx@linutronix.de,
	jgarzik@pobox.com, linux-ide@vger.kernel.org,
	suresh.b.siddha@intel.com, jbarnes@virtuousgeek.org,
	rdunlap@xenotime.net, mtk.manpages@gmail.com,
	Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [PATCH] PCI: Add support for multiple MSI
Date: Sat, 12 Jul 2008 13:45:42 +1000	[thread overview]
Message-ID: <1215834342.7549.151.camel@pasglop> (raw)
In-Reply-To: <487719AC.9070609@jp.fujitsu.com>

On Fri, 2008-07-11 at 17:28 +0900, Hidetoshi Seto wrote:
> Hi,
> 
> First of all, it seems that mask/unmask of MSI has problems.
>  - Per-vector masking is optional for MSI, so I think that allocating
>    multiple messages for a function without masking capability would be
>    not good idea, since all vector in the block will be masked/unmasked
>    at once without any agreement.
>  - Even if the function supports per-vector masking, current
>    mask/unmask_msi_irq() functions assume that MSI uses only one vector,
>    therefore they only set/unset the first bit of the maskbits which
>    for the first vector of the block.  The bits for other vectors are
>    initialized as 'masked' but no one unmask them.

I tend to think we should just do soft-masking anyway for MSI... better
than whacking config space.

Ben


  parent reply	other threads:[~2008-07-12  3:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  0:57 Multiple MSI, take 3 Matthew Wilcox
2008-07-11  0:59 ` [PATCH] PCI MSI: Replace 'type' with 'is_msix' Matthew Wilcox
2008-07-11  0:59 ` [PATCH] PCI: Add support for multiple MSI Matthew Wilcox
2008-07-11  8:28   ` Hidetoshi Seto
2008-07-11  9:45     ` Matthew Wilcox
2008-07-12  3:45     ` Benjamin Herrenschmidt [this message]
2008-07-11  1:00 ` [PATCH] Rewrite MSI-HOWTO Matthew Wilcox
2008-09-26  6:42   ` Grant Grundler
2008-07-11  1:00 ` [PATCH] AHCI: Request multiple MSIs Matthew Wilcox
2008-07-11  1:00 ` [PATCH] x86-64: Support for " Matthew Wilcox
2008-07-11  4:50   ` Kenji Kaneshige
2008-07-11  8:50     ` Matthew Wilcox
2008-07-14  1:08       ` Kenji Kaneshige
2008-07-11 10:06 ` Multiple MSI, take 3 Eric W. Biederman
2008-07-11 10:23   ` Matthew Wilcox
2008-07-11 10:32     ` David Miller
2008-07-11 10:41       ` Matthew Wilcox
2008-07-11 11:05     ` Eric W. Biederman
2008-07-11 11:34     ` Eric W. Biederman
2008-07-11 12:17       ` Matthew Wilcox
2008-07-11 15:10         ` Matthew Wilcox
2008-07-11 21:59   ` Suresh Siddha
2008-07-11 22:59     ` Eric W. Biederman
2008-07-11 23:15       ` Suresh Siddha
2008-07-11 23:59         ` Eric W. Biederman
2008-07-12  3:52       ` Benjamin Herrenschmidt
2008-07-12  4:41         ` Eric W. Biederman
2008-07-12  7:36           ` Benjamin Herrenschmidt
2008-07-13 22:30             ` Eric W. Biederman
2008-07-13 22:44               ` Benjamin Herrenschmidt
2008-07-13 23:29                 ` Eric W. Biederman
2008-07-14  0:17                   ` Benjamin Herrenschmidt
2008-07-14  0:44                     ` David Miller
2008-07-14  2:03                       ` Eric W. Biederman
2008-07-14  3:19                         ` David Miller
2008-09-26  5:30 ` Jike Song
2008-09-27 19:04   ` Matthew Wilcox

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=1215834342.7549.151.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@gmail.com \
    --cc=rdunlap@xenotime.net \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=willy@linux.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;
as well as URLs for NNTP newsgroup(s).