[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API
From: |
Jan Kiszka |
Subject: |
Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API |
Date: |
Tue, 28 Jun 2011 14:46:43 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
On 2011-06-28 14:09, Avi Kivity wrote:
> On 06/28/2011 03:07 PM, Jan Kiszka wrote:
>>>
>>> The point is that different buses have different widths.
>>> target_phys_addr_t matches just one bus in the system. It needs to be
>>> the maximum size of all buses present to be useful.
>>
>> Then we need a type for that. Or we need to demand that
>> target_phys_addr_t is defined large enough to support all buses that the
>> particular arch wants to address. Hardcoding 64 bit or anything is not
>> appropriate for a generic subsystem.
>
> Okay, let's make t_p_a_t max(bus size in system). Do we have 32-bit
> targets that don't support pci (I guess, pc-isa with cpu < ppro?).
At least lm32 and microblaze appear to fall into that category.
> Do we want to support a 32-bit variant of pci? It certainly existed at
> some point.
As long as making everything 64 bit in the implementation of the device
models is not guest visible, I don't think that should be a problem.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
- [Qemu-devel] [RFC v2 03/20] memory: merge adjacent segments of a single memory region, (continued)
- [Qemu-devel] [RFC v2 03/20] memory: merge adjacent segments of a single memory region, Avi Kivity, 2011/06/27
- [Qemu-devel] [RFC v2 04/20] Internal interfaces for memory API, Avi Kivity, 2011/06/27
- [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/27
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Michael S. Tsirkin, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Jan Kiszka, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Jan Kiszka, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API,
Jan Kiszka <=
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Peter Maydell, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Olivier Galibert, 2011/06/28
- Re: [Qemu-devel] [RFC v2 01/20] Hierarchical memory region API, Avi Kivity, 2011/06/28
[Qemu-devel] [RFC v2 11/20] sysbus: add MemoryRegion based memory management API, Avi Kivity, 2011/06/27
[Qemu-devel] [RFC v2 13/20] pci: add API to get a BAR's mapped address, Avi Kivity, 2011/06/27
[Qemu-devel] [RFC v2 10/20] pci: add MemoryRegion based BAR management API, Avi Kivity, 2011/06/27
Re: [Qemu-devel] [RFC v2 00/20] Memory API, Avi Kivity, 2011/06/27