public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu Zhao <yu.zhao@intel.com>
To: "jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"marc.c.dionne@gmail.com" <marc.c.dionne@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: use fixed-up device class when configuring device
Date: Mon, 01 Jun 2009 09:50:07 +0800	[thread overview]
Message-ID: <4A2333CF.2040601@intel.com> (raw)
In-Reply-To: <20090529171956.GE28355@lackof.org>

Hi Jesse,

Can you please take this fix for 2.6.30 RC if possible? It fixes a 
regression introduced by the SR-IOV patch series.

Thanks,
Yu

Grant Grundler wrote:
> On Thu, May 28, 2009 at 12:25:05AM +0800, Yu Zhao wrote:
>> The device class may be changed after the early fixup. Need to
>> re-read the class value from pci_dev when configuring the device.
>> Otherwise some devices such as JMicron SATA controller won't work.
> 
> I looked at pci_setup_device() and was thinking pci_fixup_device()
> should be called before pci_cfg_space_size() and thus avoid having
> to setup local "class" variable twice. pci_cfg_space_size() only
> seems to care if the device is a PCI_CLASS_BRIDGE_HOST (or not).
> 
> But dev->class has to be set up in any case and the current order
> makes more sense to me.
> 
> Reviewed-by: Grant Grundler <grundler@parisc-linux.org>
> 
> thanks,
> grant
> 
>> Tested-by: Marc Dionne <marc.c.dionne@gmail.com>
>> Signed-off-by: Yu Zhao <yu.zhao@intel.com>
>> ---
>>  drivers/pci/probe.c |    2 ++
>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>> index e3c3e08..f1ae247 100644
>> --- a/drivers/pci/probe.c
>> +++ b/drivers/pci/probe.c
>> @@ -745,6 +745,8 @@ int pci_setup_device(struct pci_dev *dev)
>>  
>>  	/* Early fixups, before probing the BARs */
>>  	pci_fixup_device(pci_fixup_early, dev);
>> +	/* device class may be changed after fixup */
>> +	class = dev->class >> 8;
>>  
>>  	switch (dev->hdr_type) {		    /* header type */
>>  	case PCI_HEADER_TYPE_NORMAL:		    /* standard header */
>> -- 
>> 1.6.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-06-01  1:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 16:25 [PATCH] PCI: use fixed-up device class when configuring device Yu Zhao
2009-05-29 17:19 ` Grant Grundler
2009-06-01  1:50   ` Yu Zhao [this message]
2009-06-01  8:31     ` Jesse Barnes
2009-06-04 10:32     ` Jesse Barnes

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=4A2333CF.2040601@intel.com \
    --to=yu.zhao@intel.com \
    --cc=grundler@parisc-linux.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=marc.c.dionne@gmail.com \
    /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