qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH 2/4] qemu: make default_write_config use mask table
Date: Wed, 13 May 2009 11:45:06 +0300	[thread overview]
Message-ID: <20090513084506.GB31593@redhat.com> (raw)
In-Reply-To: <20090513082746.GJ22497%yamahata@valinux.co.jp>

On Wed, May 13, 2009 at 05:27:46PM +0900, Isaku Yamahata wrote:
> On Wed, May 13, 2009 at 11:07:24AM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 13, 2009 at 04:50:50PM +0900, Isaku Yamahata wrote:
> > > Change much of hw/pci to use symbolic constants and a table-driven
> > > design: add a mask table with writable bits set and readonly bits unset.
> > > Detect change by comparing original and new registers.
> > > 
> > > As a result, writing a single byte in BAR registers now works as it
> > > should. Writing to upper limit registers in the bridge also works as it
> > > should. Writes to BAR registers trigger mapping update.  Code is also
> > > shorter.
> > > 
> > > Changelog since v1
> > > - simplify the code some more
> > > - use PCI_CONFIG_SPACE_SIZE instead of 0x100
> > > - only trigger pci update when IO/MEM bits in command register have changed
> > > 
> > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > 
> > You must also add
> > From: Michael S. Tsirkin <mst@redhat.com>
> > 
> > at the top, otherwise git won't record the authorship
> > information in log correctly.
> 
> Oh sorry, does this looks okay?
> 
> From: Michael S. Tsirkin <mst@redhat.com>
> 
> Change much of hw/pci to use symbolic constants and a table-driven
> design: add a mask table with writable bits set and readonly bits unset.
> Detect change by comparing original and new registers.
> 
> As a result, writing a single byte in BAR registers now works as it
> should. Writing to upper limit registers in the bridge also works as it
> should. Writes to BAR registers trigger mapping update.  Code is also
> shorter.
> 
> Changelog since v1
> - simplify the code some more
> - use PCI_CONFIG_SPACE_SIZE instead of 0x100
> - only trigger pci update when IO/MEM bits in command register have changed
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>  hw/pci.c |  147 +++++++++++++-------------------------------------------------
>  hw/pci.h |   18 +++++++-
>  2 files changed, 47 insertions(+), 118 deletions(-)
> 

Right. But Changelog should come after ---: you want git to ignore it.

-- 
MST

  reply	other threads:[~2009-05-13  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13  7:50 [Qemu-devel] [PATCH 0/4] pci config space emulation clean up TAKE 4 Isaku Yamahata
2009-05-13  7:50 ` [Qemu-devel] [PATCH 1/4] vmware_vga: clean up Isaku Yamahata
2009-05-13  7:50 ` [Qemu-devel] [PATCH 2/4] qemu: make default_write_config use mask table Isaku Yamahata
2009-05-13  8:07   ` [Qemu-devel] " Michael S. Tsirkin
2009-05-13  8:27     ` Isaku Yamahata
2009-05-13  8:45       ` Michael S. Tsirkin [this message]
2009-05-13  7:50 ` [Qemu-devel] [PATCH 3/4] pci: pci_default_config_write() clean up Isaku Yamahata
2009-05-13  7:50 ` [Qemu-devel] [PATCH 4/4] pci/config: convert pci configuration space handler to use callback Isaku Yamahata

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=20090513084506.GB31593@redhat.com \
    --to=mst@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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).