From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Greg KH <gregkh@suse.de>
Cc: Rafa? Bilski <rafalbilski@interia.pl>,
linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] (Longhaul 1/5) PCI: Protect bus master DMA from Longhaul by rw semaphores
Date: Wed, 28 Jun 2006 19:03:00 +0100 [thread overview]
Message-ID: <1151517780.15166.52.camel@localhost.localdomain> (raw)
In-Reply-To: <20060628173448.GA2371@suse.de>
Ar Mer, 2006-06-28 am 10:34 -0700, ysgrifennodd Greg KH:
> Eeek! You mean the longhaul driver can change the frequency of the PCI
> bus? Oh, that's a recipe for disaster...
Not as I understand the docs, and that would be unfixable. Some C3
setups do however appear to "fall off the bus" during transitions which
means if BMDMA is active things get confused.
I am still not clear if this is just cache corruption through us not
listening or whether we genuinely need to halt. In the former case
flushing and disabling the CPU caches ought to be sufficient.
Alan
next prev parent reply other threads:[~2006-06-28 17:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 13:56 [PATCH] (Longhaul 1/5) PCI: Protect bus master DMA from Longhaul by rw semaphores Rafał Bilski
2006-06-28 17:34 ` Greg KH
2006-06-28 18:03 ` Alan Cox [this message]
2006-06-28 18:00 ` Jeremy Fitzhardinge
2006-06-28 18:10 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 18:25 Rafał Bilski
2006-06-29 11:37 ` Alan Cox
2006-06-29 12:03 ` Bart Hartgers
2006-06-29 12:50 ` Rafał Bilski
2006-06-29 14:12 ` Rafał Bilski
2006-06-29 15:01 ` Bart Hartgers
2006-06-29 15:40 ` Rafał Bilski
2006-06-30 10:46 ` Bart Hartgers
2006-06-29 15:16 ` Bart Hartgers
2006-06-29 15:55 ` Alan Cox
2006-06-29 18:54 ` Rafał Bilski
2006-06-29 15:52 ` Alan Cox
[not found] <fa.lpmuYQxc6OV7Bh11JMM/FzqVWyY@ifi.uio.no>
2006-06-29 23:17 ` Robert Hancock
2006-07-01 18:02 ` Rafał Bilski
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=1151517780.15166.52.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rafalbilski@interia.pl \
/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