public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Like Xu <like.xu@linux.intel.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Add Intel CPUID.1F cpuid emulation support
Date: Mon, 22 Apr 2019 09:56:15 -0700	[thread overview]
Message-ID: <20190422165615.GD1236@linux.intel.com> (raw)
In-Reply-To: <20190422155333.GB32647@char.us.oracle.com>

On Mon, Apr 22, 2019 at 11:53:33AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Apr 22, 2019 at 02:40:34PM +0800, Like Xu wrote:
> > Expose Intel V2 Extended Topology Enumeration Leaf to guest only when
> > host system has multiple software-visible die within each package.
> 
> Is there some doc on this?

It's in recent versions of the SDM, in the massive "Information Returned
by CPUID Instruction" table.

  reply	other threads:[~2019-04-22 17:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  6:40 [PATCH] KVM: x86: Add Intel CPUID.1F cpuid emulation support Like Xu
2019-04-22 15:53 ` Konrad Rzeszutek Wilk
2019-04-22 16:56   ` Sean Christopherson [this message]
2019-04-22 18:35 ` Sean Christopherson
2019-04-23  3:23   ` Like Xu
2019-04-23 17:44     ` Sean Christopherson
2019-04-24  1:59       ` Like Xu
2019-04-24 13:53         ` Sean Christopherson
2019-04-24 14:32 ` Sean Christopherson
2019-04-25  2:58   ` Like Xu
2019-04-25  4:18     ` Xiaoyao Li
2019-04-25  6:02       ` Like Xu
2019-04-25  6:30         ` Xiaoyao Li
2019-04-25  7:07           ` Like Xu
2019-04-25 14:19             ` Sean Christopherson
2019-04-25 15:33               ` Like Xu
2019-04-25 16:28                 ` Xiaoyao Li
2019-04-26  1:30                   ` Like Xu

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=20190422165615.GD1236@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=like.xu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=tglx@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