All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-arm@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: Aarch64-qemu
Date: Wed, 06 Nov 2019 14:16:25 +0000	[thread overview]
Message-ID: <87o8xphyyu.fsf@linaro.org> (raw)
In-Reply-To: <CAA8B=UQN_cYkij5eYwhbefF0om08R+BO2Zvj0bT3Kex_Sx79ww@mail.gmail.com>


Wissem Yahiaoui <wissem.yahiaouii@gmail.com> writes:

> Hi Peter & Qemu Team,
>
>
> Actually, I also tried it after you send me the documentation. but it will
> be also an segmentation fault. Here, it a screenshot on how I did use
> it.

Please just use inline text. Screenshots for text output or test cases
is just a pain to copy/transcribe.

>
>
> Thanks,
>
> On Wed, 6 Nov 2019 at 12:55, Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> On Wed, 6 Nov 2019 at 11:44, Wissem Yahiaoui <wissem.yahiaouii@gmail.com>
>> wrote:
>> >
>> > Hi Qemu team,
>> >
>> > As I sent you in the first email, that the SVE specific registers in
>> aarch64-qemu results an core dumped/segmentation fault. I Tried the
>> ZCR_EL1, ZCR_EL2 and ZCR_EL12, it compiles fine with the gnu toolchain, but
>> it doesn't run in qemu. I need to simulate the length check at run-time, I
>> am using Qemu but apparently I am missing some step/s.
>>
>> You need to use the prctl() that I suggested, you cannot directly
>> access any of those registers from userspace. If you have a
>> simple test program which tries to use the prctl() but does not
>> work then I can have a look at what is going wrong.
>>
>> thanks
>> -- PMM
>>


--
Alex Bennée

  reply	other threads:[~2019-11-06 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 12:55 Aarch64-qemu Wissem Yahiaoui
2019-11-02 18:10 ` Aarch64-qemu Peter Maydell
     [not found]   ` <CAA8B=UTMXMOKsMjDQ3oCP1J8QdL+UXLM3Paf81w=E5sV=RDg=Q@mail.gmail.com>
     [not found]     ` <CAFEAcA9w5be6HO+ghPHrJsy4KxhBZ1MNLdPOQ4kE4nHqFKneUg@mail.gmail.com>
     [not found]       ` <CAA8B=URoKnQTZdQar_D-xrid-JoaF_mz-EYr0SasprPpvXznoQ@mail.gmail.com>
     [not found]         ` <CAFEAcA9WYCmD+oGHtM=g8pxyCmYt=12NchojdtgPufQUwWFRpg@mail.gmail.com>
2019-11-06 11:44           ` Aarch64-qemu Wissem Yahiaoui
2019-11-06 11:54             ` Aarch64-qemu Peter Maydell
2019-11-06 12:16               ` Aarch64-qemu Wissem Yahiaoui
2019-11-06 14:16                 ` Alex Bennée [this message]
2019-11-06 12:06             ` Aarch64-qemu Alex Bennée

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=87o8xphyyu.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@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.