From: Paolo Bonzini <pbonzini@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>, Laszlo Ersek <lersek@redhat.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Tian, Feng" <feng.tian@intel.com>,
"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
"Zeng, Star" <star.zeng@intel.com>,
"Fan, Jeff" <jeff.fan@intel.com>
Subject: Re: [PATCH V2 0/6] Enable SMM page level protection.
Date: Wed, 9 Nov 2016 17:06:18 +0100 [thread overview]
Message-ID: <0844819f-6e5a-ece1-7ca6-68b61e71c737@redhat.com> (raw)
In-Reply-To: <3be2f1bf-8c0a-e470-a5c0-a6130b159da5@redhat.com>
On 09/11/2016 16:54, Paolo Bonzini wrote:
>> > and 2) AP is in protected mode with paging disabled.
> It is not clear to me what the (4) SIPI done is there for, and why it is
> triggered in S3Resume.c rather than CpuS3.c. And why does it take so
> much for APs to complete it?
SMI of course, not SIPI.
Paolo
next prev parent reply other threads:[~2016-11-09 16:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 9:30 [PATCH V2 0/6] Enable SMM page level protection Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 1/6] MdeModulePkg/Include: Add PiSmmMemoryAttributesTable.h Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 2/6] MdeModulePkg/dec: Add gEdkiiPiSmmMemoryAttributesTableGuid Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 3/6] MdeModulePkg/PiSmmCore: Add MemoryAttributes support Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 4/6] UefiCpuPkg/dec: Add PcdCpuSmmStaticPageTable Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 5/6] UefiCpuPkg/PiSmmCpuDxeSmm: Add paging protection Jiewen Yao
2016-11-04 9:30 ` [PATCH V2 6/6] QuarkPlatformPkg/dsc: enable Smm " Jiewen Yao
2016-11-04 22:40 ` [PATCH V2 0/6] Enable SMM page level protection Laszlo Ersek
2016-11-04 22:46 ` Yao, Jiewen
2016-11-04 23:08 ` Laszlo Ersek
2016-11-08 1:22 ` Laszlo Ersek
2016-11-08 12:59 ` Yao, Jiewen
2016-11-08 13:22 ` Laszlo Ersek
2016-11-08 13:41 ` Yao, Jiewen
2016-11-09 6:25 ` Yao, Jiewen
2016-11-09 11:30 ` Paolo Bonzini
2016-11-09 15:01 ` Yao, Jiewen
2016-11-09 15:54 ` Paolo Bonzini
2016-11-09 16:06 ` Paolo Bonzini [this message]
2016-11-09 22:28 ` Laszlo Ersek
2016-11-09 22:59 ` Paolo Bonzini
2016-11-09 23:27 ` Laszlo Ersek
2016-11-10 1:13 ` Yao, Jiewen
2016-11-10 6:30 ` Fan, Jeff
2016-11-10 0:49 ` Yao, Jiewen
2016-11-10 0:50 ` Yao, Jiewen
2016-11-10 1:02 ` Fan, Jeff
2016-11-09 20:46 ` Laszlo Ersek
2016-11-10 10:41 ` Yao, Jiewen
2016-11-10 12:01 ` Laszlo Ersek
2016-11-10 14:48 ` Yao, Jiewen
2016-11-10 14:53 ` Paolo Bonzini
2016-11-10 16:22 ` Laszlo Ersek
2016-11-10 16:39 ` Paolo Bonzini
2016-11-10 16:25 ` Laszlo Ersek
2016-11-10 12:27 ` Paolo Bonzini
2016-11-09 11:23 ` Paolo Bonzini
2016-11-09 15:16 ` Yao, Jiewen
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=0844819f-6e5a-ece1-7ca6-68b61e71c737@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