From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: imammedo@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Fri, 16 Aug 2019 04:24:15 -0700 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 699E9308212F; Fri, 16 Aug 2019 11:24:14 +0000 (UTC) Received: from dell-r430-03.lab.eng.brq.redhat.com (dell-r430-03.lab.eng.brq.redhat.com [10.37.153.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3A12A43FF3; Fri, 16 Aug 2019 11:24:12 +0000 (UTC) From: Igor Mammedov To: qemu-devel@nongnu.org Cc: "Chen, Yingwen" , edk2-devel-groups-io , Phillip Goerl , "Yao, Jiewen" , "Nakajima, Jun" , Boris Ostrovsky , edk2-rfc-groups-io , Laszlo Ersek , Joao Marcal Lemos Martins , pbonzini@redhat.com Subject: [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 Message-Id: <20190816112407.28180-1-imammedo@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.47]); Fri, 16 Aug 2019 11:24:14 +0000 (UTC) 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" CC: edk2-devel-groups-io CC: Phillip Goerl CC: qemu devel list CC: "Yao, Jiewen" CC: "Nakajima, Jun" CC: Boris Ostrovsky CC: edk2-rfc-groups-io CC: Laszlo Ersek CC: Joao Marcal Lemos Martins 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