From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "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 15:26:58 +0200 [thread overview]
Message-ID: <cef0da67-bdb6-234a-d928-532c8e10b599@redhat.com> (raw)
In-Reply-To: <071089ea-c73b-3851-899f-829bfe532867@redhat.com>
On 03/05/2017 15:14, Laszlo Ersek wrote:
> I'd prefer a solution that would keep the fw logic / code flow related
> to register configuration intact, and would just replace a few numbers /
> constants if possible.
I see. In my other answer I tried to keep it as intact as possible.
I'm a bit worried about the limits on the number of fw-cfg files.
Paolo
> And, whether the "largest TSEG size" (number of MBs) that QEMU exposed
> in the new fw_cfg file depended *only* on the machine type, or on other
> config elements as well (such as max VCPU count), that would be QEMU's
> prerogative of course.
>
> To me personally, the ability (via fw_cfg) to ask / request the
> following looks best:
>
> - Is there a dynamic largest? (= does the fw_cfg file exist?)
> - What is it exactly? (= what are its contents?)
> - Please give me it. (= write 11b)
next prev parent reply other threads:[~2017-05-03 13:27 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
2017-05-03 13:14 ` Laszlo Ersek
2017-05-03 13:26 ` Paolo Bonzini [this message]
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=cef0da67-bdb6-234a-d928-532c8e10b599@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