qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Memory API: handling unassigned physical memory


From: Avi Kivity
Subject: Re: [Qemu-devel] Memory API: handling unassigned physical memory
Date: Tue, 01 May 2012 15:42:32 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1

On 05/01/2012 03:41 PM, Peter Maydell wrote:
> On 1 May 2012 13:39, Avi Kivity <address@hidden> wrote:
> > On 04/30/2012 04:40 PM, Peter Maydell wrote:
> >> I wrote it for essentially the purpose described above :-)
> >> If you're the owner of the sysbus device in question then it's
> >> entirely fine as you are the one deciding whether to use the
> >> traditional map function or not.
> >>
> >> It's as good as we're going to get until QOM actually lets
> >> you export memory regions and pins, at which point we can just
> >> convert all the sysbus devices.
> >
> > Sure.  But expect breakage if sysbus changes, for example dropping use
> > of get_system_memory().
>
> That's OK, I'm happy to nak sysbus patches which break this
> use case :-)

sysbus should just die.

-- 
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]