On Fri, May 23, 2014 at 6:31 PM, Suravee Suthikulanit
wrote:
> On 5/22/2014 9:54 PM, Bjorn Helgaas wrote:
>>
>> I've been poking around for recent dmesg logs that contain "PCI: Using
>> configuration type 1 for extended access", and there are quite a few.
>> In most cases there*is* an MCFG
On Fri, May 23, 2014 at 6:31 PM, Suravee Suthikulanit
suravee.suthikulpa...@amd.com wrote:
On 5/22/2014 9:54 PM, Bjorn Helgaas wrote:
I've been poking around for recent dmesg logs that contain PCI: Using
configuration type 1 for extended access, and there are quite a few.
In most cases
On 5/22/2014 9:54 PM, Bjorn Helgaas wrote:
I've been poking around for recent dmesg logs that contain "PCI: Using
configuration type 1 for extended access", and there are quite a few.
In most cases there*is* an MCFG table, but apparently we decide not
to use it for some reason (unfortunately we
On 5/23/2014 6:56 AM, Robert Richter wrote:
On 22.05.14 20:54:54, Bjorn Helgaas wrote:
I'm going to go out on a limb and guess that Windows does not enable
ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
of MCFG is broken in some way, and we probably *could* use ECAM in all
On 23.05.14 07:01:41, Bjorn Helgaas wrote:
> [I guess I've been using the wrong term here. I think "ECS" just
> refers to the extended config space itself, and I should have been
> saying "IO ECS" or "EnableCf8ExtCfg".]
>
> My understanding was that if we don't enable IO ECS and we don't have
>
On Fri, May 23, 2014 at 5:56 AM, Robert Richter wrote:
> On 22.05.14 20:54:54, Bjorn Helgaas wrote:
>> I'm going to go out on a limb and guess that Windows does not enable
>> ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
>> of MCFG is broken in some way, and we probably
On 22.05.14 20:54:54, Bjorn Helgaas wrote:
> I'm going to go out on a limb and guess that Windows does not enable
> ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
> of MCFG is broken in some way, and we probably *could* use ECAM in all
> these cases I'm seeing.
Even if ECS
On 22.05.14 20:54:54, Bjorn Helgaas wrote:
I'm going to go out on a limb and guess that Windows does not enable
ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
of MCFG is broken in some way, and we probably *could* use ECAM in all
these cases I'm seeing.
Even if ECS is
On Fri, May 23, 2014 at 5:56 AM, Robert Richter r...@kernel.org wrote:
On 22.05.14 20:54:54, Bjorn Helgaas wrote:
I'm going to go out on a limb and guess that Windows does not enable
ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
of MCFG is broken in some way, and we
On 23.05.14 07:01:41, Bjorn Helgaas wrote:
[I guess I've been using the wrong term here. I think ECS just
refers to the extended config space itself, and I should have been
saying IO ECS or EnableCf8ExtCfg.]
My understanding was that if we don't enable IO ECS and we don't have
MCFG, we
On 5/23/2014 6:56 AM, Robert Richter wrote:
On 22.05.14 20:54:54, Bjorn Helgaas wrote:
I'm going to go out on a limb and guess that Windows does not enable
ECS, so it probably uses ECAM. Therefore, I suspect Linux's parsing
of MCFG is broken in some way, and we probably *could* use ECAM in all
On 5/22/2014 9:54 PM, Bjorn Helgaas wrote:
I've been poking around for recent dmesg logs that contain PCI: Using
configuration type 1 for extended access, and there are quite a few.
In most cases there*is* an MCFG table, but apparently we decide not
to use it for some reason (unfortunately we
On Thu, May 22, 2014 at 5:39 PM, Suravee Suthikulanit
wrote:
> On 5/22/2014 3:20 PM, Bjorn Helgaas wrote:
>> On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov wrote:
>>> On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the
On 5/22/2014 3:20 PM, Bjorn Helgaas wrote:
On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov wrote:
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the newest stuff
that's in the field. I suspect things would probably work if we
On Thu, May 22, 2014 at 02:20:04PM -0600, Bjorn Helgaas wrote:
> Even if MMCONFIG does work fine on everything from Fam10h onwards, we
> still depend on the BIOS to provide a correct MCFG table.
It is very hazy memory of mine that starting with F10h, we had an MCFG
table always present but I
On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov wrote:
> On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
>> I chose Fam16h (0x16) because it looks like that's the newest stuff
>> that's in the field. I suspect things would probably work if we
>> changed this patch to leave ECS
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
> I chose Fam16h (0x16) because it looks like that's the newest stuff
> that's in the field. I suspect things would probably work if we
> changed this patch to leave ECS disabled on some Fam16h, Fam15h, etc.,
> but that would change
On Wed, May 21, 2014 at 5:38 PM, Borislav Petkov wrote:
> On Wed, May 21, 2014 at 05:18:17PM -0600, Bjorn Helgaas wrote:
>> ECS is an AMD mechanism that allows access to extended PCI config space
>> (offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
>> MMCONFIG, to access
On Wed, May 21, 2014 at 5:38 PM, Borislav Petkov b...@alien8.de wrote:
On Wed, May 21, 2014 at 05:18:17PM -0600, Bjorn Helgaas wrote:
ECS is an AMD mechanism that allows access to extended PCI config space
(offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
MMCONFIG, to
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the newest stuff
that's in the field. I suspect things would probably work if we
changed this patch to leave ECS disabled on some Fam16h, Fam15h, etc.,
but that would change
On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov b...@alien8.de wrote:
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the newest stuff
that's in the field. I suspect things would probably work if we
changed this patch to leave
On Thu, May 22, 2014 at 02:20:04PM -0600, Bjorn Helgaas wrote:
Even if MMCONFIG does work fine on everything from Fam10h onwards, we
still depend on the BIOS to provide a correct MCFG table.
It is very hazy memory of mine that starting with F10h, we had an MCFG
table always present but I don't
On 5/22/2014 3:20 PM, Bjorn Helgaas wrote:
On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov b...@alien8.de wrote:
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16) because it looks like that's the newest stuff
that's in the field. I suspect things would
On Thu, May 22, 2014 at 5:39 PM, Suravee Suthikulanit
suravee.suthikulpa...@amd.com wrote:
On 5/22/2014 3:20 PM, Bjorn Helgaas wrote:
On Thu, May 22, 2014 at 1:17 PM, Borislav Petkov b...@alien8.de wrote:
On Thu, May 22, 2014 at 11:56:03AM -0600, Bjorn Helgaas wrote:
I chose Fam16h (0x16)
On Wed, May 21, 2014 at 05:18:17PM -0600, Bjorn Helgaas wrote:
> ECS is an AMD mechanism that allows access to extended PCI config space
> (offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
> MMCONFIG, to access that space, but apparently old machines have issues
> that meant
ECS is an AMD mechanism that allows access to extended PCI config space
(offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
MMCONFIG, to access that space, but apparently old machines have issues
that meant we couldn't use ECAM.
The solution was to enable ECS so we could use
ECS is an AMD mechanism that allows access to extended PCI config space
(offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
MMCONFIG, to access that space, but apparently old machines have issues
that meant we couldn't use ECAM.
The solution was to enable ECS so we could use
On Wed, May 21, 2014 at 05:18:17PM -0600, Bjorn Helgaas wrote:
ECS is an AMD mechanism that allows access to extended PCI config space
(offsets 256-4096) via I/O ports CF8/CFCh. We normally use ECAM, i.e.,
MMCONFIG, to access that space, but apparently old machines have issues
that meant we
28 matches
Mail list logo
