All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1679358] Re: ARM: SCTLR fields not being preserved
Date: Mon, 06 Nov 2017 19:18:12 -0000	[thread overview]
Message-ID: <150999589239.4347.10880623847111437463.launchpad@gac.canonical.com> (raw)
In-Reply-To: 20170403221712.26304.98856.malonedeb@chaenomeles.canonical.com

** Tags added: arm

** Summary changed:

- ARM: SCTLR fields not being preserved
+ ARM: RES0/RES1 SCTLR fields not read-only

** Changed in: qemu
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1679358

Title:
  ARM: RES0/RES1 SCTLR fields not read-only

Status in QEMU:
  Confirmed

Bug description:
  There are fields in SCTLR that are RAO/SBOP or WI or in the case of
  the RR field, accessible only in secure mode. Currently it seems that
  qemu just propagates any write to SCTLR to the register and this
  screwed up in a bootloader that I am debugging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1679358/+subscriptions

  parent reply	other threads:[~2017-11-06 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 22:17 [Qemu-devel] [Bug 1679358] [NEW] ARM: SCTLR fields not being preserved Yifan
2017-04-04  8:32 ` Peter Maydell
2017-04-04 14:59 ` [Qemu-devel] [Bug 1679358] " Yifan
2017-04-04 15:14 ` Peter Maydell
2017-11-06 19:18 ` Peter Maydell [this message]
2021-05-08  5:29 ` [Bug 1679358] Re: ARM: RES0/RES1 SCTLR fields not read-only Thomas Huth
2021-07-08  4:17 ` Launchpad Bug Tracker

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=150999589239.4347.10880623847111437463.launchpad@gac.canonical.com \
    --to=peter.maydell@linaro.org \
    --cc=1679358@bugs.launchpad.net \
    --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.