linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guo Chao <yan@linux.vnet.ibm.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Wei Yang <weiyang@linux.vnet.ibm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Yinghai Lu <yinghai@kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Gavin Shan <shangw@linux.vnet.ibm.com>,
	Jack Morgenstein <jackm@dev.mellanox.co.il>,
	Amir Vadai <amirv@mellanox.com>,
	Eugenia Emantayev <eugenia@mellanox.com>,
	talal@mellanox.com,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v7] PCI: Try best to allocate pref mmio 64bit above 4g
Date: Tue, 8 Apr 2014 16:22:40 +0800	[thread overview]
Message-ID: <20140408082240.GB3198@yanx> (raw)
In-Reply-To: <5343AB8B.5070409@mellanox.com>

On Tue, Apr 08, 2014 at 10:55:55AM +0300, Or Gerlitz wrote:
> On 08/04/2014 10:41, Wei Yang wrote:
> >>>So just to make sure we're on the same page -- fixing the bug is
> >>>carried out through netdev, e.g this 3.14-rc8
> >>>upstream commit 97a5221 "net/mlx4_core: pass
> >>>pci_device_id.driver_data to __mlx4_init_one during reset"
> >>>and now this one more fix which is under discussion
> >>>http://marc.info/?l=linux-pci&m=139675010015646&w=2, right?
> >No, this onehttp://marc.info/?l=linux-pci&m=139675010015646&w=2  is another
> >bug in mlx4 driver, missing a proper pci_dev_data in mlx4_init_one.
> >
> >The bug discussing in this thread is the driver "forget" to release the
> >"owner" during kexec. So this device couldn't be usded after kexec.
> >
> Can you guys please open a kernel.org bugzilla ticket, or better...
> work on a patch?
> 

It's already fixed in upstream.

commit 367d56f7b4d5ce61e883c64f81786c7a3ae88eea
Author: Gavin Shan <shangw@linux.vnet.ibm.com>
Date:   Tue Mar 4 15:35:20 2014 +0800

    net/mlx4: Support shutdown() interface


Thanks,
Guo Chao


  reply	other threads:[~2014-04-08  8:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE9FiQXzRQ9S0mwwb58R2icBTtHHJ6NMVFMaxEgtVNP9mZVjZw@mail.gmail.com>
2014-03-07 20:08 ` [PATCH v7] PCI: Try best to allocate pref mmio 64bit above 4g Yinghai Lu
2014-04-04 22:43   ` Bjorn Helgaas
2014-04-08  2:57     ` Guo Chao
2014-04-08  7:18       ` Or Gerlitz
2014-04-08  7:41         ` Wei Yang
2014-04-08  7:55           ` Or Gerlitz
2014-04-08  8:22             ` Guo Chao [this message]
2014-04-08 15:02       ` Bjorn Helgaas
2014-04-09  7:52         ` Guo Chao
2014-04-10 17:26           ` Bjorn Helgaas
2014-04-10 21:23             ` Benjamin Herrenschmidt
2014-04-15 11:54             ` Guo Chao
2014-04-16  0:09               ` Bjorn Helgaas
2014-04-16  2:29                 ` Yinghai Lu
2014-04-16 17:06                   ` Bjorn Helgaas
2014-04-17  3:30                     ` Yinghai Lu
2014-04-16  4:16                 ` Yinghai Lu
2014-04-16 17:10                   ` Bjorn Helgaas
2014-04-16  6:30                 ` Benjamin Herrenschmidt
2014-04-16  6:33                   ` Benjamin Herrenschmidt
2014-04-16 17:15                     ` Bjorn Helgaas
2014-04-16 22:11   ` Bjorn Helgaas
2014-04-17  4:20     ` Yinghai Lu
2014-04-17 16:35       ` Yinghai Lu
2014-04-17  4:23 ` [PATCH v8] " Yinghai Lu
2014-04-17 16:40 ` [PATCH v9] " Yinghai Lu
2014-05-20  3:45   ` [PATCH v10 0/4] PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources Bjorn Helgaas
2014-05-20  3:45     ` [PATCH v10 1/4] " Bjorn Helgaas
2014-05-20  3:45     ` [PATCH v10 2/4] PCI: Change pbus_size_mem() return values to be more conventional Bjorn Helgaas
2014-05-22  8:20       ` Wei Yang
2014-05-22 16:59         ` Bjorn Helgaas
2014-05-20  3:46     ` [PATCH v10 3/4] PCI: Simplify __pci_assign_resource() coding style Bjorn Helgaas
2014-05-20  3:46     ` [PATCH v10 4/4] PCI: Add resource allocation comments Bjorn Helgaas
2014-05-21  3:31     ` [PATCH v10 0/4] PCI: Restrict 64-bit prefetchable bridge windows to 64-bit resources Wei Yang
2014-05-21  4:36       ` Bjorn Helgaas

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=20140408082240.GB3198@yanx \
    --to=yan@linux.vnet.ibm.com \
    --cc=amirv@mellanox.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=eugenia@mellanox.com \
    --cc=jackm@dev.mellanox.co.il \
    --cc=linux-pci@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=shangw@linux.vnet.ibm.com \
    --cc=talal@mellanox.com \
    --cc=weiyang@linux.vnet.ibm.com \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).