All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alok Kataria <akataria@vmware.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	kvm@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
	Gleb Natapov <gleb@kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	jmattson@vmware.com
Subject: Re: [PATCH v2] KVM: Synthesize G bit for all segments.
Date: Fri, 11 Jul 2014 09:09:57 +0200	[thread overview]
Message-ID: <53BF8DC5.8090201@redhat.com> (raw)
In-Reply-To: <1405062495.12694.7.camel@akataria-dtop.eng.vmware.com>

Il 11/07/2014 09:08, Alok Kataria ha scritto:
> +       /*
> +        * AMD CPUs circa 2014 track the G bit for all segments except CS.
> +        * However, the SVM spec states that the G bit is not observed by the
> +        * CPU, and some VMware virtual CPUs drop the G bit for all segments.
> +        * So let's synthesize a legal G bit for all segments, this helps
> +        * running KVM nested. It also helps cross-vendor migration, because
> +        * Intel's vmentry has a check on the 'G' bit.
> +        */

Good, I updated the patch.  I am picking it up.

Paolo

  reply	other threads:[~2014-07-11  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  7:08 [PATCH v2] KVM: Synthesize G bit for all segments Alok Kataria
2014-07-11  7:09 ` Paolo Bonzini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-07 10:38 [RFC PATCH] " Alok Kataria
2014-07-07 13:04 ` Paolo Bonzini
2014-07-08  4:17   ` [PATCH v2] " Alok Kataria
2014-07-10  8:55     ` Jan Kiszka
2014-07-10 12:27       ` 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=53BF8DC5.8090201@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=akataria@vmware.com \
    --cc=gleb@kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=jmattson@vmware.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=x86@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 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.