From: Patrick Plenefisch <simonpatp@gmail.com>
To: Huang Rui <ray.huang@amd.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Juergen Gross" <jgross@suse.com>,
"Chen, Jiqian" <Jiqian.Chen@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: Re: ACPI VFCT table too short on PVH dom0 (was: Re: E820 memory allocation issue on Threadripper platforms)
Date: Sat, 20 Jan 2024 20:27:02 -0500 [thread overview]
Message-ID: <CAOCpoWeBe5LY-JkHdPfeJZSnXnBiLEWLvXosdH2fyPvJSoDxYw@mail.gmail.com> (raw)
In-Reply-To: <ZapG1weSIJWOkT8m@amd.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Fri, Jan 19, 2024 at 4:54 AM Huang Rui <ray.huang@amd.com> wrote:
> Thanks Roger to involve us. The VFCT table is to expose video BIOS image by
> AMD GPUs. You can see details here:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/include/atombios.h
>
> Did you apply this patch?
>
>
> https://lore.kernel.org/xen-devel/20230312075455.450187-2-ray.huang@amd.com/
Yes, that appears to be in 4.18. I recompiled and confirmed that 4.18 fails
with the same symptoms as 4.17
>
>
> Thanks,
> Ray
>
>
[-- Attachment #2: Type: text/html, Size: 1330 bytes --]
next prev parent reply other threads:[~2024-01-21 1:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 2:29 E820 memory allocation issue on Threadripper platforms Patrick Plenefisch
2024-01-11 8:37 ` Jan Beulich
2024-01-11 9:19 ` Xenia Ragiadakou
2024-01-11 10:13 ` Juergen Gross
2024-01-16 0:22 ` Patrick Plenefisch
2024-01-16 9:33 ` Jan Beulich
2024-01-17 6:12 ` Patrick Plenefisch
2024-01-17 8:46 ` Jan Beulich
2024-01-17 10:13 ` Roger Pau Monné
2024-01-17 10:40 ` Jan Beulich
2024-01-17 12:54 ` Roger Pau Monné
2024-01-18 6:23 ` Patrick Plenefisch
2024-01-18 8:27 ` Roger Pau Monné
2024-01-18 8:34 ` Patrick Plenefisch
2024-01-18 9:46 ` Roger Pau Monné
2024-01-18 12:41 ` ACPI VFCT table too short on PVH dom0 (was: Re: E820 memory allocation issue on Threadripper platforms) Roger Pau Monné
2024-01-19 7:44 ` Patrick Plenefisch
2024-01-19 9:54 ` Huang Rui
2024-01-19 15:32 ` Deucher, Alexander
2024-01-21 1:27 ` Patrick Plenefisch [this message]
2024-01-19 11:06 ` Roger Pau Monné
2024-01-21 1:33 ` Patrick Plenefisch
2024-01-24 1:27 ` Patrick Plenefisch
2024-01-24 8:23 ` Roger Pau Monné
2024-01-25 0:20 ` Patrick Plenefisch
2024-01-18 16:03 ` E820 memory allocation issue on Threadripper platforms Patrick Plenefisch
2024-01-18 9:01 ` Jan Beulich
2024-01-19 13:40 ` Marek Marczykowski-Górecki
2024-01-19 13:50 ` Jan Beulich
2024-01-19 14:31 ` Marek Marczykowski-Górecki
2024-03-10 14:06 ` Marek Marczykowski-Górecki
2024-03-12 21:07 ` Jason Andryuk
2024-03-12 22:00 ` Marek Marczykowski-Górecki
2024-01-17 8:46 ` Roger Pau Monné
2024-01-17 12:06 ` Marek Marczykowski-Górecki
2024-01-17 12:59 ` Roger Pau Monné
2024-01-17 13:40 ` 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=CAOCpoWeBe5LY-JkHdPfeJZSnXnBiLEWLvXosdH2fyPvJSoDxYw@mail.gmail.com \
--to=simonpatp@gmail.com \
--cc=Jiqian.Chen@amd.com \
--cc=alexander.deucher@amd.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=ray.huang@amd.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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: 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).