From: Peter Maydell <peter.maydell@linaro.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/9] target/xtensa queue
Date: Tue, 21 May 2019 12:01:20 +0100 [thread overview]
Message-ID: <CAFEAcA-RRZ+GC6FL2V7U09SY4zUA1rE8f9JvM-3XQ2sLRLj1Ew@mail.gmail.com> (raw)
In-Reply-To: <20190520175837.4561-1-jcmvbkbc@gmail.com>
On Mon, 20 May 2019 at 18:58, Max Filippov <jcmvbkbc@gmail.com> wrote:
>
> Hi Peter,
>
> please pull the following batch of updates to target/xtensa:
>
> The following changes since commit efb4f3b62c69383a7308d7b739a3193e7c0ccae8:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2019-05-10 14:49:36 +0100)
>
> are available in the git repository at:
>
> git://github.com/OSLL/qemu-xtensa.git tags/20190520-xtensa
>
> for you to fetch changes up to b345e140534ea17814b02bdf8798f18db6295304:
>
> target/xtensa: implement exclusive access option (2019-05-15 10:31:52 -0700)
>
> ----------------------------------------------------------------
> target/xtensa: SR reorganization and options for modern cores
>
> Reorganize special register handling to support configurations with
> conflicting SR definitions.
>
> Implement options used by the modern xtensa cores:
> - memory protection unit;
> - block prefetch;
> - exclusive access
>
> Add special register definitions and IRQ types for ECC/parity,
> gather/scatter and IDMA.
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.1
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-05-21 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 17:58 [Qemu-devel] [PULL 0/9] target/xtensa queue Max Filippov
2019-05-21 11:01 ` Peter Maydell [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=CAFEAcA-RRZ+GC6FL2V7U09SY4zUA1rE8f9JvM-3XQ2sLRLj1Ew@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jcmvbkbc@gmail.com \
--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).