From: "stephane eranian" <eranian@googlemail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, ia64 <linux-ia64@vger.kernel.org>,
Robert Richter <robert.richter@amd.com>
Subject: Re: 2.6.25 new perfmon kernel patch + libpfm + pfmon available
Date: Wed, 30 Apr 2008 13:51:39 +0000 [thread overview]
Message-ID: <7c86c4470804300651u5a8fc98dr56fd1834ba902a0e@mail.gmail.com> (raw)
In-Reply-To: <20080429083334.1a019318@infradead.org>
If I recall, AMD said that this special initialization would eventually migrate
into the core kernel. The pci_read() may be there because it was not exported
by the kernel (this particular code lives in a kernel module).
If you think there is now enough support in the core kernel to do this
initialization
then I'd be happy to remove this piece of code.
On Tue, Apr 29, 2008 at 5:33 PM, Arjan van de Ven <arjan@infradead.org> wrote:
> On Wed, 30 Apr 2008 15:11:11 +0200
>
> "stephane eranian" <eranian@googlemail.com> wrote:
>
>
> > Sorry,
> >
> > It's http://perfmon2.sf.net
> >
> >
>
> hummmmm, I wonder why perfmon wants to reimplement half of the PCI layer...
>
> +extern spinlock_t pci_config_lock;
> +
> +#define PCI_CONF1_ADDRESS(bus, devfn, reg) \
> + (0x80000000 | ((reg & 0xF00) << 16) | ((bus & 0xFF) << 16) \
> + | (devfn << 8) | (reg & 0xFC))
> +
> +#define is_ibs_pmc(x) (x = 4 || x = 5)
> +
> +static int pci_read(unsigned int seg, unsigned int bus,
> + unsigned int devfn, int reg, int len, u32 *value)
> +{
> + unsigned long flags;
>
> especially since this doesn't seem to use the proper config space abstractions :(
>
next prev parent reply other threads:[~2008-04-30 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c86c4470804291446l4693b317ha7ee2382d00e99e6@mail.gmail.com>
2008-04-29 21:47 ` 2.6.25 new perfmon kernel patch + libpfm + pfmon available stephane eranian
2008-04-29 15:08 ` Arjan van de Ven
2008-04-30 13:11 ` stephane eranian
2008-04-29 15:33 ` Arjan van de Ven
2008-04-30 13:51 ` stephane eranian [this message]
2008-04-29 16:42 ` Arjan van de Ven
2008-05-08 10:11 ` Robert Richter
2008-05-02 16:01 ` stephane eranian
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=7c86c4470804300651u5a8fc98dr56fd1834ba902a0e@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=arjan@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.richter@amd.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