qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 00/17] pci: switch a ton of drivers to symbolic names
Date: Thu, 10 Dec 2009 20:09:39 +0200	[thread overview]
Message-ID: <20091210180939.GA25707@redhat.com> (raw)

The recent e1000 bug made the important of using
symbolic macros for pci config access clear for me.
So I started going over drivers and converting
to symbolic constants instead of hard-coded ones.
I did a large part until I run out of steam.
Maybe some brave soul will take up converting
the rest of them, or maybe I will: note that
when converting bridges one should be careful
to use bridge macros where appropriate.

Instead of testing a huge number of configurations,
I compared binaries before and after conversion.
Almost all of them generate exact same stripped binary
before and after the change.
The only object changed was eepro100, objdump showed
that the change was because gcc for some reason
decides to use a bit more stack for init function
after comments are added there.

This methodology was the reason that I added TODOs where I saw
deviations from spec or other code ugliness, will have to be fixed
separately.

I also verified separately that eepro100 still works
and survives light usage.

This patcheset applies on top of e1000 bugfix
I have posted previously.

Michael S. Tsirkin (17):
  e1000: switch to symbolic names for pci registers
  ne2000: switch to symbolic names for pci registers
  rtl: switch to symbolic names for pci registers
  pcnet: switch to symbolic names for pci registers
  pci: add more status bits
  eepro100: symbolic names for pci registers
  piix: symbolic constants
  cmd646: symbolic names for pci registers
  vmware_vga: symbolic names for pci registers
  lsi: symbolic names for pci registers
  pci: add another devsel macro
  es1370: symbolic names for pci registers
  wdt_i6300esb: symbolic names for pci registers
  ac97: symbolic names for pci registers
  usb-uhci: symbolic names for pci registers
  usb-uhci: symbolic names for pci registers
  pci: remove unused macro

 hw/ac97.c         |   57 ++++++++++++++++++++++++++++------------------------
 hw/e1000.c        |   11 ++++++---
 hw/eepro100.c     |   49 +++++++++++++++++++++++++++++---------------
 hw/es1370.c       |   29 ++++++++++++++-------------
 hw/ide/cmd646.c   |    7 +++--
 hw/ide/piix.c     |   13 +++++++----
 hw/lsi53c895a.c   |   10 +++++---
 hw/ne2000.c       |    3 +-
 hw/pci.h          |    5 +++-
 hw/pcnet.c        |   26 +++++++++++++++--------
 hw/rtl8139.c      |   16 +++++++++-----
 hw/usb-ohci.c     |    6 +++-
 hw/usb-uhci.c     |    7 +++--
 hw/vmware_vga.c   |   20 ++++++++++--------
 hw/wdt_i6300esb.c |    2 +-
 15 files changed, 156 insertions(+), 105 deletions(-)

             reply	other threads:[~2009-12-10 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 18:09 Michael S. Tsirkin [this message]
2009-12-10 18:17 ` [Qemu-devel] [PATCH 00/17] pci: switch a ton of drivers to symbolic names Glauber Costa
2009-12-10 18:28 ` Paul Brook
2009-12-11 10:26   ` Michael S. Tsirkin
2009-12-12 15:46 ` [Qemu-devel] " Juan Quintela

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=20091210180939.GA25707@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).