From: Blue Swirl <blauwirbel@gmail.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH, RFC] pci: handle BAR mapping at pci level
Date: Wed, 7 Jul 2010 19:29:09 +0000 [thread overview]
Message-ID: <AANLkTilsCbfzUB9Dii0cHGCffGc7Mu4q2PCc9S39jrcO@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007072214310.5706@linmac>
On Wed, Jul 7, 2010 at 6:15 PM, malc <av1474@comtv.ru> wrote:
> On Wed, 7 Jul 2010, Blue Swirl wrote:
>
>> Add I/O port registration functions which separate registration
>> from the mapping stage.
>
> Why?
So that the device code can specify all other parameters except for
the I/O port, which will be handled by PCI BAR mappings.
next prev parent reply other threads:[~2010-07-07 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:53 [Qemu-devel] [PATCH, RFC] pci: handle BAR mapping at pci level Blue Swirl
2010-07-07 17:55 ` [Qemu-devel] " Michael S. Tsirkin
2010-07-07 18:12 ` Blue Swirl
2010-07-07 18:15 ` [Qemu-devel] " malc
2010-07-07 19:29 ` Blue Swirl [this message]
2010-07-07 19:02 ` Anthony Liguori
2010-07-07 19:36 ` Blue Swirl
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=AANLkTilsCbfzUB9Dii0cHGCffGc7Mu4q2PCc9S39jrcO@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=av1474@comtv.ru \
--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).