From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Chen, Yingwen" <yingwen.chen@intel.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
Phillip Goerl <phillip.goerl@oracle.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
pbonzini@redhat.com, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
edk2-rfc-groups-io <rfc@edk2.groups.io>,
Laszlo Ersek <lersek@redhat.com>,
Joao Marcal Lemos Martins <joao.m.martins@oracle.com>
Subject: [Qemu-devel] [POC QEMU PATCH 0/2] CPU hotplug: use dedicated SMRAM at 0x30000 in SMM address space
Date: Fri, 16 Aug 2019 07:24:05 -0400 [thread overview]
Message-ID: <20190816112407.28180-1-imammedo@redhat.com> (raw)
It's just a quick hack together with Seabios to show
that normal RAM at 0x30000 is not affected by SMM relocation
and dedicated SMRAM could be used for relocation without need to
care about untrusted RAM content at 0x30000.
CC: "Chen, Yingwen" <yingwen.chen@intel.com>
CC: edk2-devel-groups-io <devel@edk2.groups.io>
CC: Phillip Goerl <phillip.goerl@oracle.com>
CC: qemu devel list <qemu-devel@nongnu.org>
CC: "Yao, Jiewen" <jiewen.yao@intel.com>
CC: "Nakajima, Jun" <jun.nakajima@intel.com>
CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
CC: edk2-rfc-groups-io <rfc@edk2.groups.io>
CC: Laszlo Ersek <lersek@redhat.com>
CC: Joao Marcal Lemos Martins <joao.m.martins@oracle.com>
CC: pbonzini@redhat.com
include/hw/pci-host/q35.h | 1 +
hw/pci-host/q35.c | 10 ++++++++++
2 files changed, 11 insertions(+)
--
2.18.1
next reply other threads:[~2019-08-16 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 11:24 Igor Mammedov [this message]
2019-08-16 11:24 ` [Qemu-devel] [PATCH QEMU 1/1] q35: use dedicated SMRAM at default SMM_BASE Igor Mammedov
2019-08-16 11:24 ` [Qemu-devel] [POC Seabios PATCH] seabios: use isolated SMM address space for relocation Igor Mammedov
2019-08-16 22:43 ` Boris Ostrovsky
2019-08-26 13:57 ` Igor Mammedov
2019-08-27 1:28 ` Boris Ostrovsky
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=20190816112407.28180-1-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=devel@edk2.groups.io \
--cc=jiewen.yao@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=jun.nakajima@intel.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=phillip.goerl@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=rfc@edk2.groups.io \
--cc=yingwen.chen@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).