From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Sergio Lopez <slp@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH v2 0/2] expose host-phys-bits to guest
Date: Thu, 8 Sep 2022 13:31:07 +0200 [thread overview]
Message-ID: <20220908113109.470792-1-kraxel@redhat.com> (raw)
When the guest (firmware specifically) knows how big
the address space actually is it can be used better.
Some more background:
https://bugzilla.redhat.com/show_bug.cgi?id=2084533
This is a RfC series exposes the information via cpuid.
v2:
- change fvm hint name.
- better commit message.
take care,
Gerd
Gerd Hoffmann (2):
[temporary] reserve bit KVM_HINTS_PHYS_ADDRESS_SIZE_DATA_VALID
[RfC] expose host-phys-bits to guest
include/standard-headers/asm-x86/kvm_para.h | 3 ++-
target/i386/cpu.h | 3 ---
hw/i386/microvm.c | 7 ++++++-
target/i386/cpu.c | 3 +--
target/i386/host-cpu.c | 5 ++++-
target/i386/kvm/kvm.c | 1 +
6 files changed, 14 insertions(+), 8 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-08 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 11:31 Gerd Hoffmann [this message]
2022-09-08 11:31 ` [PATCH v2 1/2] [temporary] reserve bit KVM_HINTS_PHYS_ADDRESS_SIZE_DATA_VALID Gerd Hoffmann
2022-09-08 11:31 ` [PATCH v2 2/2] [RfC] expose host-phys-bits to guest Gerd Hoffmann
2022-09-08 14:19 ` Michael S. Tsirkin
2022-09-09 5:18 ` Gerd Hoffmann
2022-09-09 5:51 ` Michael S. Tsirkin
2022-09-09 6:06 ` Gerd Hoffmann
2022-09-09 6:13 ` Michael S. Tsirkin
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=20220908113109.470792-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=eduardo@habkost.net \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=slp@redhat.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).