|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 13/14] PPC: e500: Map PIO space into core memory region
On 10/08/2012 03:48:42 PM, Alexander Graf wrote: On 08.10.2012, at 22:20, Scott Wood wrote: > On 10/08/2012 07:23:52 AM, Alexander Graf wrote:>> On PPC, we don't have PIO. So usually PIO space behind a PCI bridge is >> accessible via MMIO. Do this mapping explicitly by mapping the PIO space>> of our PCI bus into a memory region that lives in memory space. >> Signed-off-by: Alexander Graf <agraf@xxxxxxx> >> --- >> hw/ppc/e500.c | 3 +-- >> hw/ppce500_pci.c | 9 +++++++-- >> 2 files changed, 8 insertions(+), 4 deletions(-) >> diff --git a/hw/ppc/e500.c b/hw/ppc/e500.c >> index d23f9b2..857d4dc 100644 >> --- a/hw/ppc/e500.c >> +++ b/hw/ppc/e500.c >> @@ -52,7 +52,6 @@>> #define MPC8544_PCI_REGS_BASE (MPC8544_CCSRBAR_BASE + 0x8000ULL)>> #define MPC8544_PCI_REGS_SIZE 0x1000ULL >> #define MPC8544_PCI_IO 0xE1000000ULL >> -#define MPC8544_PCI_IOLEN 0x10000ULL>> #define MPC8544_UTIL_BASE (MPC8544_CCSRBAR_BASE + 0xe0000ULL) Are you sure about that? Certainly that's the limit on x86 due to the I/O instructions, and some (buggy?) PCI devices might have trouble with larger I/O addresses, but I didn't think it was actually illegal. Some mpc85xx boards have default configs with larger I/O windows (though probably not for any good reason). > Any chance of similarly constraining PCI MMIO to its proper window?We can't distinguish between inbound and outbound right now. If we only need to restrict CPU -> PCI access, then yes. Better than nothing. :-) -Scott _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |