From: Avi Kivity <avi@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sparc64: use pci_mem_base
Date: Wed, 17 Jun 2009 10:13:31 +0300 [thread overview]
Message-ID: <4A38979B.4030701@redhat.com> (raw)
In-Reply-To: <200906170106.39575.paul@codesourcery.com>
On 06/17/2009 03:06 AM, Paul Brook wrote:
>> Like pci bus would handle that memory address mapping between
>> devices and cpu?
>>
>
> Yes. In fact individual devices generally shouldn't need to know about the
> mappings at all. They should just provide a handler for accesses via a
> particular BAR.
>
I have a patch series which may help with this, I just need to rebase it.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-06-17 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 23:00 [Qemu-devel] [PATCH] sparc64: use pci_mem_base Igor Kovalenko
2009-06-16 23:13 ` Paul Brook
2009-06-16 23:24 ` Igor Kovalenko
2009-06-17 0:06 ` Paul Brook
2009-06-17 7:13 ` Avi Kivity [this message]
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=4A38979B.4030701@redhat.com \
--to=avi@redhat.com \
--cc=paul@codesourcery.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).