From: Paolo Bonzini <pbonzini@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"Fan, Jeff" <jeff.fan@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>
Subject: Re: SMRAM sizes on large hosts
Date: Wed, 3 May 2017 14:56:57 +0200 [thread overview]
Message-ID: <49e28e04-2a61-c3d8-790a-3c08cf664a07@redhat.com> (raw)
In-Reply-To: <1493794647.8581.144.camel@redhat.com>
On 03/05/2017 08:57, Gerd Hoffmann wrote:
> qemu implements what physical q35 support. The extended smram register
> has two bits for the tseg size, three out of the four values are used
> (for 1, 2, 8 MB sizes). "11" is reserved in the specs. We could use
> "11" to implement a bigger tseg. Current code sets the tseg size to
> zero for "11". Alternatively we could add some qemu-specific register.
If you can set TSEG while SMRAM is closed, you could detect that in
edk2. According to Laszlo 32 MB should be more than enough, and we
could enable it only for >192 CPUs.
Paolo
> When implementing this in qemu we will have to do it runtime-switchable,
> for backward compatibility with older qemu versions. So ideally
> firmware would detect somehow whenever qemu supports a bigger tseg or
> not and adapt at runtime. If edk2 can't do this we would need two edk2
> builds ...
next prev parent reply other threads:[~2017-05-03 12:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 18:16 SMRAM sizes on large hosts Laszlo Ersek
2017-05-02 20:49 ` Kinney, Michael D
2017-05-03 1:20 ` Yao, Jiewen
2017-05-03 6:57 ` Gerd Hoffmann
2017-05-03 12:56 ` Paolo Bonzini [this message]
2017-05-03 13:14 ` Laszlo Ersek
2017-05-03 13:26 ` Paolo Bonzini
2017-05-03 13:35 ` Laszlo Ersek
2017-05-03 13:55 ` Paolo Bonzini
2017-05-03 22:34 ` Laszlo Ersek
2017-05-03 12:58 ` Laszlo Ersek
2017-05-03 13:44 ` Gerd Hoffmann
2017-05-03 22:33 ` Laszlo Ersek
2017-05-03 23:36 ` Laszlo Ersek
2017-05-04 6:18 ` Gerd Hoffmann
2017-05-04 14:52 ` Gerd Hoffmann
2017-05-04 15:21 ` Laszlo Ersek
2017-05-04 8:23 ` Igor Mammedov
2017-05-04 11:34 ` Laszlo Ersek
2017-05-04 14:00 ` Igor Mammedov
2017-05-04 14:41 ` Gerd Hoffmann
2017-05-04 14:50 ` Igor Mammedov
2017-05-04 15:19 ` Laszlo Ersek
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=49e28e04-2a61-c3d8-790a-3c08cf664a07@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