[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110825181912.GB27183@redhat.com>
Date: Thu, 25 Aug 2011 21:19:12 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jan Kiszka <jan.kiszka@...mens.com>
Cc: Brian King <brking@...ux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Alex Williamson <alex.williamson@...hat.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Matthew Wilcox <matthew@....cx>
Subject: Re: Broken pci_block_user_cfg_access interface
On Thu, Aug 25, 2011 at 03:06:01PM +0200, Jan Kiszka wrote:
> > I took a look at the sysfs triggered pci reset function and don't see any way
> > that the controlling device driver ever gets to be involved in this reset.
> > If code outside the ipr driver were to reset the adapter, the adapter firmware
> > would be left in an uninitialized state and until scsi core starts timing
> > out ops and driving EH, the card would be unusable. I can't imagine the
> > ipr driver is unique in this.
>
> Right, that's why a PCI core service is needed for coordination.
>
> Jan
But why do we want to trigger reset through sysfs while the
driver runs?
> --
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists