From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: xen-devel@lists.xenproject.org, Andrew.Cooper3@citrix.com
Subject: Re: Ryzen 6000 (Mobile)
Date: Tue, 6 Sep 2022 12:52:25 +0200 [thread overview]
Message-ID: <0fb4cab5-beed-777e-ae58-5d8b79893c30@suse.com> (raw)
In-Reply-To: <J4OUtvfDQmC1VoMHUDxa-c-c6LAnJzclOfocuzVylOTkOKm7H3Rp64q4svIjtgzGKVHQAuorobWyZxsamZsozAbiV3iZFvn__AjeNBqGf2Q=@protonmail.com>
On 29.08.2022 17:26, Dylanger Daly wrote:
> Please see the attached iomem and meminfo text files from both Qubes under Xen and functional Fedora Workstation.
>
> After some investigation, I've seen that I'm able to run a few small VMs just fine, however as soon as I start a larger VM, PCI devices appear to stop working, I assume this is because AMD moved PCI register addresses and Xen doesn't know about this change, so it's mapping this memory for other appVMs to use, resulting in weird behavior? Does that sound correct?
Not really, no. Even if BARs were moved, they still shouldn't overlap RAM.
But yes, BARs moving without Xen knowing would already be a problem. But
then the basic question is: Why would BARs be moved? The only reason I
could see (in the context of VM creation) is if PCI pass-through was
involved. Iirc you said it isn't, though.
Jan
next prev parent reply other threads:[~2022-09-06 21:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 23:04 Ryzen 6000 (Mobile) Dylanger Daly
2022-07-19 6:29 ` Jan Beulich
2022-07-19 6:47 ` Dylanger Daly
2022-07-19 6:58 ` Jan Beulich
2022-07-19 6:50 ` Dylanger Daly
2022-07-19 9:34 ` Andrew Cooper
2022-07-20 0:33 ` Dylanger Daly
2022-07-20 8:11 ` Jan Beulich
2022-07-20 8:13 ` Jan Beulich
2022-08-15 11:07 ` Dylanger Daly
2022-08-15 11:30 ` Jan Beulich
2022-08-15 11:50 ` Dylanger Daly
2022-08-15 11:55 ` Jan Beulich
2022-08-15 12:03 ` Andrew Cooper
2022-08-15 15:39 ` Dylanger Daly
2022-08-15 16:19 ` Jan Beulich
2022-08-15 16:54 ` Dylanger Daly
2022-08-16 6:17 ` Jan Beulich
2022-08-16 8:34 ` Dylanger Daly
2022-08-16 8:59 ` Jan Beulich
2022-08-16 9:19 ` Dylanger Daly
2022-08-16 9:30 ` Jan Beulich
2022-08-16 11:22 ` Jan Beulich
2022-08-24 18:15 ` Dylanger Daly
2022-08-25 8:35 ` Jan Beulich
2022-08-25 11:10 ` Dylanger Daly
2022-08-25 14:55 ` Jan Beulich
2022-08-29 15:26 ` Dylanger Daly
2022-09-06 10:52 ` Jan Beulich [this message]
2022-09-06 11:45 ` Dylanger Daly
2022-08-31 22:12 ` Dylanger Daly
2022-09-06 10:50 ` Jan Beulich
2022-09-03 15:59 ` Dylanger Daly
2022-09-05 20:44 ` Dylanger Daly
[not found] ` <6JMvOsjmpWkAsnm6AXzNsjtj5_jy5vG_vG_PwTyDzX0z1buoX89r5UEpSGKf-H7CTBtg9gNlq4Icy7Q9OIDjfrxp2AqNMXbyKTCD0y_d0Hc=@protonmail.com>
2022-09-06 11:51 ` 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=0fb4cab5-beed-777e-ae58-5d8b79893c30@suse.com \
--to=jbeulich@suse.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=dylangerdaly@protonmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.