qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: qemu devel list <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] q35/mch: implement extended TSEG sizes
Date: Thu, 08 Jun 2017 21:48:53 +0200	[thread overview]
Message-ID: <1496951333.29761.5.camel@redhat.com> (raw)
In-Reply-To: <20170608204026-mutt-send-email-mst@kernel.org>

  Hi,

> I really dislike negotiation being re-invented for each device.  Do
> we
> need these tricks?  Can we just do fw cfg with standard discovery?
> This ties in with my proposal to generalize smi features to
> generic ones.

Device properties should be part of the device.
We should have done this with the smi too.

A more standard way to handle this would be to add a vendor-specific
pci capability and place the register there.  Not sure we have room for
that in the pci config space though.

cheers,
  Gerd

  reply	other threads:[~2017-06-08 19:49 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 [this message]
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

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=1496951333.29761.5.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).