From: Wei Huang <wehuang@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com,
peter maydell <peter.maydell@linaro.org>,
quintela@redhat.com, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH V8 4/4] tests: Add migration test for aarch64
Date: Tue, 4 Sep 2018 13:07:56 -0400 (EDT) [thread overview]
Message-ID: <1199030251.32861977.1536080876430.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180903115335.i763ae67bykvjijl@kamzik.brq.redhat.com>
----- Original Message -----
> From: "Andrew Jones" <drjones@redhat.com>
> To: "Wei Huang" <wei@redhat.com>
> Cc: qemu-devel@nongnu.org, lvivier@redhat.com, "peter maydell" <peter.maydell@linaro.org>, quintela@redhat.com,
> dgilbert@redhat.com
> Sent: Monday, September 3, 2018 6:53:35 AM
> Subject: Re: [Qemu-devel] [PATCH V8 4/4] tests: Add migration test for aarch64
>
> On Sat, Sep 01, 2018 at 01:11:15AM -0400, Wei Huang wrote:
> > +.section .text
> > +
> > + .globl _start
> > +
> > +_start:
> > + /* disable MMU to use phys mem address */
> > + mrs x0, sctlr_el1
> > + bic x0, x0, #(1<<0)
> > + msr sctlr_el1, x0
> > + isb
> > +
> > + /* traverse test memory region */
> > + mov x0, #ARM_TEST_MEM_START
> > + mov x1, #ARM_TEST_MEM_END
>
> I don't think there's any reason to require the start and
> end addresses to be hard coded. We should be able to get
> the start address with
Are you saying that we should make the .S file as independent as possible? These variables need to be defined for migration-test.c anyway. Why can't we just use them here?
>
> #define KERNEL_OFFSET 0x80000
> adr x0, _start
> add x0, x0, #(1024 * 1024 - KERNEL_OFFSET)
>
> and the end address with
>
> add x1, x0, #(99 * 1024 * 1024)
>
> Thanks,
> drew
>
next prev parent reply other threads:[~2018-09-04 17:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 5:11 [Qemu-devel] [PATCH V8 0/4] tests: Add migration test for aarch64 Wei Huang
2018-09-01 5:11 ` [Qemu-devel] [PATCH V8 1/4] tests/migration: Convert x86 boot block compilation script into Makefile Wei Huang
2018-09-03 9:32 ` Juan Quintela
2018-09-03 11:08 ` Andrew Jones
2018-09-03 11:45 ` Juan Quintela
2018-09-03 12:14 ` Andrew Jones
2018-09-04 15:51 ` Wei Huang
2018-09-01 5:11 ` [Qemu-devel] [PATCH V8 2/4] tests/migration: Support cross compilation in generating boot header file Wei Huang
2018-09-03 9:43 ` Juan Quintela
2018-09-03 11:26 ` Andrew Jones
2018-09-04 17:04 ` Wei Huang
2018-09-04 18:05 ` Andrew Jones
2018-09-01 5:11 ` [Qemu-devel] [PATCH V8 3/4] tests/migration: Add migration-test " Wei Huang
2018-09-03 9:35 ` Juan Quintela
2018-09-03 11:34 ` Andrew Jones
2018-09-01 5:11 ` [Qemu-devel] [PATCH V8 4/4] tests: Add migration test for aarch64 Wei Huang
2018-09-01 10:07 ` Peter Maydell
2018-09-02 5:00 ` Wei Huang
2018-09-03 11:46 ` Andrew Jones
2018-09-03 9:42 ` Juan Quintela
2018-09-03 11:53 ` Andrew Jones
2018-09-04 17:07 ` Wei Huang [this message]
2018-09-04 18:02 ` Andrew Jones
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=1199030251.32861977.1536080876430.JavaMail.zimbra@redhat.com \
--to=wehuang@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).