Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-08-05 Thread Richard Henderson
On 08/04/2011 04:58 PM, Edgar E. Iglesias wrote: > QEMU only models the data lanes so I think Richards patch is quite OK > because it brings the decission back to the CPU model. > > I would prefer though, if the new Memory API would let devices pass > ctrl data back to the CPU in addition to the d

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-08-04 Thread Edgar E. Iglesias
On Sun, Jul 24, 2011 at 01:56:00PM -0500, Anthony Liguori wrote: > On 07/24/2011 11:42 AM, Richard Henderson wrote: > >On 07/24/2011 06:28 AM, Anthony Liguori wrote: > >>On 07/23/2011 02:17 PM, Richard Henderson wrote: > >>>Signed-off-by: Richard Henderson > >> > >>Why? > > > >So that I can write i

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Richard Henderson
On 07/24/2011 06:47 PM, Anthony Liguori wrote: > On 07/24/2011 02:00 PM, Richard Henderson wrote: >> On 07/24/2011 11:56 AM, Anthony Liguori wrote: >>> What is returned by totally unregistered MMIO is defined by the >>> chipset. What's returned by an empty space in the MMIO space of a >>> device is

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Anthony Liguori
On 07/24/2011 02:00 PM, Richard Henderson wrote: On 07/24/2011 11:56 AM, Anthony Liguori wrote: What is returned by totally unregistered MMIO is defined by the chipset. What's returned by an empty space in the MMIO space of a device is device specific. It's one and the same here, it's the chip

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Richard Henderson
On 07/24/2011 11:56 AM, Anthony Liguori wrote: > What is returned by totally unregistered MMIO is defined by the > chipset. What's returned by an empty space in the MMIO space of a > device is device specific. It's one and the same here, it's the chipset I'm implementing. > What does your device

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Anthony Liguori
On 07/24/2011 11:42 AM, Richard Henderson wrote: On 07/24/2011 06:28 AM, Anthony Liguori wrote: On 07/23/2011 02:17 PM, Richard Henderson wrote: Signed-off-by: Richard Henderson Why? So that I can write i/o functions like this: switch (addr) { case 0: ... case 64: ... case 128:

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Richard Henderson
On 07/24/2011 06:28 AM, Anthony Liguori wrote: > On 07/23/2011 02:17 PM, Richard Henderson wrote: >> Signed-off-by: Richard Henderson > > Why? So that I can write i/o functions like this: switch (addr) { case 0: ... case 64: ... case 128: ... ... default: unassigned_mem_readl(...

Re: [Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-24 Thread Anthony Liguori
On 07/23/2011 02:17 PM, Richard Henderson wrote: Signed-off-by: Richard Henderson Why? Regards, Anthony Liguori --- cpu-common.h |7 +++ exec.c | 12 ++-- 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/cpu-common.h b/cpu-common.h index 44b04b3..7

[Qemu-devel] [PATCH 1/7] Export the unassigned_mem read/write functions.

2011-07-23 Thread Richard Henderson
Signed-off-by: Richard Henderson --- cpu-common.h |7 +++ exec.c | 12 ++-- 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/cpu-common.h b/cpu-common.h index 44b04b3..78e1bad 100644 --- a/cpu-common.h +++ b/cpu-common.h @@ -56,6 +56,13 @@ static inline void