LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com> To: "Christian König" <christian.koenig@amd.com>, helgaas@kernel.org, linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org Subject: Re: [PATCH v9 4/5] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v5 Date: Tue, 21 Nov 2017 17:26:18 -0500 [thread overview] Message-ID: <b937778c-556e-5587-c557-abba8cefe100@oracle.com> (raw) In-Reply-To: <3443aad0-8c3b-b97e-685a-96b0866827be@amd.com> On 11/21/2017 08:34 AM, Christian König wrote: > Hi Boris, > > attached are two patches. > > The first one is a trivial fix for the infinite loop issue, it now > correctly aborts the fixup when it can't find address space for the > root window. > > The second is a workaround for your board. It simply checks if there > is exactly one Processor Function to apply this fix on. > > Both are based on linus current master branch. Please test if they fix > your issue. Yes, they do fix it but that's because the feature is disabled. Do you know what the actual problem was (on Xen)? Thanks. -boris > > Thanks for the help, > Christian. > > Am 20.11.2017 um 17:33 schrieb Boris Ostrovsky: >> On 11/20/2017 11:07 AM, Christian König wrote: >>> Am 20.11.2017 um 16:51 schrieb Boris Ostrovsky: >>>> (and then it breaks differently as a Xen guest --- we hung on the last >>>> pci_read_config_dword(), I haven't looked at this at all yet) >>> Hui? How does this fix applies to a Xen guest in the first place? >>> >>> Please provide the output of "lspci -nn" and explain further what is >>> your config with Xen. >>> >>> >> >> This is dom0. >> >> -bash-4.1# lspci -nn >> 00:00.0 Host bridge [0600]: ATI Technologies Inc RD890 Northbridge only >> dual slot (2x16) PCI-e GFX Hydra part [1002:5a10] (rev 02) >> 00:00.2 Generic system peripheral [0806]: ATI Technologies Inc Device >> [1002:5a23] >> 00:0d.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge >> (external gfx1 port B) [1002:5a1e] >> 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA >> Controller [AHCI mode] [1002:4391] >> 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB >> OHCI0 Controller [1002:4397] >> 00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 >> Controller [1002:4398] >> 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI >> Controller [1002:4396] >> 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB >> OHCI0 Controller [1002:4397] >> 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 >> Controller [1002:4398] >> 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI >> Controller [1002:4396] >> 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller >> [1002:4385] (rev 3d) >> 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host >> controller [1002:439d] >> 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge >> [1002:4384] >> 00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB >> OHCI2 Controller [1002:4399] >> 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1600] >> 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1601] >> 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1602] >> 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1603] >> 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1604] >> 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1605] >> 00:19.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1600] >> 00:19.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1601] >> 00:19.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1602] >> 00:19.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1603] >> 00:19.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1604] >> 00:19.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device >> [1022:1605] >> 01:04.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA >> G200eW WPCM450 [102b:0532] (rev 0a) >> 02:00.0 Ethernet controller [0200]: Intel Corporation 82576 Gigabit >> Network Connection [8086:10c9] (rev 01) >> 02:00.1 Ethernet controller [0200]: Intel Corporation 82576 Gigabit >> Network Connection [8086:10c9] (rev 01) >> -bash-4.1# >> >> >> -boris > >
next prev parent reply other threads:[~2017-11-21 22:26 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-18 13:58 Resizable PCI BAR support V9 Christian König 2017-10-18 13:58 ` [PATCH v9 1/5] PCI: add a define for the PCI resource type mask v2 Christian König 2017-10-18 13:58 ` [PATCH v9 2/5] PCI: add resizeable BAR infrastructure v5 Christian König 2017-10-18 13:58 ` [PATCH v9 3/5] PCI: add functionality for resizing resources v7 Christian König 2017-10-18 13:58 ` [PATCH v9 4/5] x86/PCI: Enable a 64bit BAR on AMD Family 15h (Models 30h-3fh) Processors v5 Christian König 2017-11-02 16:43 ` Alex Deucher 2017-11-20 15:51 ` Boris Ostrovsky 2017-11-20 16:07 ` Christian König 2017-11-20 16:33 ` Boris Ostrovsky 2017-11-21 13:34 ` Christian König 2017-11-21 22:26 ` Boris Ostrovsky [this message] 2017-11-22 10:09 ` Christian König 2017-11-22 16:24 ` Boris Ostrovsky 2017-11-22 16:54 ` Christian König 2017-11-22 17:27 ` Boris Ostrovsky 2017-11-23 8:11 ` Christian König 2017-11-23 14:12 ` Boris Ostrovsky 2017-11-27 18:30 ` Boris Ostrovsky 2017-11-28 9:12 ` Christian König 2017-11-28 9:46 ` [Xen-devel] " Jan Beulich 2017-11-28 10:17 ` Christian König 2017-11-28 10:53 ` Jan Beulich 2017-11-28 11:59 ` Christian König 2017-11-28 18:55 ` Boris Ostrovsky 2017-10-18 13:58 ` [PATCH v9 5/5] drm/amdgpu: resize VRAM BAR for CPU access v5 Christian König 2017-10-24 19:44 ` Resizable PCI BAR support V9 Bjorn Helgaas 2017-10-25 11:27 ` Christian König
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=b937778c-556e-5587-c557-abba8cefe100@oracle.com \ --to=boris.ostrovsky@oracle.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=christian.koenig@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=helgaas@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ /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: linkBe 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).