public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: eranian@gmail.com
Cc: Robert Richter <robert.richter@amd.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	perfmon2-devel@lists.sourceforge.net,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [perfmon2] [PATCH 2/2] x86: add PCI extended config space	access for AMD Barcelona
Date: Fri, 27 Jun 2008 17:35:21 -0400	[thread overview]
Message-ID: <48655D19.7010204@redhat.com> (raw)
In-Reply-To: <7c86c4470806270810q4c739f25r44ed194a48cf7c1f@mail.gmail.com>

stephane eranian wrote:
> Robert,
> 
> This patch was applied to the perfmon GIT tree.
> Please test.
> Thanks.
> 
> 
> On Thu, Jun 19, 2008 at 5:59 PM, Robert Richter <robert.richter@amd.com> wrote:
>> On 19.06.08 17:50:40, Robert Richter wrote:
>>> This patch implements PCI extended configuration space access for
>>> AMD's Barcelona CPUs. It extends the method using CF8/CFC IO
>>> addresses. An x86 capability bit has been introduced that is set for
>>> CPUs supporting PCI extended config space accesses.
>>>
>>> Signed-off-by: Robert Richter <robert.richter@amd.com>
>>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>>> ---
>>>  arch/x86/kernel/cpu/cpu.h |    3 +
>>>  arch/x86/pci/Makefile_32  |    1 +
>>>  arch/x86/pci/Makefile_64  |    2 +-
>>>  arch/x86/pci/amd_bus.c    |  560 +++++++++++++++++++++++++++++++++++++++++++++
>>>  arch/x86/pci/direct.c     |   25 ++-
>>>  arch/x86/pci/k8-bus_64.c  |  528 ------------------------------------------
>>>  arch/x86/pci/pci.h        |    1 +
>>>  7 files changed, 584 insertions(+), 536 deletions(-)
>>>  create mode 100644 arch/x86/pci/amd_bus.c
>>>  delete mode 100644 arch/x86/pci/k8-bus_64.c
>> These patches are for the perfmon/master tree. They are based upon
>> tip/x86/cpu.
>>
>> -Robert
>>
>> --
>> Advanced Micro Devices, Inc.
>> Operating System Research Center
>> email: robert.richter@amd.com

It looks like the amd_bus.c file didn't get into the git tree. See the builds 
failing because of that.

-Will

  reply	other threads:[~2008-06-27 21:35 UTC|newest]

Thread overview: 14+ 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
2008-04-29 16:42           ` Arjan van de Ven
2008-05-08 10:11             ` Robert Richter
2008-06-19 15:50           ` [PATCH 1/2] AMD64: Removing PCI ECS workaround Robert Richter
2008-06-19 15:50           ` [PATCH 2/2] x86: add PCI extended config space access for AMD Barcelona Robert Richter
2008-06-19 15:59             ` Robert Richter
2008-06-27 15:10               ` stephane eranian
2008-06-27 21:35                 ` William Cohen [this message]
2008-06-27 23:07                   ` [perfmon2] " stephane eranian
2008-05-02 16:01   ` 2.6.25 new perfmon kernel patch + libpfm + pfmon available 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=48655D19.7010204@redhat.com \
    --to=wcohen@redhat.com \
    --cc=arjan@infradead.org \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=perfmon2-devel@lists.sourceforge.net \
    --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