xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Bader <stefan.bader@canonical.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xiantao.zhang@intel.com,
	Suravee Suthikulanit <suravee.suthikulpanit@amd.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 1/1] x86/AMD: Fix setup ssss:bb:dd:f for d0 failed
Date: Thu, 08 Aug 2013 14:35:12 +0200	[thread overview]
Message-ID: <52039080.6010005@canonical.com> (raw)
In-Reply-To: <5203AB2C02000078000EA4CC@nat28.tlf.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 3227 bytes --]

On 08.08.2013 14:29, Jan Beulich wrote:
>>>> On 08.08.13 at 14:07, Stefan Bader <stefan.bader@canonical.com> wrote:
>> On 08.08.2013 13:49, Jan Beulich wrote:
>>> Question is - did you in particular try with a legacy PCI device
>>> behind a legacy PCI bridge? That's the main scenario where the
>>> bridge not having got mapped could result in problems (see my
>>> other reply to Suravee on this thread).
>>
>> Not sure whether I confuse things here. Would the VGA card be what you 
>> meant?
> 
> If the output you provided was complete, then this really seems to
> be a legacy PCI device, so yes. But please realize that this working
> for you is not a guarantee that it's working in general - whether
> requests get forwarded by legacy bridges with the original requester
> ID or the bridge's is subject to the bridge implementation afaik. So a
> theoretical answer is going to be needed here anyway... But thanks
> for clarifying!

No, sure it is only one piece of the puzzle and a completing theoretical answer
is needed. Would not want to rely on any single testing.

-Stefan
> 
> Jan
> 
>> -[0000:00]-+-00.0  Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI 
>> bridg
>> e (external gfx0 port A) [1002:5a13]
>>            ...
>>            +-14.4-[04]----04.0  Matrox Electronics Systems Ltd. MGA G200eW
>> WPCM450 [102b:0532]
>>
>> 00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI 
>> to
>> PCI Bridge [1002:4384] (prog-if 01 [Subtractive decode])
>> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
>> SERR+ FastB2B- DisINTx-
>> 	Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
>> <MAbort- >SERR- <PERR- INTx-
>> 	Latency: 64
>> 	Bus: primary=00, secondary=04, subordinate=04, sec-latency=64
>> 	I/O behind bridge: 0000f000-00000fff
>> 	Memory behind bridge: fdf00000-fe7fffff
>> 	Prefetchable memory behind bridge: fc000000-fcffffff
>> 	Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
>> <MAbort+ <SERR- <PERR-
>> 	BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
>> 		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
>>
>> 04:04.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. 
>> MGA
>> G200eW WPCM450 [102b:0532] (rev 0a) (prog-if 00 [VGA controller])
>> 	Subsystem: Super Micro Computer Inc Device [15d9:a711]
>> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
>> SERR- FastB2B- DisINTx-
>> 	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
>> <MAbort- >SERR- <PERR- INTx-
>> 	Latency: 64 (4000ns min, 8000ns max), Cache Line Size: 64 bytes
>> 	Interrupt: pin A routed to IRQ 10
>> 	Region 0: Memory at fc000000 (32-bit, prefetchable) [size=16M]
>> 	Region 1: Memory at fdffc000 (32-bit, non-prefetchable) [size=16K]
>> 	Region 2: Memory at fe000000 (32-bit, non-prefetchable) [size=8M]
>> 	Expansion ROM at <unassigned> [disabled]
>> 	Capabilities: [dc] Power Management version 1
>> 		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
>> 		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> 
> 
> 



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-08-08 12:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  2:40 [PATCH 1/1] x86/AMD: Fix setup ssss:bb:dd:f for d0 failed suravee.suthikulpanit
2013-08-07  2:42 ` Suravee Suthikulanit
2013-08-07  8:33   ` Stefan Bader
2013-08-08 11:12     ` Stefan Bader
2013-08-08 11:49       ` Jan Beulich
2013-08-08 12:07         ` Stefan Bader
2013-08-08 12:29           ` Jan Beulich
2013-08-08 12:35             ` Stefan Bader [this message]
2013-08-07  7:33 ` Jan Beulich
2013-08-07 15:31   ` Suravee Suthikulanit
2013-08-07 15:42     ` Jan Beulich
2013-08-07 19:20       ` Suravee Suthikulanit
2013-08-08  6:38         ` Jan Beulich
2013-08-30  1:25           ` Suravee Suthikulpanit
2013-08-30  8:09             ` Jan Beulich
2013-08-31  0:03               ` Suravee Suthikulpanit
2013-08-07  9:34 ` Andrew Cooper
2013-08-07  9:57   ` Jan Beulich

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=52039080.6010005@canonical.com \
    --to=stefan.bader@canonical.com \
    --cc=JBeulich@suse.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xiantao.zhang@intel.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).