From: ebiederm@xmission.com (Eric W. Biederman)
To: Grant Grundler <iod00d@hp.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-ia64@vger.kernel.org, Jesse Barnes <jbarnes@engr.sgi.com>,
linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: [Fastboot] Re: [BROKEN PATCH] kexec for ia64
Date: Thu, 05 Aug 2004 02:14:55 +0000 [thread overview]
Message-ID: <m1hdri2uw0.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040804233335.GD548@cup.hp.com>
Grant Grundler <iod00d@hp.com> writes:
> On Wed, Aug 04, 2004 at 07:07:04AM -0600, Eric W. Biederman wrote:
> > Initially that patch
> > was targeted for a kernel without device_shutdown(), so I was
> > likely considering the old trick of running through all of the PCI
> > devices and disabling their bus master bit.
>
> Blindly disabling all PCI bus master bits will also kill VGA/serial
> console and any USB keyboard attached to the system.
VGA/serial console devices rarely need to do be bus masters so they
should be fine.
> I'll comment more on the "DMA is a Red Herring" when I can read
> more what it is about.
Most of those cases don't matter as the driver should always be calling
pci_set_master() on startup. Disabling all the bus master bits on ioxapics
in pci space would likely cripple the system. As they are architectural
hardware and rarely have pci drivers that can enable them.
In the general case it appears to be overkill, incorrect and
insufficient to disable bus mastering on all PCI devices. Which is
why device_shutdown() calls device specific code.
Eric
next prev parent reply other threads:[~2004-08-05 2:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 22:24 [BROKEN PATCH] kexec for ia64 Jesse Barnes
2004-07-26 22:36 ` Jesse Barnes
2004-07-26 23:09 ` David Mosberger
2004-07-26 23:30 ` David Mosberger
2004-07-26 23:34 ` Jesse Barnes
2004-07-26 23:42 ` David Mosberger
2004-07-27 8:24 ` Christian Hildner
2004-07-27 14:49 ` Jesse Barnes
2004-07-27 16:50 ` Luck, Tony
2004-07-30 22:55 ` Randy.Dunlap
2004-08-04 13:07 ` Eric W. Biederman
2004-08-04 16:24 ` Jesse Barnes
2004-08-04 23:33 ` Grant Grundler
2004-08-05 2:14 ` Eric W. Biederman [this message]
2004-08-05 15:39 ` [Fastboot] " Grant Grundler
2004-08-05 16:44 ` Eric W. Biederman
2004-08-05 19:44 ` Tolentino, Matthew E
2004-08-05 21:29 ` Eric W. Biederman
2004-08-05 22:15 ` Eric W. Biederman
2004-08-05 16:45 ` Luck, Tony
2004-08-05 17:05 ` [Fastboot] " Eric W. Biederman
2004-08-05 19:18 ` Khalid Aziz
2004-08-05 18:28 ` Grant Grundler
2004-08-05 18:56 ` Eric W. Biederman
2004-08-05 21:24 ` Grant Grundler
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=m1hdri2uw0.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=iod00d@hp.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--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