qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/4] target-arm: Implement missing EL3 (and EL2) registers
Date: Fri, 14 Aug 2015 19:42:37 +0200	[thread overview]
Message-ID: <20150814174237.GC27827@toto> (raw)
In-Reply-To: <CAFEAcA8UG1mtyK3jVAju6Z+k4Jb6-zE54gGAKG_xF-00c8rS7w@mail.gmail.com>

On Fri, Aug 14, 2015 at 11:12:55AM +0100, Peter Maydell wrote:
> Ping?
> 

Hi! Sorry for the delay! I'll have a look at this over the weekend.
Do you happen to have the patches all applied in a branch somewhere?

Thanks,
Edgar


> thanks
> -- PMM
> 
> On 30 July 2015 at 19:36, Peter Maydell <peter.maydell@linaro.org> wrote:
> > This series adds a handful of EL3 system registers that
> > we were missing. It also includes the EL2 flavours
> > where there were obvious easy parallels. I think this
> > means we now have all the EL3 sysregs we care about.
> > (A previous series added missing address translation
> > operations; I still have to do the missing TLB ops.)
> >
> > None of these registers are exciting; they're all either
> > reads-as-written or RAZ/WI.
> >
> > A note for people who care about EL2: I notice that a
> > lot of AArch32 EL2 registers have the access permission
> > pattern of "accessible from EL2(NS) and from EL3 if
> > SCR.NS==1, but traps if accessed from EL3 if SCR.NS==0".
> > We don't implement this wrinkle (we won't trap the
> > erroneous EL3 access). This is true of the EL2 regs I
> > add here, but then it's true of all our existing ones...
> >
> > Peter Maydell (4):
> >   target-arm: Add missing MAIR_EL3 and TPIDR_EL3 registers
> >   target-arm: Implement missing AMAIR registers
> >   target-arm: Implement missing AFSR registers
> >   target-arm: Implement missing ACTLR registers
> >
> >  target-arm/helper.c | 74 ++++++++++++++++++++++++++++++++++++++++++++++++-----
> >  1 file changed, 68 insertions(+), 6 deletions(-)
> >

  reply	other threads:[~2015-08-14 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 18:36 [Qemu-devel] [PATCH 0/4] target-arm: Implement missing EL3 (and EL2) registers Peter Maydell
2015-07-30 18:36 ` [Qemu-devel] [PATCH 1/4] target-arm: Add missing MAIR_EL3 and TPIDR_EL3 registers Peter Maydell
2015-08-16 21:54   ` Edgar E. Iglesias
2015-07-30 18:36 ` [Qemu-devel] [PATCH 2/4] target-arm: Implement missing AMAIR registers Peter Maydell
2015-08-16 22:02   ` Edgar E. Iglesias
2015-07-30 18:36 ` [Qemu-devel] [PATCH 3/4] target-arm: Implement missing AFSR registers Peter Maydell
2015-08-16 22:05   ` Edgar E. Iglesias
2015-07-30 18:36 ` [Qemu-devel] [PATCH 4/4] target-arm: Implement missing ACTLR registers Peter Maydell
2015-08-16 22:09   ` Edgar E. Iglesias
2015-08-14 10:12 ` [Qemu-devel] [PATCH 0/4] target-arm: Implement missing EL3 (and EL2) registers Peter Maydell
2015-08-14 17:42   ` Edgar E. Iglesias [this message]
2015-08-14 17:48     ` Peter Maydell
2015-08-14 17:55       ` Edgar E. Iglesias

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=20150814174237.GC27827@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=patches@linaro.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).