qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian Herbszt" <herbszt@gmx.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] piix: use pci_config_set_prog_interface()
Date: Tue, 28 Dec 2010 19:48:23 +0100	[thread overview]
Message-ID: <DA6C395899B14F2B8FD31E37B7EA0D8A@FSCPC> (raw)
In-Reply-To: <20101228171955.GA2850@redhat.com>

Michael S. Tsirkin wrote:
> On Tue, Dec 28, 2010 at 05:24:06PM +0100, Sebastian Herbszt wrote:
>> Michael S. Tsirkin wrote:
>> >On Mon, Dec 20, 2010 at 10:18:01PM +0100, Sebastian Herbszt wrote:
>> >>Use pci_config_set_prog_interface().
>> >>
>> >>Signed-off-by: Sebastian Herbszt <herbszt@gmx.de>
>> >
>> >Since I was asked explicitly - I don't have a problem
>> >with these changes: both class and prog interface.
>> >However, they aren't all that useful in themselves.
>> >
>> >For class, what I would like to see is a system where
>> >the device class is put in the qdev info table,
>> >and where -device ?
>> >(and hopefully the legacy -help, -nic etc as well)
>> >use this information.
>> 
>> I am not sure if you mean something like the patch below.
> 
> Not exactly
> 
> - I'd like to keep the pci_config_set_class in the devices,
>  just make it do an assert.

Assert on which condition?

> - Nics already have DEFINE_NIC_PROPERTIES - can this be used somehow?
>  Same for other devices ...

We got DEFINE_NIC_PROPERTIES and DEFINE_BLOCK_PROPERTIES.
Something like DEFINE_PCI_PROPERTIES could be introduced, but i am not sure
which device properties it should hold (vendor_id, device_id, class, etc?).
Those will then be user-modifiable with e.g. -device e1000,pci_class=1234.

Sebastian

diff --git a/hw/e1000.c b/hw/e1000.c
index af101bd..e302703 100644
--- a/hw/e1000.c
+++ b/hw/e1000.c
@@ -1171,6 +1171,7 @@ static PCIDeviceInfo e1000_info = {
     .romfile    = "pxe-e1000.bin",
     .qdev.props = (Property[]) {
         DEFINE_NIC_PROPERTIES(E1000State, conf),
+        DEFINE_PROP_UINT16("pci_class", E1000State, dev.class, PCI_CLASS_NETWORK_ETHERNET),
         DEFINE_PROP_END_OF_LIST(),
     }
 };
diff --git a/hw/pci.c b/hw/pci.c
index ef00d20..06bbf04 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -1620,6 +1620,9 @@ static int pci_qdev_init(DeviceState *qdev, DeviceInfo *base)
                                      info->is_bridge);
     if (pci_dev == NULL)
         return -1;
+
+    pci_config_set_class(pci_dev->config, pci_dev->class);
+
     rc = info->init(pci_dev);
     if (rc != 0) {
         do_pci_unregister_device(pci_dev);
diff --git a/hw/pci.h b/hw/pci.h
index 17744dc..5dc9053 100644
--- a/hw/pci.h
+++ b/hw/pci.h
@@ -189,6 +189,9 @@ struct PCIDevice {
     char *romfile;
     ram_addr_t rom_offset;
     uint32_t rom_bar;
+
+    /* class */
+    uint16_t class;
 };

 PCIDevice *pci_register_device(PCIBus *bus, const char *name,

  reply	other threads:[~2010-12-28 18:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 21:18 [Qemu-devel] [PATCH] piix: use pci_config_set_prog_interface() Sebastian Herbszt
2010-12-27 14:01 ` [Qemu-devel] " Michael S. Tsirkin
2010-12-28 16:24   ` Sebastian Herbszt
2010-12-28 17:19     ` Michael S. Tsirkin
2010-12-28 18:48       ` Sebastian Herbszt [this message]
2010-12-28 21:08         ` Michael S. Tsirkin
2010-12-29 10:26           ` Sebastian Herbszt
2010-12-29 11:21             ` Michael S. Tsirkin
2010-12-29 14:55             ` 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=DA6C395899B14F2B8FD31E37B7EA0D8A@FSCPC \
    --to=herbszt@gmx.de \
    --cc=mst@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).