From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, "Fan, Jeff" <jeff.fan@intel.com>
Cc: "edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path
Date: Mon, 14 Nov 2016 13:00:48 +0100 [thread overview]
Message-ID: <648314a4-6c17-7c88-7e47-98c4de95fe2d@redhat.com> (raw)
In-Reply-To: <3e61ffc4-9eaf-0015-11a7-e2d698624acb@redhat.com>
On 14/11/2016 12:27, Laszlo Ersek wrote:
> Well...
>
> http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05658.html
> http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg00125.html
> http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg00563.html
>
> Are you suggesting that I resurrect this patch? That would be my
> pleasure. Please say yes.
It's hard to say no when someone has written the code already. :)
Paolo
> Also, no special handling would be necessary on the S3 resume path,
> because after resume, SMM clients like the variable driver would
> continue calling the Trigger() method. SmmControl2Dxe is a Runtime
> DXE Driver. The OVMF side patch looks like this (I think I never
> posted it, but I preserved it):
next prev parent reply other threads:[~2016-11-14 12:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 5:45 [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path Jeff Fan
2016-11-11 5:45 ` [PATCH v2 1/3] UefiCpuPkg/PiSmmCpuDxeSmm: " Jeff Fan
2016-11-11 5:45 ` [PATCH v2 2/3] UefiCpuPkg/PiSmmCpuDxeSmm: Place AP to 32bit protected mode " Jeff Fan
2016-11-11 5:45 ` [PATCH v2 3/3] UefiCpuPkg/PiSmmCpuDxeSmm: Decrease mNumberToFinish in AP safe code Jeff Fan
2016-11-11 10:16 ` Paolo Bonzini
2016-11-11 19:49 ` [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path Laszlo Ersek
2016-11-13 12:51 ` Fan, Jeff
2016-11-14 1:41 ` Yao, Jiewen
2016-11-14 8:17 ` Laszlo Ersek
2016-11-14 8:50 ` Paolo Bonzini
2016-11-14 10:39 ` Laszlo Ersek
2016-11-14 11:09 ` Paolo Bonzini
2016-11-14 11:27 ` Laszlo Ersek
2016-11-14 12:00 ` Paolo Bonzini [this message]
2016-11-14 18:07 ` Laszlo Ersek
2016-11-14 18:13 ` Paolo Bonzini
2016-11-14 23:56 ` Laszlo Ersek
2016-11-15 0:47 ` Fan, Jeff
2016-11-15 1:03 ` Laszlo Ersek
2016-11-15 1:04 ` Fan, Jeff
2016-11-15 1:19 ` Fan, Jeff
2016-11-15 1:30 ` Laszlo Ersek
2016-11-15 1:27 ` Laszlo Ersek
2016-11-15 1:38 ` Fan, Jeff
[not found] ` <542CF652F8836A4AB8DBFAAD40ED192A4A2DCDE3@shsmsx102.ccr.corp.intel.com>
2016-11-15 1:21 ` Yao, Jiewen
2016-11-15 1:24 ` Fan, Jeff
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=648314a4-6c17-7c88-7e47-98c4de95fe2d@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