mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid.aziz@hp.com>
To: Myron Stowe <myron.stowe@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-kernel@vger.kernel.org, bhelgaas@google.com,
	linux-pci@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] Disable Bus Master on PCI device shutdown
Date: Wed, 06 Jun 2012 17:03:59 -0600	[thread overview]
Message-ID: <1339023839.25761.764.camel@lyra> (raw)
In-Reply-To: <CAL-B5D3Wda7TV_NBJWEbzJm=0eCs=b-wgGLdJUFRTwP_ewXGGg@mail.gmail.com>

On Wed, 2012-06-06 at 14:16 -0600, Myron Stowe wrote:
> Hay Khalid,
> 
> I've been following this discussion but still do not understand what the
> perceived correct fix is for the situation you were originally trying to
> circumvent - namely, stopping NIC devices from triggering DMA activity
> upon receipt of an incoming packet.
> 
> From the discussion it sounds like a driver, upon shutdown, can end
> all active I/O
> clearing the I/O queue, and also (?) shut down its DMA engine, and may
> also go as far as disabling the Bus Master bit.
> 
> What was occurring in the original issue - was the driver in question not
> shutting down its DMA engine for some, possibly valid, reason?
> 
> Thanks,
>  Myron

Hi Myron,

The last driver issue with kexec was reported on kexec mailing list in
July of last year and that was with qla driver. From what H Peter Anvin
described, the driver left DMA engine running.

For the issue I found on an ia64 platform, it was so many years ago that
you are now taxing my old and decrepit memory :) I am digging through
old internal bug reports and will let you know once I find that original
bug report.

====================================================================
Khalid Aziz                                         Unix Systems Lab
(970)898-9214                                        Hewlett-Packard
khalid.aziz@hp.com                                  Fort Collins, CO


  reply	other threads:[~2012-06-06 23:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 19:00 Khalid Aziz
2012-05-03 23:52 ` Bjorn Helgaas
2012-05-04 17:15   ` Bjorn Helgaas
2012-06-06 13:50 ` Matthew Garrett
2012-06-06 16:17   ` Khalid Aziz
2012-06-06 16:27     ` Matthew Garrett
2012-06-06 17:32       ` Khalid Aziz
2012-06-06 17:42         ` Matthew Garrett
2012-06-06 18:07           ` Khalid Aziz
2012-06-06 19:42             ` Eric W. Biederman
2012-06-06 20:09               ` Matthew Garrett
2012-06-07 17:43                 ` Khalid Aziz
2012-06-07 14:21               ` Khalid Aziz
2012-06-06 20:16             ` Myron Stowe
2012-06-06 23:03               ` Khalid Aziz [this message]
2012-06-06 23:18                 ` Myron Stowe
2012-06-06 20:50   ` Alan Cox
2012-06-07 17:07     ` Andi Kleen
2012-06-07 17:13       ` Alan Cox
2012-06-07 17:36       ` Khalid Aziz
2012-06-07 17:08   ` Andi Kleen

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=1339023839.25761.764.camel@lyra \
    --to=khalid.aziz@hp.com \
    --cc=bhelgaas@google.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=myron.stowe@gmail.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®