qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vfio/igd: handle q35 machine type
Date: Wed, 09 Mar 2016 09:03:57 +0100	[thread overview]
Message-ID: <1457510637.676.15.camel@redhat.com> (raw)
In-Reply-To: <20160308081533.57e0fa8d@t450s.home>

  Hi,

> > q35 already has a isa bridge @ 1f.0, and it's not a dummy device but
> > emulates the ich9 lpc.  Just overwriting the identity of that device
> > isn't a good idea I think.
> 
> It's not a good idea in practice or in theory?  It's exactly what we're
> proposing to do for the host bridge.

We don't change the pci ids for the host bridge.  It's still a
i440fx/q35 host bridge, only the subsystem ID is changed (although I'm
sometimes wondering why), and the gfx registers added of course.

> Do we know for certain that any of
> the emulated ich9 registers do not align with newer chipsets?

See drivers/mfd/lpc_ich.c (lpc_chipset_info array).

Lots of different versions exist for GPIO wiring.  Which probably isn't
that much of a problem as I think we don't emulate gpio.

For iTCO there are tree different versions too, and we *do* emulate
that.

> It seems
> quite limiting of igd assignment on q35 VMs if we're going to remove
> collateral device modification.  Should we only claim "legacy" igd
> support on 440FX and support only universal passthrough on q35?  Thanks,

I'll go test this a bit more.  Possibly we can drop the whole lpc
tweaking.  At least when looking at the linux driver code it doesn't
seem to be very important.

cheers,
  Gerd

  reply	other threads:[~2016-03-09  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  8:41 [Qemu-devel] [PATCH v2] vfio/igd: handle q35 machine type Gerd Hoffmann
2016-03-07 21:41 ` Alex Williamson
2016-03-08  8:04   ` Gerd Hoffmann
2016-03-08 15:15     ` Alex Williamson
2016-03-09  8:03       ` Gerd Hoffmann [this message]
2016-03-09 15:00         ` Gerd Hoffmann
2016-03-10  5:49           ` [Qemu-devel] [iGVT-g] " Tian, Kevin
2016-03-09 15:02         ` [Qemu-devel] " Gerd Hoffmann

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=1457510637.676.15.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alex.williamson@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).