From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC] q35/mch: implement extended TSEG sizes
Date: Wed, 07 Jun 2017 07:52:50 +0200 [thread overview]
Message-ID: <1496814770.5126.1.camel@redhat.com> (raw)
In-Reply-To: <20170530212614.18343-1-lersek@redhat.com>
Hi,
Patch looks sane overall.
> Invent a new, QEMU-specific register in the config space of the DRAM
> Controller, at offset 0x50, in order to allow guest firmware to query
> the
> TSEG (SMRAM) size.
Hmm, 0x50 appears to be the only unused config space register in the
specs. I suspect in reality it isn't unused but undocumented. I don't
have a better idea though, and in practice it probably isn't much of a
problem.
cheers,
Gerd
next prev parent reply other threads:[~2017-06-07 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 21:26 [Qemu-devel] [RFC] q35/mch: implement extended TSEG sizes Laszlo Ersek
2017-06-06 16:58 ` Laszlo Ersek
2017-06-07 5:52 ` Gerd Hoffmann [this message]
2017-06-07 9:01 ` 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-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=1496814770.5126.1.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).