public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Biro <rossb@google.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode
Date: Wed, 06 Apr 2005 08:47:11 -0400	[thread overview]
Message-ID: <4253DA4F.2020707@google.com> (raw)
In-Reply-To: <4252FAE6.8080107@osdl.org>

Randy.Dunlap wrote:
> 
> 
> Is this related (or could it be -- or should it be) at all to the
> current discussion on the linux-pci mailing list
> linux-pci@atrey.karlin.mff.cuni.cz) about "PCI Error Recovery
> API Proposal" ?


I'm not familiar with the proposal, but this is not related to error 
recovery since master aborts are a way of life on the PCI bus and things 
just need to deal.  The only question is how.

> 
>> the master.  This can only happen when the system is heavily loaded.
> 
> 
> or a PCI device isn't playing nicely?

Yes, but at least then you could blame the device in that case.

[ style and grammar comments noted ]

One thing I did fail to mention in my original post is that all of this 
could be done by rc scripts from user space, but that seems unclean to me.

	Ross

  reply	other threads:[~2005-04-06 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 19:33 [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode Ross Biro
2005-04-05 20:53 ` Randy.Dunlap
2005-04-06 12:47   ` Ross Biro [this message]
2005-04-06 20:44 ` Daniel Egger
2005-04-10 13:29 ` Andi Kleen
     [not found]   ` <8783be66050412075218b2b0b0@mail.gmail.com>
2005-04-13 18:37     ` Andi Kleen
2005-04-13 23:00       ` Ross Biro
2005-04-13 23:28         ` Dave Jones
2005-04-14 17:25           ` Ross Biro
2005-04-14 17:34             ` Tim Hockin
2005-04-14 18:02               ` Andi Kleen
2005-04-14 18:33                 ` Dave Jones
2005-04-14 19:14             ` Daniel Egger

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=4253DA4F.2020707@google.com \
    --to=rossb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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