From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
"Williams, Mitch A" <mitch.a.williams@intel.com>
Subject: Re: [PATCH] msi: Immediately mask and unmask msi-x irqs.
Date: Tue, 3 Apr 2007 13:57:25 -0700 [thread overview]
Message-ID: <20070403205725.GD15704@linux-os.sc.intel.com> (raw)
In-Reply-To: <m18xd9ckn4.fsf@ebiederm.dsl.xmission.com>
On Tue, Apr 03, 2007 at 01:39:43PM -0600, Eric W. Biederman wrote:
> "Siddha, Suresh B" <suresh.b.siddha@intel.com> writes:
>
> Further now that we cache the msi message that read_msi_msg should go
> away and we should use the cached version from the msi_desc.
Ok. Then this patch is a must.
> > Don't we need the flush for the PCI_CAP_ID_MSI case aswell.
>
> At least the 3.0 pci spec does not allow pci configuration access to
> be posted. So unless we find some hardware that actually does post
> pci configuration writes we should be ok.
ok. Thanks.
prev parent reply other threads:[~2007-04-03 20:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 18:54 [PATCH 2.6.21-rc5] Flush MSI-X table writes (rev 3) Mitch Williams
2007-03-30 19:04 ` Eric W. Biederman
2007-03-30 19:47 ` Andrew Morton
2007-03-30 19:49 ` Greg KH
2007-03-30 20:00 ` Andrew Morton
2007-03-30 20:10 ` Greg KH
2007-03-30 20:21 ` Williams, Mitch A
2007-03-30 20:24 ` Greg KH
2007-03-30 20:26 ` Eric W. Biederman
2007-03-30 20:49 ` Williams, Mitch A
2007-03-30 20:56 ` Chuck Ebbert
2007-03-30 21:05 ` Eric W. Biederman
2007-04-03 7:41 ` [PATCH] msi: Immediately mask and unmask msi-x irqs Eric W. Biederman
2007-04-03 17:24 ` Williams, Mitch A
2007-04-03 18:52 ` Siddha, Suresh B
2007-04-03 19:39 ` Eric W. Biederman
2007-04-03 20:57 ` Siddha, Suresh B [this message]
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=20070403205725.GD15704@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mitch.a.williams@intel.com \
--cc=torvalds@linux-foundation.org \
/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