From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: greg@kroah.com, mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] x86_64: check msr to get mmconfig for amd family 10h opteron v3
Date: Mon, 11 Feb 2008 19:45:38 -0800 [thread overview]
Message-ID: <200802111945.38920.yinghai.lu@sun.com> (raw)
In-Reply-To: <20080211185115.87e878d3.akpm@linux-foundation.org>
On Monday 11 February 2008 06:51:15 pm Andrew Morton wrote:
> On Mon, 11 Feb 2008 18:20:46 -0800 Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
>
> > On Monday 11 February 2008 05:09:44 pm Andrew Morton wrote:
> > > On Mon, 11 Feb 2008 16:48:35 -0800
> > > Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
> > >
> > > > From: Yinghai Lu <Yinghai.Lu@Sun.COM>
> > > >
> > > > so even booting kernel with acpi=off or even MCFG is not there, we still can
> > > > use MMCONFIG.
> > > >
> > >
> > > This patch threw a big reject. I didn't check why.
> > >
> > >
> > > > + pci_direct_conf1.read(0, bus, devfn, 0, 4, &l);
> > >
> > > When I fixed the reject, compilation failed here.
> > >
> > > arch/x86/pci/mmconfig-shared.c: In function 'pci_mmcfg_check_hostbridge':
> > > arch/x86/pci/mmconfig-shared.c:214: error: 'pci_direct_conf1' undeclared (first use in this function)
> > >
> > >
> > > What kernel are you patching?
> > >
> >
> > linus tree.
>
> hm. So why didn't it compile? pci_direct_conf1 is defined over in
> arch/x86/pci/direct.c and is not mentioned in any header file.
it is in arch/x86/pci/pci.h
and arch/x86/pci/mmconf_shared.c has one
#include "pci.h"
did you compile that for 32 bit?
YH
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b6ce068a1285a24185b01be8a49021827516b3e1
diff --git a/arch/x86/pci/pci.h b/arch/x86/pci/pci.h
index 36cb44c..3431518 100644 (file)
--- a/arch/x86/pci/pci.h
+++ b/arch/x86/pci/pci.h
@@ -85,10 +85,17 @@ extern spinlock_t pci_config_lock;
extern int (*pcibios_enable_irq)(struct pci_dev *dev);
extern void (*pcibios_disable_irq)(struct pci_dev *dev);
-extern int pci_conf1_write(unsigned int seg, unsigned int bus,
- unsigned int devfn, int reg, int len, u32 value);
-extern int pci_conf1_read(unsigned int seg, unsigned int bus,
- unsigned int devfn, int reg, int len, u32 *value);
+struct pci_raw_ops {
+ int (*read)(unsigned int domain, unsigned int bus, unsigned int devfn,
+ int reg, int len, u32 *val);
+ int (*write)(unsigned int domain, unsigned int bus, unsigned int devfn,
+ int reg, int len, u32 val);
+};
+
+extern struct pci_raw_ops *raw_pci_ops;
+extern struct pci_raw_ops *raw_pci_ext_ops;
+
+extern struct pci_raw_ops pci_direct_conf1;
extern int pci_direct_probe(void);
extern void pci_direct_init(int type);
prev parent reply other threads:[~2008-02-12 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 0:43 [PATCH 1/4] x86: validate against acpi motherboard resources Yinghai Lu
2008-02-12 0:45 ` [PATCH 2/4] x86: clear pci_mmcfg_virt when mmcfg get rejected Yinghai Lu
2008-02-12 0:47 ` [PATCH 3/4] x86: mmconf enable mcfg early Yinghai Lu
2008-02-12 0:48 ` [PATCH 4/4] x86_64: check msr to get mmconfig for amd family 10h opteron v3 Yinghai Lu
2008-02-12 1:09 ` Andrew Morton
2008-02-12 2:20 ` Yinghai Lu
2008-02-12 2:51 ` Andrew Morton
2008-02-12 3:45 ` Yinghai Lu [this message]
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=200802111945.38920.yinghai.lu@sun.com \
--to=yinghai.lu@sun.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.