From: Patrick Jefferson <patrick.jefferson@hp.com>
To: greg@kroah.com
Cc: ink@jurassic.park.msu.ru, gregkh@suse.de,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] PCI: fix MMIO addressing collisions
Date: Wed, 24 May 2006 21:43:31 +0000 [thread overview]
Message-ID: <4474D383.4030506@hp.com> (raw)
In-Reply-To: <20060523224718.GA31629@kroah.com>
Greg KH wrote:
> On Wed, May 24, 2006 at 02:06:54AM +0400, Ivan Kokshaysky wrote:
>
>>On Tue, May 23, 2006 at 12:28:10PM +0000, Patrick Jefferson wrote:
>>
>>>Clearing PCI Command bits fixes machine halts observed during sizing
>>>seqences using MMIO cycles. Clearing the bits is suggested by an
>>>implementation note in the PCI spec.
>>
>>The patch is not acceptable. This was discussed back in 2002:
>>
>> http://www.uwsg.iu.edu/hypermail/linux/kernel/0212.2/index.html#978
>
>
> I agree, it's not going to be accepted.
>
> Patrick, are you trying to solve the same thing that Grant was back in
> 2002? Why do you feel this patch is necessary?
No. The problem is similar, involving colliding addresses, but
critically different. Sizing a device's BAR via memory-mapped
configuration space accesses will do spectacular things when the size,
say E0000000, unforeseeably equals the mapped config space address, like
E0000000. The Memory bit in the PCI Command register must be cleared.
Either a) some other specific sequence exists for safe sizing,
Or b) disabling memory decoding by the device must be allowed, at
minimum, as a special case,
Or c) a switch from MMCONFIG to CF8/CFC and back again should be used
when sizing,
Or d) the resulting machine crash is acceptable during linux boot.
The patch, since it addresses d), is necessary unless b) or c) are
feasible, or a) exists.
Any suggestions would be appreciated.
Thanks,
Patrick
prev parent reply other threads:[~2006-05-24 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 12:28 [PATCH] PCI: fix MMIO addressing collisions Patrick Jefferson
2006-05-23 22:06 ` Ivan Kokshaysky
2006-05-23 22:47 ` Greg KH
2006-05-24 21:43 ` Patrick Jefferson [this message]
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=4474D383.4030506@hp.com \
--to=patrick.jefferson@hp.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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