From: Peter Maydell <peter.maydell@linaro.org>
To: Julia Suvorova <jusual@mail.ru>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] arm: Clarify the logic of set_pc()
Date: Thu, 31 Jan 2019 13:53:03 +0000 [thread overview]
Message-ID: <CAFEAcA_XuPneKXWftxjkqDn4CVTPXD1M4jSh8tM0HjnrR5tkGg@mail.gmail.com> (raw)
In-Reply-To: <20190129121817.7109-1-jusual@mail.ru>
On Tue, 29 Jan 2019 at 12:18, Julia Suvorova <jusual@mail.ru> wrote:
>
> Until now, the set_pc logic was unclear, which raised questions about
> whether it should be used directly, applying a value to PC or adding
> additional checks, for example, set the Thumb bit in Arm cpu. Let's set
> the set_pc logic for “Configure the PC, as was done in the ELF file”
> and implement synchronize_with_tb hook for preserving PC to cpu_tb_exec.
>
> Signed-off-by: Julia Suvorova <jusual@mail.ru>
Applied to target-arm.next, thanks.
-- PMM
next prev parent reply other threads:[~2019-01-31 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 12:18 [Qemu-devel] [PATCH] arm: Clarify the logic of set_pc() Julia Suvorova
2019-01-30 3:50 ` Stefan Hajnoczi
2019-01-31 13:53 ` Peter Maydell [this message]
2019-01-31 17:56 ` no-reply
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_XuPneKXWftxjkqDn4CVTPXD1M4jSh8tM0HjnrR5tkGg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jusual@mail.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).