From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] q35/mch: implement extended TSEG sizes
Date: Fri, 16 Jun 2017 06:23:59 +0300 [thread overview]
Message-ID: <20170616062332-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1497510465.5952.1.camel@redhat.com>
On Thu, Jun 15, 2017 at 09:07:45AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > To be specific, what I meant is a bit that tells guest that a
> > config space register is available, and lets host find out
> > that guest is going to use it.
> >
> > This to ensure full forward and backward compatibility.
> >
> > I agree a fw cfg file for a single bit seems like an overkill, that's
> > why I thought sharing feature files with SMI would be a good idea.
> >
> > Do you see an issue with that?
>
> The point of placing the extended-tseg-size register in mch pci config
> is that the firmware can figure this easily *without* looking somewhere
> else, as all the other tseg (and smram) config bits are in mch pci
> config space too.
>
> When involving fw_cfg there is no reason to keep the extended-tseg-size
> register in mch. We can simply place a "etc/q35-extended-tseg-size"
> file in fw_cfg then (which is either not present or contains the
> extended tseg size). So a feature bit in fw_cfg looks absolutely
> pointless to me.
>
> I still think the approach and patch by Laszlo is perfectly fine.
> While being at it:
>
> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>
> cheers,
> Gerd
I guess I'll merge it and we'll see if there's any fallout.
Thanks everyone.
--
MST
prev parent reply other threads:[~2017-06-16 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 16:10 [Qemu-devel] [PATCH] q35/mch: implement extended TSEG sizes Laszlo Ersek
2017-06-08 16:34 ` Paolo Bonzini
2017-06-08 18:31 ` Laszlo Ersek
2017-06-08 17:41 ` Michael S. Tsirkin
2017-06-08 19:48 ` Gerd Hoffmann
2017-06-08 19:55 ` Michael S. Tsirkin
2017-06-08 23:01 ` Laszlo Ersek
2017-06-09 0:19 ` Michael S. Tsirkin
2017-06-09 17:41 ` Laszlo Ersek
2017-06-09 11:40 ` Paolo Bonzini
2017-06-09 20:01 ` Gerd Hoffmann
2017-06-14 18:25 ` Michael S. Tsirkin
2017-06-15 7:07 ` Gerd Hoffmann
2017-06-16 3:23 ` Michael S. Tsirkin [this message]
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=20170616062332-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.