From: Florian Jakobsmeier <florian.jakobsmeier@googlemail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: xen/arm: Software Step ARMv8 - PC stuck on instruction
Date: Wed, 5 Jul 2017 16:03:00 +0200 [thread overview]
Message-ID: <CAAH2infUs+YoBio9v61SonCL6uPcbXsciKm1NwPD2A_qhPN4=g@mail.gmail.com> (raw)
In-Reply-To: <cae18431-5285-569b-af96-a3ad6509bfa4@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 2831 bytes --]
2017-07-04 20:37 GMT+02:00 Julien Grall <julien.grall@arm.com>:
>
> On 07/04/2017 01:30 PM, Florian Jakobsmeier wrote:
>
>> Hello all,
>>
>
> Hi Florian,
>
>
> asmlinkage void leave_hypervisor_tail(void)
>> {
>> + /*This methode will be called after the 'guest_entry' macro in
>> /arch/arm64/entry.S set guest registers
>> + Check single_step_enabled flag in domain struct here and set
>> needed registers
>> +
>> + */
>> +
>> + struct vcpu *v = current;
>> +
>> + if ( unlikely(v->domain->arch.monitor.singlestep_enabled ) )
>> + {
>> +
>> + WRITE_SYSREG(READ_SYSREG(MDCR_EL2) | HDCR_TDE, MDCR_EL2);
>> + WRITE_SYSREG(READ_SYSREG(SPSR_EL2) | 0x200000, SPSR_EL2 );
>> + WRITE_SYSREG(READ_SYSREG(MDSCR_EL1) | 0x1, MDSCR_EL1);
>> +
>> + if (!(v->arch.single_step ))
>> + {
>> + gprintk(XENLOG_ERR, "Setting vcpu=%d for
>> domain=%d\n",v->vcpu_id,v->domain->domain_id);
>> +
>> + gprintk(XENLOG_ERR, "[Set_singlestep] MDSCR_EL1
>> 0x%lx\n", READ_SYSREG(MDSCR_EL1));
>> + gprintk(XENLOG_ERR, "[Set_singlestep] SPSR_EL2
>> 0x%lx\n", READ_SYSREG(SPSR_EL2));
>> + gprintk(XENLOG_ERR, "[Set_singlestep] MDCR_EL2
>> 0x%lx\n", READ_SYSREG(MDCR_EL2));
>> + v->arch.single_step = 1;
>> +
>> + return;
>> + }else
>> + {
>> + //gprintk(XENLOG_ERR, "Register for vcpu=%d for
>> domain=%d already set\n",v->vcpu_id,v->domain->domain_id);
>> + }
>> + }
>>
>>
>> As mentioned, this function will set the needed registers.
>> "monitor.singlestep_enabled" is the domain SS flag which is used to
>> determine if the registers should be set. "arch.single_step" is the vcpu
>> flag to check if the register were already set once (not really in use as
>> for now). "HDCR_TDE" is the same value as "MDCR_EL2_TDE" would be, but this
>> one is not implemented yet, thats why I'm using HDCR_TDE. "SPSR_EL2 |
>> 0x200000" sets the SS bit for EL2 (because our exception will be taken to
>> the hypervisor). "MDSCR_EL1 | 0x1" to enable the SS bit.
>> Because I'm checking the domain in this function, every vcpu that will be
>> used, will be set with the values above. By this I can assure that each
>> vcpu will trigger these exceptions.
>>
>
> SPSR_EL2 is saved/restored on entry and exit of a trap to the hypervisor
> (see arch/arm/arm*/entry.S). So the value you wrote in the register is
> overridden afterwards.
>
> If you want to set the SS bit, you need to do in the save registered cpsr.
> You can access using:
>
> guest_cpu_user_regs()->cpsr |= 0x200000;
>
> This solved the problem. Thank you
> Cheers,
>
> --
> Julien Grall
>
Greetings
Florian
[-- Attachment #1.2: Type: text/html, Size: 4126 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-05 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:30 xen/arm: Software Step ARMv8 - PC stuck on instruction Florian Jakobsmeier
2017-07-04 18:37 ` Julien Grall
2017-07-05 14:03 ` Florian Jakobsmeier [this message]
2017-07-26 13:12 ` Florian Jakobsmeier
2017-08-02 13:32 ` Julien Grall
2017-08-03 9:49 ` James Morse
2017-08-03 10:16 ` Florian Jakobsmeier
2017-08-03 10:46 ` James Morse
2017-08-03 11:08 ` Julien Grall
2017-08-03 12:29 ` Florian Jakobsmeier
2017-08-03 13:02 ` James Morse
2017-08-03 16:00 ` Florian Jakobsmeier
2017-08-07 17:05 ` James Morse
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='CAAH2infUs+YoBio9v61SonCL6uPcbXsciKm1NwPD2A_qhPN4=g@mail.gmail.com' \
--to=florian.jakobsmeier@googlemail.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).