From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, ehabkost@redhat.com, marcel@redhat.com,
mst@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 5/5] x86: Set physical address bits based on host
Date: Fri, 8 Jul 2016 18:34:03 +0200 [thread overview]
Message-ID: <a757e0e5-aff2-3538-63cf-dea8d2a28076@redhat.com> (raw)
In-Reply-To: <1467990099-27853-6-git-send-email-dgilbert@redhat.com>
On 08/07/2016 17:01, Dr. David Alan Gilbert (git) wrote:
> + uint32_t host_phys_bits = x86_host_phys_bits();
> + static bool warned;
> +
> + if (cpu->host_phys_bits) {
> + /* The user asked for us to use the host physical bits */
> + cpu->phys_bits = host_phys_bits;
> + }
> +
> + /* Print a warning if the user set it to a value that's not the
> + * host value.
> + */
> + if (cpu->phys_bits != host_phys_bits && cpu->phys_bits != 0 &&
> + !warned) {
> + error_report("Warning: Host physical bits (%u)"
> + " does not match phys-bits property (%u)",
> + host_phys_bits, cpu->phys_bits);
> + warned = true;
> + }
> +
> + if (cpu->phys_bits &&
> + (cpu->phys_bits > TARGET_PHYS_ADDR_SPACE_BITS ||
> + cpu->phys_bits < 32)) {
> error_setg(errp, "phys-bits should be between 32 and %u "
> " (but is %u)",
> TARGET_PHYS_ADDR_SPACE_BITS, cpu->phys_bits);
Michael Tsirkin suggested a way to support guest-phys-bits <
host-phys-bits in KVM. I plan to implement it soonish. In the
meanwhile I guess this patch is fine, we can refine it later.
Paolo
next prev parent reply other threads:[~2016-07-08 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 15:01 [Qemu-devel] [PATCH v4 0/5] x86: Physical address limit patches Dr. David Alan Gilbert (git)
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 1/5] x86: Provide TCG_PHYS_ADDR_BITS Dr. David Alan Gilbert (git)
2016-07-08 18:44 ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 2/5] x86: Allow physical address bits to be set Dr. David Alan Gilbert (git)
2016-07-08 18:59 ` Eduardo Habkost
2016-07-08 19:24 ` Paolo Bonzini
2016-07-08 19:25 ` Dr. David Alan Gilbert
2016-07-08 19:50 ` Eduardo Habkost
2016-07-08 23:36 ` Eduardo Habkost
2016-07-09 0:59 ` Richard Henderson
2016-07-09 2:36 ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 3/5] x86: Mask mtrr mask based on CPU physical address limits Dr. David Alan Gilbert (git)
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 4/5] x86: fill high bits of mtrr mask Dr. David Alan Gilbert (git)
2016-07-08 23:07 ` Eduardo Habkost
2016-07-08 15:01 ` [Qemu-devel] [PATCH v4 5/5] x86: Set physical address bits based on host Dr. David Alan Gilbert (git)
2016-07-08 16:34 ` Paolo Bonzini [this message]
2016-07-08 23:16 ` Eduardo Habkost
2016-07-11 12:29 ` Dr. David Alan Gilbert
2016-07-11 13:01 ` Eduardo Habkost
2016-07-11 15:39 ` Dr. David Alan Gilbert
2016-07-11 18:42 ` Eduardo Habkost
2016-07-11 18:47 ` Dr. David Alan Gilbert
2016-07-09 0:15 ` [Qemu-devel] [PATCH v4 0/5] x86: Physical address limit patches Eduardo Habkost
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=a757e0e5-aff2-3538-63cf-dea8d2a28076@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.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).