[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions
From: |
Avi Kivity |
Subject: |
Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions |
Date: |
Thu, 15 Dec 2011 16:22:58 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0 |
On 12/15/2011 04:21 PM, Paolo Bonzini wrote:
>
>> cpu-common.h | 36 -----------------------------
>> exec-obsolete.h | 66
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> exec.c | 3 ++
>> hw/etraxfs_eth.c | 3 --
>> memory.c | 3 ++
>> 5 files changed, 72 insertions(+), 39 deletions(-)
>> create mode 100644 exec-obsolete.h
>
>
> I would prefer exec-private.h or memory-private.h. Right now, the
> situation is that exec.c provides a low-level interface to memory.c.
> If the situation changes, the header will disappear.
Since the header is going to disappear, does it really matter? I plan
on removing it long before 1.1.
--
error compiling committee.c: too many arguments to function