qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/28] target-arm queue
Date: Fri, 16 Dec 2022 11:54:33 +0000	[thread overview]
Message-ID: <CAFEAcA-4ULFQaJysT14RG-mZCm6vbsfkDspJ2W5+_FGrFmc+MA@mail.gmail.com> (raw)
In-Reply-To: <87ilibin55.fsf@linaro.org>

On Fri, 16 Dec 2022 at 11:49, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > drop the sysregs patch as the tcg sysregs test fails
> > (probably a bug in the test)
>
> Well I assume because it complains about extra bits leaking into
> userspace:
>
>   ➜  ./qemu-aarch64 ./tests/tcg/aarch64-linux-user/sysregs
>   Checking Counter registers
>   ctr_el0             : 0x0000000080038003
>   cntvct_el0          : 0x017314376c668b73
>   cntfrq_el0          : 0x0000000003b9aca0
>   Checking CPUID registers
>   id_aa64isar0_el1    : 0x1021111110212120
>     !!extra bits!!    : 0x1000000000000000
>   id_aa64isar1_el1    : 0x0011101101211012
>     !!extra bits!!    : 0x0011100100000000
>   id_aa64mmfr0_el1    : 0xffffffffff000000
>     !!extra bits!!    : 0xffffffff00000000
>   id_aa64pfr0_el1     : 0x0001000100110011
>   id_aa64pfr1_el1     : 0x0000000001000321
>     !!extra bits!!    : 0x0000000001000301
>   id_aa64dfr0_el1     : 0x0000000000000006
>   id_aa64zfr0_el1     : 0x0110110100110021 (not RAZ!)
>   midr_el1            : 0x00000000000f0510
>   mpidr_el1           : 0x0000000080000000
>   Remaining registers should fail
>   id_mmfr0_el1        : 0x00000000deadbeef
>   id_mmfr1_el1        : 0x00000000deadbeef
>   id_mmfr2_el1        : 0x00000000deadbeef
>   id_mmfr3_el1        : 0x00000000deadbeef
>   mvfr0_el1           : 0x00000000deadbeef
>   mvfr1_el1           : 0x00000000deadbeef
>   Extra information leaked to user-space!
>
> So it should have been updated when the API was changed.

Yes, exactly (or written in a way that supports "in future
we might expose more fields").

thanks
-- PMM


  reply	other threads:[~2022-12-16 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 17:40 [PULL v2 00/28] target-arm queue Peter Maydell
2022-12-15 21:39 ` Peter Maydell
2022-12-16 11:47 ` Alex Bennée
2022-12-16 11:54   ` Peter Maydell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-15 14:18 Peter Maydell
2024-10-15 16:30 ` 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=CAFEAcA-4ULFQaJysT14RG-mZCm6vbsfkDspJ2W5+_FGrFmc+MA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@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).