From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>,
Feng Tian <feng.tian@intel.com>,
edk2-devel@ml01.01.org,
Michael D Kinney <michael.d.kinney@intel.com>,
Jeff Fan <jeff.fan@intel.com>, Star Zeng <star.zeng@intel.com>
Subject: Re: [PATCH V2 0/6] Enable SMM page level protection.
Date: Thu, 10 Nov 2016 11:39:21 -0500 (EST) [thread overview]
Message-ID: <1042282326.11988922.1478795961783.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <305270ae-51ee-07ba-fb6b-1d66cc5ba8fc@redhat.com>
> And, in my recent KVM / QEMU usage instructions for Jiewen:
>
> https://www.mail-archive.com/edk2-devel@lists.01.org/msg19446.html
>
> I provided the following settings:
>
> > # Settings for Ia32 only:
> > [...]
> > QEMU_COMMAND="qemu-system-i386 -cpu coreduo,-nx"
> >
> > # Settings for Ia32X64 only:
> > [...]
> > QEMU_COMMAND=qemu-system-x86_64
>
> I guess the "-nx" bit can be left off with TCG, but AFAIR it is required
> for KVM.
Oh right now I remember. The same problem exists: EFER is not saved in the
32-bit state save map. AFAIK all processors with XD also have long mode.
That said, qemu-system-x86_64 and no -cpu option should work even with Ia32
PEI/DXE/SMM and no -cpu option. In that case you could use XD.
Now if only Intel made the *full* format of the state save map public, we
could emulate everything more accurately... I'm told it's in the BIOS
writers guide.
Paolo
next prev parent reply other threads:[~2016-11-10 16:39 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
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 [this message]
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=1042282326.11988922.1478795961783.JavaMail.zimbra@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