From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [Qemu-arm] [PATCH v1 1/5] xlnx-zynqmp: Add a secure prop to en/disable ARM Security Extensions
Date: Tue, 24 May 2016 18:57:47 +0200 [thread overview]
Message-ID: <20160524165747.GR3731@toto> (raw)
In-Reply-To: <CAFEAcA-mBjS2tuQD1irUnaWD7qa1nrgMRL8LS66DdaTJmtEBHA@mail.gmail.com>
On Tue, May 24, 2016 at 05:30:54PM +0100, Peter Maydell wrote:
> On 19 May 2016 at 23:54, Edgar E. Iglesias <edgar.iglesias@gmail.com> wrote:
> > From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
> >
> > Add a secure prop to en/disable ARM Security Extensions.
> > This is particulary useful for KVM runs.
>
> "particularly"
>
> > Default to disabled to match the behavior of KVM.
>
> This is a change in behaviour, though, right? Is that OK?
IMO it's OK. But I don't have a very strong opinion. We
didn't have EL3 in this machine to start with, it came in when
we enabled it on the a53. We don't have a big user-base that
really depends on either default I'd say.
Best regards,
Edgar
>
> > Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> > ---
> > hw/arm/xlnx-zynqmp.c | 3 +++
> > include/hw/arm/xlnx-zynqmp.h | 3 +++
> > 2 files changed, 6 insertions(+)
> >
> > diff --git a/hw/arm/xlnx-zynqmp.c b/hw/arm/xlnx-zynqmp.c
> > index 4d504da..965a250 100644
> > --- a/hw/arm/xlnx-zynqmp.c
> > +++ b/hw/arm/xlnx-zynqmp.c
> > @@ -238,6 +238,8 @@ static void xlnx_zynqmp_realize(DeviceState *dev, Error **errp)
> > }
> > g_free(name);
> >
> > + object_property_set_bool(OBJECT(&s->apu_cpu[i]),
> > + s->secure, "has_el3", NULL);
> > object_property_set_int(OBJECT(&s->apu_cpu[i]), GIC_BASE_ADDR,
> > "reset-cbar", &error_abort);
> > object_property_set_bool(OBJECT(&s->apu_cpu[i]), true, "realized",
> > @@ -370,6 +372,7 @@ static void xlnx_zynqmp_realize(DeviceState *dev, Error **errp)
> >
> > static Property xlnx_zynqmp_props[] = {
> > DEFINE_PROP_STRING("boot-cpu", XlnxZynqMPState, boot_cpu),
> > + DEFINE_PROP_BOOL("secure", XlnxZynqMPState, secure, false),
> > DEFINE_PROP_END_OF_LIST()
> > };
> >
> > diff --git a/include/hw/arm/xlnx-zynqmp.h b/include/hw/arm/xlnx-zynqmp.h
> > index 2332596..38d4c8c 100644
> > --- a/include/hw/arm/xlnx-zynqmp.h
> > +++ b/include/hw/arm/xlnx-zynqmp.h
> > @@ -84,6 +84,9 @@ typedef struct XlnxZynqMPState {
> >
> > char *boot_cpu;
> > ARMCPU *boot_cpu_ptr;
> > +
> > + /* Has the ARM Security extensions? */
> > + bool secure;
> > } XlnxZynqMPState;
>
> thanks
> -- PMM
WARNING: multiple messages have this Message-ID (diff)
From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Alistair Francis <alistair.francis@xilinx.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/5] xlnx-zynqmp: Add a secure prop to en/disable ARM Security Extensions
Date: Tue, 24 May 2016 18:57:47 +0200 [thread overview]
Message-ID: <20160524165747.GR3731@toto> (raw)
In-Reply-To: <CAFEAcA-mBjS2tuQD1irUnaWD7qa1nrgMRL8LS66DdaTJmtEBHA@mail.gmail.com>
On Tue, May 24, 2016 at 05:30:54PM +0100, Peter Maydell wrote:
> On 19 May 2016 at 23:54, Edgar E. Iglesias <edgar.iglesias@gmail.com> wrote:
> > From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
> >
> > Add a secure prop to en/disable ARM Security Extensions.
> > This is particulary useful for KVM runs.
>
> "particularly"
>
> > Default to disabled to match the behavior of KVM.
>
> This is a change in behaviour, though, right? Is that OK?
IMO it's OK. But I don't have a very strong opinion. We
didn't have EL3 in this machine to start with, it came in when
we enabled it on the a53. We don't have a big user-base that
really depends on either default I'd say.
Best regards,
Edgar
>
> > Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> > ---
> > hw/arm/xlnx-zynqmp.c | 3 +++
> > include/hw/arm/xlnx-zynqmp.h | 3 +++
> > 2 files changed, 6 insertions(+)
> >
> > diff --git a/hw/arm/xlnx-zynqmp.c b/hw/arm/xlnx-zynqmp.c
> > index 4d504da..965a250 100644
> > --- a/hw/arm/xlnx-zynqmp.c
> > +++ b/hw/arm/xlnx-zynqmp.c
> > @@ -238,6 +238,8 @@ static void xlnx_zynqmp_realize(DeviceState *dev, Error **errp)
> > }
> > g_free(name);
> >
> > + object_property_set_bool(OBJECT(&s->apu_cpu[i]),
> > + s->secure, "has_el3", NULL);
> > object_property_set_int(OBJECT(&s->apu_cpu[i]), GIC_BASE_ADDR,
> > "reset-cbar", &error_abort);
> > object_property_set_bool(OBJECT(&s->apu_cpu[i]), true, "realized",
> > @@ -370,6 +372,7 @@ static void xlnx_zynqmp_realize(DeviceState *dev, Error **errp)
> >
> > static Property xlnx_zynqmp_props[] = {
> > DEFINE_PROP_STRING("boot-cpu", XlnxZynqMPState, boot_cpu),
> > + DEFINE_PROP_BOOL("secure", XlnxZynqMPState, secure, false),
> > DEFINE_PROP_END_OF_LIST()
> > };
> >
> > diff --git a/include/hw/arm/xlnx-zynqmp.h b/include/hw/arm/xlnx-zynqmp.h
> > index 2332596..38d4c8c 100644
> > --- a/include/hw/arm/xlnx-zynqmp.h
> > +++ b/include/hw/arm/xlnx-zynqmp.h
> > @@ -84,6 +84,9 @@ typedef struct XlnxZynqMPState {
> >
> > char *boot_cpu;
> > ARMCPU *boot_cpu_ptr;
> > +
> > + /* Has the ARM Security extensions? */
> > + bool secure;
> > } XlnxZynqMPState;
>
> thanks
> -- PMM
next prev parent reply other threads:[~2016-05-24 17:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 22:54 [Qemu-devel] [PATCH v1 0/5] xlnx-zynqmp: Fix various issues with KVM runs Edgar E. Iglesias
2016-05-19 22:54 ` Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-arm] [PATCH v1 1/5] xlnx-zynqmp: Add a secure prop to en/disable ARM Security Extensions Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-24 16:30 ` [Qemu-arm] " Peter Maydell
2016-05-24 16:30 ` [Qemu-devel] " Peter Maydell
2016-05-24 16:57 ` Edgar E. Iglesias [this message]
2016-05-24 16:57 ` Edgar E. Iglesias
2016-05-24 17:29 ` [Qemu-arm] " Peter Maydell
2016-05-24 17:29 ` [Qemu-devel] " Peter Maydell
2016-05-19 22:54 ` [Qemu-arm] [PATCH v1 2/5] xlnx-zynqmp: Break out RPU setup into a separate function Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-24 16:23 ` Peter Maydell
2016-05-24 16:23 ` Peter Maydell
2016-05-19 22:54 ` [Qemu-arm] [PATCH v1 3/5] xlnx-zynqmp: Make the RPU subsystem optional Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-24 16:26 ` [Qemu-arm] " Peter Maydell
2016-05-24 16:26 ` [Qemu-devel] " Peter Maydell
2016-05-24 16:32 ` [Qemu-arm] " Edgar E. Iglesias
2016-05-24 16:32 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-24 16:37 ` [Qemu-arm] " Peter Maydell
2016-05-24 16:37 ` [Qemu-devel] " Peter Maydell
2016-05-24 16:52 ` [Qemu-arm] " Edgar E. Iglesias
2016-05-24 16:52 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-arm] [PATCH v1 4/5] xlnx-zynqmp: Delay realization of GIC until post CPU realization Edgar E. Iglesias
2016-05-19 22:54 ` [Qemu-devel] " Edgar E. Iglesias
2016-05-24 16:28 ` [Qemu-arm] " Peter Maydell
2016-05-24 16:28 ` [Qemu-devel] " Peter Maydell
2016-05-19 22:54 ` [Qemu-devel] [PATCH v1 5/5] xlnx-zynqmp: Use the in kernel GIC model for KVM runs Edgar E. Iglesias
2016-05-19 22:54 ` Edgar E. Iglesias
2016-05-24 16:29 ` [Qemu-arm] " Peter Maydell
2016-05-24 16:29 ` [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=20160524165747.GR3731@toto \
--to=edgar.iglesias@xilinx.com \
--cc=alistair.francis@xilinx.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.