From: Greg KH <gregkh@suse.de>
To: tcamuso@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
prarit@redhat.com
Subject: Re: [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF
Date: Wed, 19 Dec 2007 15:04:47 -0800 [thread overview]
Message-ID: <20071219230447.GA24219@suse.de> (raw)
In-Reply-To: <20071219221751.20362.23451.sendpatchset@dhcp83-188.boston.redhat.com>
On Wed, Dec 19, 2007 at 05:17:51PM -0500, tcamuso@redhat.com wrote:
> commit d1f2a573ca7083d237cfc354f42e089de9fa0f0b
> Author: Tony Camuso <tony.camuso@hp.com>
> Date: Wed Dec 19 15:33:53 2007 -0500
>
> Introduces a flag bit to arch/x86/pci/pci.h to indicate that
> MMCONFIG is the system-wide default PCI config access mechanisim.
>
> Function pci_mmcfg_init() in arch/x86/pci/mmconfig-shared.c sets
> the bit in the pci_probe mask when MMCONFIG has been successfully
> initialized for the platform.
>
> Signed-off-by: Tony Camuso tony.camuso@hp.com
>
> diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c
> index 4df637e..fc0f866 100644
> --- a/arch/x86/pci/mmconfig-shared.c
> +++ b/arch/x86/pci/mmconfig-shared.c
> @@ -274,7 +274,8 @@ void __init pci_mmcfg_init(int type)
> unreachable_devices();
> if (known_bridge)
> pci_mmcfg_insert_resources(IORESOURCE_BUSY);
> - pci_probe = (pci_probe & ~PCI_PROBE_MASK) | PCI_PROBE_MMCONF;
> + pci_probe = pci_probe & ~PCI_PROBE_MASK;
> + pci_probe = pci_probe | PCI_PROBE_MMCONF | PCI_USING_MMCONF;
> } else {
> /*
> * Signal not to attempt to insert mmcfg resources because
> diff --git a/arch/x86/pci/pci.h b/arch/x86/pci/pci.h
> index ac56d39..53f4051 100644
> --- a/arch/x86/pci/pci.h
> +++ b/arch/x86/pci/pci.h
> @@ -28,6 +28,7 @@
> #define PCI_ASSIGN_ALL_BUSSES 0x4000
> #define PCI_CAN_SKIP_ISA_ALIGN 0x8000
> #define PCI_USE__CRS 0x10000
> +#define PCI_USING_MMCONF 0x20000
>
> extern unsigned int pci_probe;
> extern unsigned long pirq_table_addr;
> @@ -39,6 +40,8 @@ enum pci_bf_sort_state {
> pci_dmi_bf,
> };
>
> +extern struct pci_ops pci_legacy_ops; /* direct.c */
This isn't needed in this patch at all, and might make the compiler
confused if you were to build with only this patch present :(
thanks,
greg k-h
next parent reply other threads:[~2007-12-19 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071219221746.20362.39243.sendpatchset@dhcp83-188.boston.redhat.com>
[not found] ` <20071219221751.20362.23451.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:04 ` Greg KH [this message]
[not found] ` <4769B035.9020005@redhat.com>
[not found] ` <20071220001936.GA23791@suse.de>
2007-12-20 0:49 ` [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF Tony Camuso
[not found] ` <20071219221756.20362.84805.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:06 ` [PATCH 2/5]PCI: x86 MMCONFIG: add legacy pci conf functions Greg KH
[not found] ` <20071219221806.20362.25964.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:10 ` [PATCH 4/5]PCI: x86 MMCONFIG: introduce pcibios_fix_bus_scan() Greg KH
2007-12-19 23:14 ` Greg KH
2007-12-19 23:16 ` [PATCH 0/5]PCI: x86 MMCONFIG Greg KH
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=20071219230447.GA24219@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=prarit@redhat.com \
--cc=tcamuso@redhat.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;
as well as URLs for NNTP newsgroup(s).