From: "M. Warner Losh" <imp@bsdimp.com>
To: mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com, avi@redhat.com,
mst@redhat.com
Subject: Re: [Qemu-devel] Re: questions on default_config_write in hw/pci.c
Date: Thu, 30 Apr 2009 11:28:20 -0600 (MDT) [thread overview]
Message-ID: <20090430.112820.48552365.imp@bsdimp.com> (raw)
In-Reply-To: <20090430171526.GA10638@amt.cnet>
In message: <20090430171526.GA10638@amt.cnet>
Marcelo Tosatti <mtosatti@redhat.com> writes:
: On Thu, Apr 30, 2009 at 07:15:08PM +0300, Michael S. Tsirkin wrote:
: > Hi,
: > I've been looking at hw/pci.c, specifically at how config
: > read/write are implemented, and have a couple of questions
: > about default_config_write:
: >
: > 1. The code at the beginning (if len == 4 ...)
: > seems to only update pci base registers if a dword write
: > is performed. I think it's legal for the guest to perform 4
: > single-byte writes. Should this be supported?
: >
: > 2. The large switch statement at the end of this function
: > uses hard-coded register offsets. Would it make sense
: > to change it to use macros from hw/pci.h?
: >
: > 3. Still there I see:
: > switch(d->config[0x0e]) {
: > case 0x00:
: > case 0x80:
: > register 0x0e is header type, which has defined values
: > of 0x00 (device or host bridge), 0x01 (pci to pci bridge) and
: > 0x02 (cardbus bridge). What is 0x80 and when is it used?
: > Would it make sense to remove this?
:
: Don't know. Check the PCI spec?
The above is a bug. 0x80 is a bit that says "I have multiple
functions" and is orthogonal to the type of device.
: > switch(d->config[0x0e]) {
should be
switch(d->config[0x0e] & 0x7f) {
: > 4. Still there, there's some handling done for type 1 devices.
: > This support seems imcomplete.
: > Are there any PCI-to-PCI bridges emulated by qemu?
: > Would it make sense to remove this code?
:
:
: It did work at one point:
:
: http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg16647.html
I have vague plans to do Cardbus-to-PCI bridge at some point...
Warner
next prev parent reply other threads:[~2009-04-30 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 16:15 [Qemu-devel] questions on default_config_write in hw/pci.c Michael S. Tsirkin
2009-04-30 16:35 ` [Qemu-devel] " Anthony Liguori
2009-04-30 17:15 ` Marcelo Tosatti
2009-04-30 17:28 ` M. Warner Losh [this message]
2009-04-30 17:33 ` Michael S. Tsirkin
2009-04-30 17:29 ` Michael S. Tsirkin
2009-04-30 17:45 ` Anthony Liguori
2009-04-30 19:26 ` Marcelo Tosatti
2009-05-01 4:50 ` M. Warner Losh
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=20090430.112820.48552365.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@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).