public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, anthony@codemonkey.ws,
	kvm@vger.kernel.org
Subject: Re: [RFC PATCH 2/6] ram_blocks: Convert to a QLIST
Date: Wed, 09 Jun 2010 10:19:16 +0200	[thread overview]
Message-ID: <m3r5kgvcsb.fsf@trasno.mitica> (raw)
In-Reply-To: <1276033548.3079.20.camel@x201> (Alex Williamson's message of "Tue, 08 Jun 2010 15:45:48 -0600")

Alex Williamson <alex.williamson@redhat.com> wrote:
> On Tue, 2010-06-08 at 14:26 -0700, Chris Wright wrote:
>> * Alex Williamson (alex.williamson@redhat.com) wrote:
>> >  extern int phys_ram_fd;
>> > -extern uint8_t *phys_ram_dirty;
>> >  extern ram_addr_t ram_size;
>> > -extern ram_addr_t last_ram_offset;
>> > +
>> > +typedef struct RAMBlock {
>> > +    uint8_t *host;
>> > +    ram_addr_t offset;
>> > +    ram_addr_t length;
>> > +    QLIST_ENTRY(RAMBlock) next;
>> > +} RAMBlock;
>> > +
>> > +typedef struct RAMList {
>> > +    uint8_t *phys_dirty;
>> > +    ram_addr_t last_offset;
>> > +    QLIST_HEAD(ram, RAMBlock) blocks;
>> > +} RAMList;
>> > +extern RAMList ram;
>> 
>> such a generic name for global namespace
>
> Well it is _the_ ram, but yea... ;)  Suggestions?

ram_block_list?

Later, Juan.

  parent reply	other threads:[~2010-06-09  8:19 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 19:14 [RFC PATCH 0/6] RAM migration overhaul Alex Williamson
2010-06-08 19:15 ` [RFC PATCH 1/6] qemu_ram_alloc: Remove duplicate code Alex Williamson
2010-06-08 21:00   ` Chris Wright
2010-06-08 19:15 ` [RFC PATCH 2/6] ram_blocks: Convert to a QLIST Alex Williamson
2010-06-08 21:26   ` Chris Wright
2010-06-08 21:45     ` Alex Williamson
2010-06-08 21:51       ` Chris Wright
2010-06-09  8:19       ` Juan Quintela [this message]
2010-06-09 20:11   ` [Qemu-devel] " Cam Macdonell
2010-06-09 20:55     ` Alex Williamson
2010-06-09 21:12       ` Yoshiaki Tamura
2010-06-08 19:15 ` [RFC PATCH 3/6] RAMBlock: Add a name field Alex Williamson
2010-06-08 20:07   ` Anthony Liguori
2010-06-08 20:09     ` Alex Williamson
2010-06-08 21:41   ` Chris Wright
2010-06-09  3:13     ` Alex Williamson
2010-06-09 11:55     ` Avi Kivity
2010-06-09 12:56     ` [Qemu-devel] " Paul Brook
2010-06-09  2:30   ` [Qemu-devel] " Paul Brook
2010-06-09  2:40     ` Anthony Liguori
2010-06-09  2:54       ` Paul Brook
2010-06-09  4:19         ` Alex Williamson
2010-06-09 12:18           ` Paul Brook
2010-06-09 16:37             ` Alex Williamson
2010-06-09 20:36               ` Paul Brook
2010-06-10  8:23                 ` Gerd Hoffmann
2010-06-10 14:33                   ` Alex Williamson
2010-06-10 14:49                     ` Paul Brook
2010-06-10 15:21                       ` Alex Williamson
2010-06-11  8:48                         ` Gerd Hoffmann
2010-06-11 15:50                           ` Alex Williamson
2010-06-11 16:12                             ` Paul Brook
2010-06-11  8:45                     ` Gerd Hoffmann
2010-06-10 15:05                 ` Alex Williamson
2010-06-10 16:40               ` Chris Wright
2010-06-10 16:45                 ` Paul Brook
2010-06-09 11:58         ` Avi Kivity
2010-06-09 13:57           ` Anthony Liguori
2010-06-09 14:09             ` Paul Brook
2010-06-09  7:28       ` Gerd Hoffmann
2010-06-08 19:16 ` [RFC PATCH 4/6] Remove uses of ram.last_offset (aka last_ram_offset) Alex Williamson
2010-06-08 19:16 ` [RFC PATCH 5/6] savevm: Migrate RAM based on name/offset Alex Williamson
2010-06-08 20:12   ` Anthony Liguori
2010-06-08 21:12     ` Alex Williamson
2010-06-08 20:54   ` Chris Wright
2010-06-08 21:22     ` Alex Williamson
2010-06-08 19:16 ` [RFC PATCH 6/6] savevm: Use RAM blocks for basis of migration Alex Williamson

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=m3r5kgvcsb.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox