From: Paolo Bonzini <pbonzini@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-arm] [PATCH 0/4] virt: provide secure-only RAM and first flash
Date: Tue, 8 Mar 2016 13:14:44 +0100 [thread overview]
Message-ID: <56DEC234.70907@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8OgSK5+X71GLrvWLkcGcQ9=MuwOuFAsQroQTa3bWbHNA@mail.gmail.com>
On 08/03/2016 13:13, Ard Biesheuvel wrote:
> > As far as this QEMU port is concerned, having some flash in secure and
> > some in non-secure is going to be useful regardless, and 64 MB is
> > plenty for both the code and the data. So if users of the Trustzone
> > port (which is disjoint from the KVM port in any case) can tolerate
> > having the code and the variables in the same pflash file, I could
> > simply move the code into the second flash, and we could reserve the
> > first flash for secure (so it sits at physical address 0x0
>
> Uhm, actually, the code is not even in the flash to begin with. So
> having the second bank be non-secure only makes perfect sense imo
Interesting, where is the code?
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] virt: provide secure-only RAM and first flash
Date: Tue, 8 Mar 2016 13:14:44 +0100 [thread overview]
Message-ID: <56DEC234.70907@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8OgSK5+X71GLrvWLkcGcQ9=MuwOuFAsQroQTa3bWbHNA@mail.gmail.com>
On 08/03/2016 13:13, Ard Biesheuvel wrote:
> > As far as this QEMU port is concerned, having some flash in secure and
> > some in non-secure is going to be useful regardless, and 64 MB is
> > plenty for both the code and the data. So if users of the Trustzone
> > port (which is disjoint from the KVM port in any case) can tolerate
> > having the code and the variables in the same pflash file, I could
> > simply move the code into the second flash, and we could reserve the
> > first flash for secure (so it sits at physical address 0x0
>
> Uhm, actually, the code is not even in the flash to begin with. So
> having the second bank be non-secure only makes perfect sense imo
Interesting, where is the code?
Paolo
next prev parent reply other threads:[~2016-03-08 12:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 14:45 [Qemu-devel] [PATCH 0/4] virt: provide secure-only RAM and first flash Peter Maydell
2016-02-12 14:45 ` [Qemu-devel] [PATCH 1/4] hw/arm/virt: Provide a secure-only RAM if booting in Secure mode Peter Maydell
2016-02-12 14:45 ` [Qemu-arm] [PATCH 2/4] loader: Add load_image_mr() to load ROM image to a MemoryRegion Peter Maydell
2016-02-12 14:45 ` [Qemu-devel] " Peter Maydell
2016-03-03 16:46 ` [Qemu-arm] " Paolo Bonzini
2016-03-03 16:46 ` [Qemu-devel] " Paolo Bonzini
2016-03-04 7:42 ` [Qemu-arm] " Michael S. Tsirkin
2016-03-04 7:42 ` [Qemu-devel] " Michael S. Tsirkin
2016-02-12 14:46 ` [Qemu-devel] [PATCH 3/4] hw/arm/virt: Load bios image to MemoryRegion, not physaddr Peter Maydell
2016-02-12 14:46 ` [Qemu-arm] [PATCH 4/4] hw/arm/virt: Make first flash device Secure-only if booting secure Peter Maydell
2016-02-12 14:46 ` [Qemu-devel] " Peter Maydell
2016-02-12 22:54 ` [Qemu-devel] [PATCH 0/4] virt: provide secure-only RAM and first flash Mark Cave-Ayland
2016-02-25 16:47 ` [Qemu-arm] " Peter Maydell
2016-02-25 16:47 ` Peter Maydell
2016-03-07 15:20 ` [Qemu-arm] " Paolo Bonzini
2016-03-07 15:20 ` [Qemu-devel] " Paolo Bonzini
2016-03-07 23:34 ` Peter Maydell
2016-03-08 12:02 ` [Qemu-arm] " Paolo Bonzini
2016-03-08 12:02 ` [Qemu-devel] " Paolo Bonzini
2016-03-08 12:10 ` [Qemu-arm] " Ard Biesheuvel
2016-03-08 12:10 ` [Qemu-devel] " Ard Biesheuvel
2016-03-08 12:13 ` Ard Biesheuvel
2016-03-08 12:14 ` Paolo Bonzini [this message]
2016-03-08 12:14 ` Paolo Bonzini
2016-03-08 12:16 ` [Qemu-arm] " Ard Biesheuvel
2016-03-08 12:16 ` [Qemu-devel] " Ard Biesheuvel
2016-03-08 12:41 ` [Qemu-arm] " Paolo Bonzini
2016-03-08 12:41 ` [Qemu-devel] " Paolo Bonzini
2016-03-08 12:50 ` Ard Biesheuvel
2016-03-08 13:06 ` [Qemu-arm] " Paolo Bonzini
2016-03-08 13:06 ` [Qemu-devel] " Paolo Bonzini
2016-03-08 13:46 ` [Qemu-arm] " Peter Maydell
2016-03-08 13:46 ` [Qemu-devel] " Peter Maydell
2016-03-09 14:06 ` [Qemu-arm] " Laszlo Ersek
2016-03-09 14:06 ` Laszlo Ersek
2016-03-09 14:07 ` [Qemu-arm] " Paolo Bonzini
2016-03-09 14:07 ` Paolo Bonzini
2016-03-09 14:21 ` [Qemu-arm] " Laszlo Ersek
2016-03-09 14:21 ` Laszlo Ersek
2016-03-08 13:49 ` [Qemu-arm] " Peter Maydell
2016-03-08 13:49 ` [Qemu-devel] " 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=56DEC234.70907@redhat.com \
--to=pbonzini@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=armbru@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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.