qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] Add PCI memory region registration
Date: Sun, 31 May 2009 14:50:10 +0300	[thread overview]
Message-ID: <4A226EF2.7040405@redhat.com> (raw)
In-Reply-To: <20090531110253.GA13812@lst.de>

Christoph Hellwig wrote:
> On Wed, May 27, 2009 at 05:33:37PM -0500, Anthony Liguori wrote:
>   
>>    pci_register_io_region(&d->dev, 0, 0x100,
>>                           PCI_ADDRESS_SPACE_IO, rtl8139_ioport_read, 
>> rtl8139_ioport_write, s);
>>
>>    pci_register_io_region(&d->dev, 1, 0x100,
>>                           PCI_ADDRESS_SPACE_MEM, rtl8139_mmio_read, 
>> rtl8139_mmio_write, s);
>>
>> Moreover, you could probably drop the opaque parameter and and just use 
>> d->dev.  I hope it's possible to get from one to the other.
>>     
>
> I also think this is a much more natural API, and would simplify drivers
> a lot.  As for the naming the PCI spec uses the term bar for these
> PIO/MMIO regions, so maybe call it pci_register_bar or pci_setup_bar?
>   

Note that this sets up an io region within a BAR, not a complete BAR.

Currently PCI IO is a three stage setup process:

- set up BAR
- set up ram_addr
- set up mapping between BAR and ram_addr

We'll need to keep this flexibility. I agree that helpers that collapse 
all three changes will help the majority of devices.


-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-05-31 11:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24  9:29 [Qemu-devel] [PATCH 0/3] Object-based physical memory management Avi Kivity
2009-05-24  9:29 ` [Qemu-devel] [PATCH 1/3] Add PhysicalMemoryRegion type Avi Kivity
2009-05-27 14:16   ` Christoph Hellwig
2009-05-27 15:07     ` Avi Kivity
2009-05-24  9:29 ` [Qemu-devel] [PATCH 2/3] Add PCI memory region registration Avi Kivity
2009-05-27 14:08   ` Anthony Liguori
2009-05-27 15:02     ` Avi Kivity
2009-05-27 15:11       ` Anthony Liguori
2009-05-27 15:24         ` Avi Kivity
2009-05-27 22:33           ` Anthony Liguori
2009-05-31 11:02             ` Christoph Hellwig
2009-05-31 11:50               ` Avi Kivity [this message]
2009-05-31 11:47             ` Avi Kivity
2009-05-31 13:52               ` Anthony Liguori
2009-05-31 13:03             ` Avi Kivity
2009-05-24  9:29 ` [Qemu-devel] [PATCH 3/3] Convert RTL8139 to use PCI memory regitration facility Avi Kivity
2009-05-27 14:08 ` [Qemu-devel] [PATCH 0/3] Object-based physical memory management Anthony Liguori
2009-05-27 14:54   ` Avi Kivity

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=4A226EF2.7040405@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=hch@lst.de \
    --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).