public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] nVMX: Keep arch.pat in sync on L1-L2 switches
Date: Mon, 05 Aug 2013 08:27:54 +0200	[thread overview]
Message-ID: <51FF45EA.9060405@web.de> (raw)
In-Reply-To: <CABpY8MJfq_vDDQf+Zcc=DdL9h9qU-hAHg4hoqSfP_5v=Jjr2Ag@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

On 2013-08-05 04:19, Arthur Chunqi Li wrote:
> On Sun, Aug 4, 2013 at 11:17 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> When asking vmx to load the PAT MSR for us while switching from L1 to L2
>> or vice versa, we have to update arch.pat as well as it may later be
>> used again to load or read out the MSR content.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Arthur, please add your tested-by also officially.
> This patch is generally good expect that we need to add
> VM_EXIT_LOAD_IA32_PAT/VM_EXIT_SAVE_IA32_PAT to
> nested_vmx_exit_ctls_high in function nested_vmx_setup_ctls_msrs() to
> enable these two features. Currently only VM_ENTRY_LOAD_IA32_PAT is
> enabled while all three are implemented.

Yes, feel free to follow up with a corresponding patch.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-08-05  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 15:17 [PATCH] nVMX: Keep arch.pat in sync on L1-L2 switches Jan Kiszka
2013-08-05  2:19 ` Arthur Chunqi Li
2013-08-05  6:27   ` Jan Kiszka [this message]
2013-08-05  8:40 ` Gleb Natapov
2013-08-06 10:45 ` Arthur Chunqi Li

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=51FF45EA.9060405@web.de \
    --to=jan.kiszka@web.de \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yzt356@gmail.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