kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Mattson <jmattson@google.com>
To: kvm@vger.kernel.org
Cc: Jim Mattson <jmattson@google.com>
Subject: [PATCH 0/3] Reduce the size of the vmcs_field_to_offset_table
Date: Thu, 21 Dec 2017 12:46:20 -0800	[thread overview]
Message-ID: <20171221204623.164581-1-jmattson@google.com> (raw)


The vmcs_field_to_offset_table is quite sparse, with its size determined
by the highest VMCS field encoding (0x6c16 for HOST_RIP). To support multiple
VMCS12 formats, we will need multiple vmcs_field_to_offset_tables, and
it would be a shame to replicate this sparse table.

Jim Mattson (3):
  kvm: vmx: Introduce VMCS12_MAX_FIELD_INDEX
  kvm: vmx: Change vmcs_field_type to vmcs_field_width
  kvm: vmx: Reduce size of vmcs_field_to_offset_table

 arch/x86/kvm/vmx.c | 197 +++++++++++++++++++++++++++++++----------------------
 1 file changed, 117 insertions(+), 80 deletions(-)

-- 
2.15.1.620.gb9897f4670-goog

             reply	other threads:[~2017-12-21 20:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 20:46 Jim Mattson [this message]
2017-12-21 20:46 ` [PATCH 1/3] kvm: vmx: Introduce VMCS12_MAX_FIELD_INDEX Jim Mattson
2017-12-22 20:11   ` [PATCH v2 " Jim Mattson
2018-01-18 16:46     ` David Hildenbrand
2017-12-21 20:46 ` [PATCH 2/3] kvm: vmx: Change vmcs_field_type to vmcs_field_width Jim Mattson
2017-12-22 20:12   ` [PATCH v2 " Jim Mattson
2017-12-21 20:46 ` [PATCH 3/3] kvm: vmx: Reduce size of vmcs_field_to_offset_table Jim Mattson
2017-12-22 16:26   ` Paolo Bonzini
2017-12-22 18:28     ` Jim Mattson
2017-12-22 20:13       ` [PATCH v2 " Jim Mattson
2017-12-22 20:09 ` [PATCH v2 0/3] Reduce the size of the vmcs_field_to_offset_table Jim Mattson
2018-01-01 22:55   ` Paolo Bonzini

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=20171221204623.164581-1-jmattson@google.com \
    --to=jmattson@google.com \
    --cc=kvm@vger.kernel.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).