All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] xen: convert to memory API
Date: Sun, 18 Dec 2011 17:57:05 +0200	[thread overview]
Message-ID: <4EEE0D51.5010403@redhat.com> (raw)
In-Reply-To: <CAFEAcA-1dhOZreqYCv4UxBqdwTiu7Bj81NKhcOND2Egd_rKu1Q@mail.gmail.com>

On 12/18/2011 05:43 PM, Peter Maydell wrote:
> On 18 December 2011 15:32, Avi Kivity <avi@redhat.com> wrote:
> > I missed Xen while converting stuff to the memory API, as it's not in hw/.
> >
> > Here comes the first simple patches; expect more as ram_addr_t is retired.
>
> Er, ram_addr_t is going away? Can you elaborate?
>

Nothing dramatic.  Uses of ram_addr_t to denote RAM will be replaced by
a (MemoryRegion *, offset) pair.  The type of the offset will be called
ram_addr_t.

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

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH 0/2] xen: convert to memory API
Date: Sun, 18 Dec 2011 17:57:05 +0200	[thread overview]
Message-ID: <4EEE0D51.5010403@redhat.com> (raw)
In-Reply-To: <CAFEAcA-1dhOZreqYCv4UxBqdwTiu7Bj81NKhcOND2Egd_rKu1Q@mail.gmail.com>

On 12/18/2011 05:43 PM, Peter Maydell wrote:
> On 18 December 2011 15:32, Avi Kivity <avi@redhat.com> wrote:
> > I missed Xen while converting stuff to the memory API, as it's not in hw/.
> >
> > Here comes the first simple patches; expect more as ram_addr_t is retired.
>
> Er, ram_addr_t is going away? Can you elaborate?
>

Nothing dramatic.  Uses of ram_addr_t to denote RAM will be replaced by
a (MemoryRegion *, offset) pair.  The type of the offset will be called
ram_addr_t.

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

  reply	other threads:[~2011-12-18 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 15:32 [Qemu-devel] [PATCH 0/2] xen: convert to memory API Avi Kivity
2011-12-18 15:32 ` Avi Kivity
2011-12-18 15:32 ` [Qemu-devel] [PATCH 1/2] memory, xen: pass MemoryRegion to xen_ram_alloc() Avi Kivity
2011-12-18 15:32   ` Avi Kivity
2011-12-18 15:32 ` [Qemu-devel] [PATCH 2/2] xen: convert to memory API Avi Kivity
2011-12-18 15:32   ` Avi Kivity
2011-12-18 15:43 ` [Qemu-devel] [PATCH 0/2] " Peter Maydell
2011-12-18 15:43   ` Peter Maydell
2011-12-18 15:57   ` Avi Kivity [this message]
2011-12-18 15:57     ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EEE0D51.5010403@redhat.com \
    --to=avi@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.