All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1679358@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1679358] Re: ARM: RES0/RES1 SCTLR fields not read-only
Date: Sat, 08 May 2021 05:29:55 -0000	[thread overview]
Message-ID: <162045179579.7349.2088801277099708223.malone@gac.canonical.com> (raw)
In-Reply-To: 20170403221712.26304.98856.malonedeb@chaenomeles.canonical.com

The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.

If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".

If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:

1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:

    https://gitlab.com/qemu-project/qemu/-/issues

and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.

2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" within the next 60 days (otherwise it will get
closed as "Expired"). We will then eventually migrate the ticket auto-
matically to the new system (but you won't be the reporter of the bug
in the new system and thus won't get notified on changes anymore).

Thank you and sorry for the inconvenience.


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

-- 
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:
  Incomplete

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:[~2021-05-08  5:36 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
2021-05-08  5:29 ` Thomas Huth [this message]
2021-07-08  4:17 ` [Bug 1679358] Re: ARM: RES0/RES1 SCTLR fields not read-only 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=162045179579.7349.2088801277099708223.malone@gac.canonical.com \
    --to=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.