All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: David Brownell <david-b@pacbell.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Pete Zaitcev <zaitcev@redhat.com>,
	johannes@erdfelt.com, rmk@arm.linux.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: pci_pool_free from IRQ
Date: Wed, 9 May 2001 14:30:20 -0400	[thread overview]
Message-ID: <20010509143020.A22522@devserv.devel.redhat.com> (raw)
In-Reply-To: <200105082108.f48L8X1154536@saturn.cs.uml.edu> <E14xFD5-0000hh-00@the-village.bc.nu> <15096.27479.707679.544048@pizda.ninka.net> <050701c0d80f$8f876ca0$6800000a@brownell.org> <15096.38109.228916.621891@pizda.ninka.net>
In-Reply-To: <15096.38109.228916.621891@pizda.ninka.net>; from davem@redhat.com on Tue, May 08, 2001 at 05:52:45PM -0700

> From: "David S. Miller" <davem@redhat.com>
> Date: Tue, 8 May 2001 17:52:45 -0700 (PDT)

> Ummm... What Alan's saying is:
> 
> 1) Whatever driver is trying to shut down from IRQ context
>    is broken must be fixed.  pci_pool is fine.
> 
> 2) The Documentation/ files which suggest that such device
>    removal from IRQs is "OK" must be fixed because it is not
>    "OK" to handle device removal from IRQ context.
> 
> So Pete's change is not needed.  A fix for the documentation and
> broken drivers is needed instead.

David, I do not follow your logic here, sorry.

I wrote that a path exists from a function that is legal in
interrupt context (pci_pool_free) into a function that is
not legal in interrupt context (pci_free_consistent).
The change breaks that connection. Note that pci_pool_free
is called when driver operates normally.

When you write "fix documentation and broken drivers", you talk
about a fix for a part that processes PCI remove. This is entirely
fine by me. But I was talking about a regular interrupt procession
in driver. A fix in pci remove does not fix regular processing.

-- Pete

  parent reply	other threads:[~2001-05-09 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08 21:01 pci_pool_free from IRQ Pete Zaitcev
2001-05-08 21:08 ` Albert D. Cahalan
2001-05-08 21:39   ` Alan Cox
2001-05-08 21:55     ` David S. Miller
2001-05-08 22:38       ` David Brownell
2001-05-09  0:52         ` David S. Miller
2001-05-09  3:09           ` David Brownell
2001-05-09 18:30           ` Pete Zaitcev [this message]
2001-05-09 19:27             ` David S. Miller
2001-05-10 20:05               ` Pete Zaitcev
2001-05-11 17:37                 ` David Brownell

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=20010509143020.A22522@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=acahalan@cs.uml.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=johannes@erdfelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.