From: Laszlo Ersek <lersek@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
Guilherme Piccoli <gpiccoli@canonical.com>
Cc: Pedro Principeza <pedro.principeza@canonical.com>,
ehabkost@redhat.com, Dann Frazier <dann.frazier@canonical.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
qemu-devel@nongnu.org, fw@gpiccoli.net
Subject: Re: ovmf / PCI passthrough impaired due to very limiting PCI64 aperture
Date: Wed, 17 Jun 2020 15:25:56 +0200 [thread overview]
Message-ID: <fefd8b35-bf57-c88e-5cfc-815189bbf05a@redhat.com> (raw)
In-Reply-To: <20200617064014.3j7no7d7trob2ioc@sirius.home.kraxel.org>
On 06/17/20 08:40, Gerd Hoffmann wrote:
> Hi,
>
>> What if then we have OVMF relying in the physbits *iff*
>> "-host-phys-bits" is used
>
> How can the guest know?
Exactly!
> Adding "you can trust physbits" bits somewhere (as suggested by Eduardo)
> would work for sure, but would depend on a qemu update.
>
> Maybe a "don't trust physbits in case it is 40" heuristic works well
> enough in practice.
... for how many years? ;)
No heuristics please.
(I absolutely prefer X-PciMmio64Mb to guesswork. With X-PciMmio64Mb,
users at least know they have to be careful. I know they don't like
that, they just want a promise "it will work forever", but it's not
randomly called "experimental", we're not there just yet.)
Thank you,
Laszlo
>> Now, regarding the problem "to trust or not" in the guests' physbits,
>> I think it's an orthogonal discussion to some extent.
>
> It isn't. OVMF can't ignore the problem, you risk to break guests if
> you do.
>
> take care,
> Gerd
>
next prev parent reply other threads:[~2020-06-17 13:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 15:16 ovmf / PCI passthrough impaired due to very limiting PCI64 aperture Guilherme G. Piccoli
2020-06-16 16:50 ` Gerd Hoffmann
2020-06-16 16:57 ` Dr. David Alan Gilbert
2020-06-16 17:10 ` Eduardo Habkost
2020-06-17 8:17 ` Christophe de Dinechin
2020-06-17 16:25 ` Eduardo Habkost
2020-06-17 8:50 ` Daniel P. Berrangé
2020-06-17 10:28 ` Dr. David Alan Gilbert
2020-06-17 14:11 ` Eduardo Habkost
2020-06-16 17:10 ` Gerd Hoffmann
2020-06-16 17:16 ` Dr. David Alan Gilbert
2020-06-16 17:14 ` Guilherme Piccoli
2020-06-17 6:40 ` Gerd Hoffmann
2020-06-17 13:25 ` Laszlo Ersek [this message]
2020-06-17 13:26 ` Laszlo Ersek
2020-06-17 13:22 ` Laszlo Ersek
2020-06-17 13:43 ` Guilherme Piccoli
2020-06-17 15:57 ` Laszlo Ersek
2020-06-17 16:01 ` Guilherme Piccoli
2020-06-18 7:56 ` Laszlo Ersek
2020-06-17 13:46 ` Dr. David Alan Gilbert
2020-06-17 15:49 ` Eduardo Habkost
2020-06-17 15:57 ` Guilherme Piccoli
2020-06-17 16:33 ` Eduardo Habkost
2020-06-17 16:40 ` Guilherme Piccoli
2020-06-18 8:00 ` Laszlo Ersek
2020-06-17 16:04 ` Dr. David Alan Gilbert
2020-06-17 16:17 ` Daniel P. Berrangé
2020-06-17 16:22 ` Eduardo Habkost
2020-06-17 16:41 ` Dr. David Alan Gilbert
2020-06-17 17:17 ` Daniel P. Berrangé
2020-06-17 17:23 ` Dr. David Alan Gilbert
2020-06-17 16:28 ` Eduardo Habkost
2020-06-19 16:13 ` Dr. David Alan Gilbert
2020-06-17 16:14 ` Laszlo Ersek
2020-06-17 16:43 ` Laszlo Ersek
2020-06-17 17:02 ` Eduardo Habkost
2020-06-18 8:29 ` Laszlo Ersek
2020-06-17 8:16 ` Christophe de Dinechin
2020-06-17 10:12 ` Gerd Hoffmann
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=fefd8b35-bf57-c88e-5cfc-815189bbf05a@redhat.com \
--to=lersek@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dann.frazier@canonical.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fw@gpiccoli.net \
--cc=gpiccoli@canonical.com \
--cc=kraxel@redhat.com \
--cc=pedro.principeza@canonical.com \
--cc=qemu-devel@nongnu.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).