From: Mario Smarduch <m.smarduch@samsung.com>
To: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: 32-bit fp/simd race - never mind :)
Date: Wed, 17 Jun 2015 20:24:02 -0700 [thread overview]
Message-ID: <558239D2.5030107@samsung.com> (raw)
In-Reply-To: <55823354.1040207@samsung.com>
I have been looking at it for too long, my concepts
got twisted.
On 06/17/2015 07:56 PM, Mario Smarduch wrote:
> Maybe I've been looking at this code too long, but it
> appears that on __kvm_vcpu_return we save/restore
> fp/simd registers and then change to hyp role. In
> between if we get an interrupt vCPU may be migrated
> to another CPU? Or am I missing something?
>
> Thanks,
> - Mario
> _______________________________________________
> kvmarm mailing list
> kvmarm@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
>
prev parent reply other threads:[~2015-06-18 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 2:56 32-bit fp/simd race Mario Smarduch
2015-06-18 3:24 ` Mario Smarduch [this message]
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=558239D2.5030107@samsung.com \
--to=m.smarduch@samsung.com \
--cc=Marc.Zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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.