From: "Richard W.M. Jones" <rjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christopher Covington <cov@codeaurora.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] aarch64 & gdb: warning: while parsing target description (at line 1): Could not load XML document "arm-core.xml"
Date: Thu, 7 Aug 2014 16:06:43 +0100 [thread overview]
Message-ID: <20140807150643.GP1302@redhat.com> (raw)
In-Reply-To: <CAFEAcA9StMpcd=UyzfSusQ1TZuPD_jVZ=ehQ0+bqjCAggpTNgg@mail.gmail.com>
On Thu, Aug 07, 2014 at 02:53:33PM +0100, Peter Maydell wrote:
> On 7 August 2014 14:43, Christopher Covington <cov@codeaurora.org> wrote:
> > On 08/07/2014 08:03 AM, Peter Maydell wrote:
> >> No, because at the moment our AArch64 TCG implementation
> >> (and the way we configure KVM) assumes that the highest
> >> exception level is running AArch64. We might fix this eventually,
> >> though.
> >
> > When EL3 and EL2 support is added, the bootloader will
> > presumably have to be modified to make the switch from
> > EL3 into EL2. In my experience switching into AArch32
> > EL2 instead of AArch64 EL2 is an easy option to add.
>
> I think the biggest difficulty is not the code to actually
> do the switch but figuring out what the command line
> UI to request "start in AArch32" ought to be and how that
> then gets plumbed into the code to do the actual work.
Out of interest, how do you do this on real hardware?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2014-08-07 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 10:42 [Qemu-devel] aarch64 & gdb: warning: while parsing target description (at line 1): Could not load XML document "arm-core.xml" Richard W.M. Jones
2014-08-07 11:18 ` Peter Maydell
2014-08-07 11:29 ` Richard W.M. Jones
2014-08-07 11:35 ` Peter Maydell
2014-08-07 11:43 ` Richard W.M. Jones
2014-08-07 12:03 ` Peter Maydell
2014-08-07 13:43 ` Christopher Covington
2014-08-07 13:53 ` Peter Maydell
2014-08-07 14:13 ` Christopher Covington
2014-08-07 14:53 ` Peter Maydell
2014-08-07 15:06 ` Richard W.M. Jones [this message]
2014-08-07 15:39 ` Peter Maydell
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=20140807150643.GP1302@redhat.com \
--to=rjones@redhat.com \
--cc=cov@codeaurora.org \
--cc=peter.maydell@linaro.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;
as well as URLs for NNTP newsgroup(s).