From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Sergio Lopez <slp@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH 0/2] expose host-phys-bits to guest
Date: Wed, 31 Aug 2022 14:50:57 +0200 [thread overview]
Message-ID: <20220831125059.170032-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.
take care,
Gerd
Gerd Hoffmann (2):
[hack] reserve bit KVM_HINTS_HOST_PHYS_BITS
[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 | 6 +++++-
target/i386/cpu.c | 3 +--
target/i386/host-cpu.c | 4 +++-
target/i386/kvm/kvm.c | 1 +
6 files changed, 12 insertions(+), 8 deletions(-)
--
2.37.2
next reply other threads:[~2022-08-31 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 12:50 Gerd Hoffmann [this message]
2022-08-31 12:50 ` [PATCH 1/2] [hack] reserve bit KVM_HINTS_HOST_PHYS_BITS Gerd Hoffmann
2022-08-31 13:05 ` Michael S. Tsirkin
2022-08-31 12:50 ` [PATCH 2/2] [RfC] expose host-phys-bits to guest Gerd Hoffmann
2022-08-31 12:58 ` Claudio Fontana
2022-09-01 6:07 ` [PATCH 0/2] " Xiaoyao Li
2022-09-01 13:58 ` Gerd Hoffmann
2022-09-01 14:36 ` Xiaoyao Li
2022-09-01 16:17 ` Gerd Hoffmann
2022-09-02 0:10 ` Xiaoyao Li
2022-09-02 6:07 ` Gerd Hoffmann
2022-09-02 6:35 ` Michael S. Tsirkin
2022-09-02 8:44 ` Gerd Hoffmann
2022-09-04 20:37 ` Michael S. Tsirkin
2022-09-05 7:39 ` Gerd Hoffmann
2022-09-01 14:55 ` Claudio Fontana
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=20220831125059.170032-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 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.