From: Huacai Chen <zltjiangshi@gmail.com>
To: mst@redhat.com
Cc: yamahata@valinux.co.jp, qemu-devel@nongnu.org,
aurelien@aurel32.net, Huacai Chen <zltjiangshi@gmail.com>
Subject: [Qemu-devel] [RFC][PATCH] PCI: fix pci_to_cpu_addr() issue
Date: Wed, 30 Jun 2010 18:39:53 +0800 [thread overview]
Message-ID: <1277894393-3891-1-git-send-email-zltjiangshi@gmail.com> (raw)
It seems like software may both use CPU address or PCI address to access a PCI
device. For example, Bonito north bridge map PCI memory space at 0x10000000 ~
0x1C000000. PMON code use 0x00000000 ~ 0x0C000000, but Linux kernel code use
0x10000000 ~ 0x1C000000 to access devices. If set pci_mem_base to 0, PMON can't
work, but if set pci_mem_base to 0x10000000, Linux can't access PCI. So I make
this patch to make both cases works.
However, I don't know whether the modification will break other archs, so
request for comments here.
Signed-off-by: Huacai Chen <zltjiangshi@gmail.com>
---
hw/pci.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index 7787005..50e3572 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -672,7 +672,7 @@ PCIDevice *pci_register_device(PCIBus *bus, const char *name,
static target_phys_addr_t pci_to_cpu_addr(PCIBus *bus,
target_phys_addr_t addr)
{
- return addr + bus->mem_base;
+ return addr | bus->mem_base;
}
static void pci_unregister_io_regions(PCIDevice *pci_dev)
--
1.7.0.4
next reply other threads:[~2010-06-30 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 10:39 Huacai Chen [this message]
2010-06-30 13:38 ` [Qemu-devel] Re: [RFC][PATCH] PCI: fix pci_to_cpu_addr() issue Isaku Yamahata
2010-06-30 14:05 ` chen huacai
2010-07-02 2:11 ` Isaku Yamahata
[not found] ` <AANLkTilli02u9jZ52c0aoTBs-JSEY_mYDwqt2GyeKoYw@mail.gmail.com>
[not found] ` <20100702101318.GD16712@valinux.co.jp>
2010-07-03 4:11 ` chen huacai
2010-07-04 13:42 ` 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=1277894393-3891-1-git-send-email-zltjiangshi@gmail.com \
--to=zltjiangshi@gmail.com \
--cc=aurelien@aurel32.net \
--cc=mst@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).