From: Borislav Petkov <bp@suse.de>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v4 6/8] [PATCH v4 6/8] Linux Patch #6
Date: Wed, 27 Jun 2018 18:44:14 +0200 [thread overview]
Message-ID: <20180627164414.GK24227@zn.tnic> (raw)
In-Reply-To: <20180623135445.864078699@localhost.localdomain>
On Sat, Jun 23, 2018 at 09:54:20AM -0400, speck for konrad.wilk_at_oracle.com wrote:
> x86/KVM/VMX: Seperate the VMX AUTOLOAD guest/host number accounting.
WARNING: 'Seperate' may be misspelled - perhaps 'Separate'?
>
> We can now load a different number of MSRs depending on if we are
> doing VMEXIT vs VMENTER.
>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
> arch/x86/kvm/vmx.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2018-06-27 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 13:54 [MODERATED] [PATCH v4 6/8] [PATCH v4 6/8] Linux Patch #6 konrad.wilk
2018-06-27 16:44 ` Borislav Petkov [this message]
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=20180627164414.GK24227@zn.tnic \
--to=bp@suse.de \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).