From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Make migration/ram.c target independent
Date: Thu, 18 May 2017 12:04:00 +0200 [thread overview]
Message-ID: <87zieaa3cf.fsf@secure.mitica> (raw)
In-Reply-To: <20170517160804.22245-1-quintela@redhat.com> (Juan Quintela's message of "Wed, 17 May 2017 18:08:02 +0200")
Juan Quintela <quintela@redhat.com> wrote:
> Hi
Hi
And I got it wrong subject.
What got target independent is savevm.c
ram.c needs to "cleanup" first include/exec/ram_addr.h
Sorry, Juan.
>
> Only reason that ram.c is compiled by target is because it use
> TARGET_PAGE_BITS. As we already have a function to export
> TARGET_PAGE_SIZE, do the same.
> After this, we can make it target independent.
>
> Please, review.
>
> Later, Juan.
>
>
>
>
> Juan Quintela (2):
> exec: Create include for target_page_size()
> migration: Make savevm.c target independent
>
> Makefile.target | 2 +-
> exec.c | 10 ++++++++++
> include/exec/target_page.h | 22 ++++++++++++++++++++++
> include/sysemu/sysemu.h | 1 -
> migration/Makefile.objs | 2 +-
> migration/migration.c | 1 +
> migration/postcopy-ram.c | 1 +
> migration/savevm.c | 15 ++++++++-------
> 8 files changed, 44 insertions(+), 10 deletions(-)
> create mode 100644 include/exec/target_page.h
next prev parent reply other threads:[~2017-05-18 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 16:08 [Qemu-devel] [PATCH 0/2] Make migration/ram.c target independent Juan Quintela
2017-05-17 16:08 ` [Qemu-devel] [PATCH 1/2] exec: Create include for target_page_size() Juan Quintela
2017-05-18 14:27 ` Dr. David Alan Gilbert
2017-05-17 16:08 ` [Qemu-devel] [PATCH 2/2] migration: Make savevm.c target independent Juan Quintela
2017-05-18 15:00 ` Dr. David Alan Gilbert
2017-05-18 10:04 ` Juan Quintela [this message]
2017-05-18 10:31 ` [Qemu-devel] [PATCH 0/2] Make migration/ram.c " Peter Xu
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=87zieaa3cf.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--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 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.