public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Greg KH <gregkh@suse.de>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz,
	pcihpd-discuss@lists.sourceforge.net
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Thu, 09 Mar 2006 13:01:00 +0900	[thread overview]
Message-ID: <440FA87C.7000504@jp.fujitsu.com> (raw)
In-Reply-To: <20060306223545.GA20885@kroah.com>

Greg KH wrote:
> Here's a summary of the current state of the Linux PCI and PCI Hotplug
> subsystems as of 2.6.16-rc5
> 
> If the information in here is incorrect, or anyone knows of any
> outstanding issues not listed here, please let me know.
> 
> List of outstanding regressions from 2.6.15:
> 	- none known.
> 
> List of outstanding regressions from older kernel versions:
> 	- some cardbus users still have issues with the change to the
> 	  PCI resource allocation stuff.
> 	  http://bugzilla.kernel.org/show_bug.cgi?id=5736 shows this
> 	  issue, but seems to be stalled for now :(
> 
> Here is a list of the current outstanding bugs for the PCI subsystem as
> tracked at bugzilla.kernel.org.  If anyone can help out with any of
> these, please add information to the bug reports.
> 
>  * 5736 [greg@kroah.com] - pci broken on PIIX/ICH laptop (CARDBUS_IO_SIZE
> 	too small?).
> 
> 
> Future stuff:
>   Wow, for a subsystem that no one cared about for a long time (PCI
>   Hotplug) all of a sudden we have so many patches floating around that
>   it is difficult to handle all of them.  If you are interested in the
>   changes in this area that will be coming in 2.6.17, please see my
>   quilt tree at
>   http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
> 
>   Summary of the changes found there are:
> 	- shpchp driver reworks that fix issues and handle the module
> 	  being able to be unloaded properly
> 	- acpiphp driver changes to try to be able to work properly for
> 	  laptop docking stations.  There is still remaining work to do
> 	  in this area.
> 	- We have unstable patches to handle multi-domain PCI busses for
> 	  i386 and x86 arches in this tree.  Unfortunately they still
> 	  seem to break NUMA and other random boxes, so they will not be
> 	  heading for mainline any time soon.  If anyone has one of
> 	  these boxes and wishes to work on this, please let me know.
> 	- MSI cleanups and fixes to get things to work on ia64.
> 	- Other minor PCI and PCI bug fixes.
> 
> 
> I still have a few outstanding patches in my TODO queue that I have not
> applied to my quilt tree.  These patches do the following:
> 	- boot parameter to disable MSI
> 	- various PCI quirks added
> 	- remove PCI_LEGACY_PROC functionality.
> 	- more acpiphp driver fixes.
> 	- kzalloc cleanup for drivers/pci
> 	- cpqphp driver cleanups as found by the Coverty checker.
> 	- other minor things.
> 
> I hope to get to these by the end of the week, depending on other 2.6.16
> stabilization work.  If you don't hear back from me by then, and you
> have sent me a PCI or PCI Hotplug patch, please resend it and poke me
> about it.
> 
> There are no new PCI driver API changes are pending that I am aware of.
> 
> Was this summary useful for people?  Anything that I should add to it?
> 

Could you please add "PCI legacy I/O port free driver"
(http://www.ussg.iu.edu/hypermail/linux/kernel/0603.0/1923.html)
to Future stuff? I hope the set of patches would be tested on -mm tree
for a while.

Thanks,
Kenji Kaneshige


  parent reply	other threads:[~2006-03-09  4:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:35 State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00   ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50   ` Greg KH
2006-03-08 23:03     ` Linus Torvalds
2006-03-08 23:18       ` Greg KH
2006-03-08 23:30         ` Linus Torvalds
2006-03-09 18:40           ` Tomasz Torcz
2006-03-09 19:49             ` Linus Torvalds
2006-03-09 20:10               ` Ben Collins
2006-03-09 20:24                 ` Linus Torvalds
2006-03-15 16:03                   ` Ben Collins
2006-03-09 20:52                 ` Lee Revell
2006-03-09 21:06                   ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47                     ` Lee Revell
2006-03-09 21:07                   ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37               ` Arjan van de Ven
2006-03-09 20:46                 ` Dave Jones
2006-03-09 21:15                   ` Arjan van de Ven
2006-03-08 23:29       ` Andrew Morton
2006-03-08 23:45         ` Dave Hansen
2006-03-08 23:52           ` Andrew Morton
2006-03-09 10:24         ` Martin MOKREJŠ
2006-03-08 23:05     ` Adrian Bunk
2006-03-08 23:18       ` Lee Revell
2006-03-08 23:23         ` Greg KH
2006-03-08 23:34           ` Lee Revell
2006-03-08 23:40             ` Greg KH
2006-03-09  0:03               ` Lee Revell
2006-03-08 23:21       ` Greg KH
2006-03-09  4:01 ` Kenji Kaneshige [this message]
2006-03-09  5:34   ` Greg KH
2006-03-09  5:11 ` Lee Revell

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=440FA87C.7000504@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=torvalds@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