From: Igor Mammedov <imammedo@redhat.com>
To: Joao Martins <joao.m.martins@oracle.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, Daniel Jordan <daniel.m.jordan@oracle.com>,
David Edmondson <david.edmondson@oracle.com>,
Alex Williamson <alex.williamson@redhat.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Ani Sinha <ani@anisinha.ca>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH RFCv2 3/4] i386/pc: warn if phys-bits is too low
Date: Thu, 24 Feb 2022 10:01:38 +0100 [thread overview]
Message-ID: <20220224100138.0ddab7b9@redhat.com> (raw)
In-Reply-To: <04efb316-e231-7abd-0eb6-5b0241afd5f2@oracle.com>
On Wed, 23 Feb 2022 17:18:55 +0000
Joao Martins <joao.m.martins@oracle.com> wrote:
> On 2/14/22 15:18, Joao Martins wrote:
> > On 2/14/22 15:03, Igor Mammedov wrote:
> >> On Mon, 7 Feb 2022 20:24:21 +0000
> >> Joao Martins <joao.m.martins@oracle.com> wrote:
> >>
> >>> Default phys-bits on Qemu is TCG_PHYS_BITS (40) which is enough
> >>> to address 1Tb (0xff ffff ffff). On AMD platforms, if a
> >>> ram-above-4g relocation happens and the CPU wasn't configured
> >>> with a big enough phys-bits, warn the user. There isn't a
> >>> catastrophic failure exactly, the guest will still boot, but
> >>> most likely won't be able to use more than ~4G of RAM.
> >>
> >> how 'unable to use" would manifest?
> >> It might be better to prevent QEMU startup with broken setup (CLI)
> >> rather then letting guest run and trying to figure out what's
> >> going wrong when users start to complain.
> >>
> > Sounds better to be conservative here.
> >
> > I will change from warn_report() to error_report()
> > and exit.
> >
>
> I was running through x86_64 qtests prior to submission
> and it seems that the inclusion of a pci_hole64_size in
> the check added by this patch would break tests if we were
> to error out. So far, I'm keeping it as a warning over
> compatibility concerns, not limited these 5 test failures
> below. Let me know otherwise if you disagree, or if you
> prefer another way.
can you check what exactly breaks tests?
> Summary of Failures:
>
> 1/56 qemu:qtest+qtest-x86_64 / qtest-x86_64/qom-test ERROR 0.07s
> killed by signal 6 SIGABRT
> 4/56 qemu:qtest+qtest-x86_64 / qtest-x86_64/test-hmp ERROR 0.07s
> killed by signal 6 SIGABRT
> 7/56 qemu:qtest+qtest-x86_64 / qtest-x86_64/boot-serial-test ERROR 0.07s
> killed by signal 6 SIGABRT
> 44/56 qemu:qtest+qtest-x86_64 / qtest-x86_64/test-x86-cpuid-compat ERROR 0.09s
> killed by signal 6 SIGABRT
> 45/56 qemu:qtest+qtest-x86_64 / qtest-x86_64/numa-test ERROR 0.17s
> killed by signal 6 SIGABRT
>
next prev parent reply other threads:[~2022-02-24 9:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 20:24 [PATCH RFCv2 0/4] i386/pc: Fix creation of >= 1010G guests on AMD systems with IOMMU Joao Martins
2022-02-07 20:24 ` [PATCH RFCv2 1/4] hw/i386: add 4g boundary start to X86MachineState Joao Martins
2022-02-14 13:19 ` Igor Mammedov
2022-02-14 13:21 ` Joao Martins
2022-02-07 20:24 ` [PATCH RFCv2 2/4] i386/pc: relocate 4g start to 1T where applicable Joao Martins
2022-02-14 14:53 ` Igor Mammedov
2022-02-14 15:05 ` Joao Martins
2022-02-14 15:31 ` Igor Mammedov
2022-02-15 9:53 ` Gerd Hoffmann
2022-02-15 19:37 ` Joao Martins
2022-02-16 8:19 ` Gerd Hoffmann
2022-02-16 11:54 ` Joao Martins
2022-02-16 12:32 ` Gerd Hoffmann
2022-02-16 9:51 ` Daniel P. Berrangé
2022-02-21 13:15 ` Dr. David Alan Gilbert
2022-02-22 8:46 ` Igor Mammedov
2022-02-22 9:30 ` Dr. David Alan Gilbert
2022-02-22 9:42 ` Gerd Hoffmann
2022-02-23 8:43 ` Igor Mammedov
2022-02-23 9:16 ` Dr. David Alan Gilbert
2022-02-23 9:31 ` Igor Mammedov
2022-02-18 17:12 ` Joao Martins
2022-02-21 6:58 ` Igor Mammedov
2022-02-21 15:28 ` Joao Martins
2022-02-22 11:00 ` Joao Martins
2022-02-23 8:38 ` Igor Mammedov
2022-02-07 20:24 ` [PATCH RFCv2 3/4] i386/pc: warn if phys-bits is too low Joao Martins
2022-02-14 13:15 ` David Edmondson
2022-02-14 13:18 ` Joao Martins
2022-02-14 15:03 ` Igor Mammedov
2022-02-14 15:18 ` Joao Martins
2022-02-14 15:41 ` Igor Mammedov
2022-02-14 15:48 ` Joao Martins
2022-02-23 17:18 ` Joao Martins
2022-02-24 9:01 ` Igor Mammedov [this message]
2022-02-24 9:27 ` Joao Martins
2022-02-07 20:24 ` [PATCH RFCv2 4/4] i386/pc: Restrict AMD-only enforcing of valid IOVAs to new machine type Joao Martins
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=20220224100138.0ddab7b9@redhat.com \
--to=imammedo@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ani@anisinha.ca \
--cc=daniel.m.jordan@oracle.com \
--cc=david.edmondson@oracle.com \
--cc=ehabkost@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=suravee.suthikulpanit@amd.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).