public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Duran, Leo" <leo.duran@amd.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ruiyu Ni <ruiyu.ni@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	 Liming Gao <liming.gao@intel.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH v5 1/2] UefiCpuPkg/SmmCpuFeaturesLib: Use global variables to replace macros
Date: Sun, 15 Oct 2017 17:26:04 +0200	[thread overview]
Message-ID: <f9a92ddc-1165-f2bf-4caf-3d6df4892d44@redhat.com> (raw)
In-Reply-To: <DM5PR12MB124386FFD07A26538747A26DF9490@DM5PR12MB1243.namprd12.prod.outlook.com>

On 14/10/2017 17:51, Duran, Leo wrote:
>>> +  // Override PSD offset for AMD
>>> +  //
>>> +  if (SmmStandardSignatureIsAuthenticAMD ()) {
>>> +    gStmPsdOffset = AMD_SMM_PSD_OFFSET;  }
>>> +
>> I think the right thing to do here would be to use the SMM state save map
>> revision; in the case of AMD, the low 16 bits (IIRC) would be 0x0064.
>>
> Hi Paolo,
> 
> In its current form, the patch merely replaces the macros with global
> variables, and does not attempt to disrupt the existing execution
> flow. But perhaps you can provide a bit more context (or an example)
> so that may better understand your suggestion?
The offsets don't really depend on Intel vs. AMD, but rather on the
version of the state save map.  QEMU and KVM for example always use the
AMD format because it's documented better (Intel doesn't document the
descriptor cache fields in the SDM), even if the CPUID vendor is
GenuineIntel.

I am not sure if you have the SMM state save map revision at this point
of the code, and likewise for 2/2.  But if you do, it would be much
nicer for us virtualization folks if you used it instead of CPUID to
pick the offsets.

Paolo


  reply	other threads:[~2017-10-15 15:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 19:45 [PATCH v5 0/2] Enhanced SMM support for AMD-based x86 systems Leo Duran
2017-10-11 19:45 ` [PATCH v5 1/2] UefiCpuPkg/SmmCpuFeaturesLib: Use global variables to replace macros Leo Duran
2017-10-12 21:40   ` Paolo Bonzini
2017-10-14 15:51     ` Duran, Leo
2017-10-15 15:26       ` Paolo Bonzini [this message]
2017-10-17 14:19   ` Duran, Leo
2017-10-17 14:23     ` Laszlo Ersek
2017-10-17 14:37       ` Paolo Bonzini
2017-10-17 14:50         ` Duran, Leo
2017-10-17 15:16           ` Paolo Bonzini
2017-10-17 14:50     ` Yao, Jiewen
2017-10-17 15:14       ` Laszlo Ersek
2017-10-17 16:40         ` Duran, Leo
2017-10-18  1:50         ` Yao, Jiewen
2017-10-18 14:36           ` Duran, Leo
2017-10-19  7:00             ` Laszlo Ersek
2017-10-19 17:02               ` Duran, Leo
2017-10-17 16:30       ` Duran, Leo
2017-10-11 19:45 ` [PATCH v5 2/2] UefiCpuPkg/PiSmmCpuDxeSmm: " Leo Duran
2017-10-13  1:52 ` [PATCH v5 0/2] Enhanced SMM support for AMD-based x86 systems Yao, Jiewen
2017-10-13  2:36   ` Yao, Jiewen
2017-10-14 16:04   ` Duran, Leo
2017-10-15  0:58     ` Yao, Jiewen
2017-10-16 17:06       ` Laszlo Ersek
2017-10-16 17:08         ` Paolo Bonzini
2017-10-16 17:31         ` Duran, Leo
2017-10-16 18:44           ` Laszlo Ersek
2017-10-16 18:56             ` Duran, Leo
2017-10-14 16:08   ` Duran, Leo
2017-10-16 17:13   ` 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-list 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=f9a92ddc-1165-f2bf-4caf-3d6df4892d44@redhat.com \
    --to=devel@edk2.groups.io \
    /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