qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joe Komlodi <joe.komlodi@xilinx.com>
To: <qemu-devel@nongnu.org>
Cc: edgari@xilinx.com
Subject: [PATCH v1 0/3] target/microblaze: Add memattrs on transactions
Date: Thu, 21 Jan 2021 16:18:52 -0800	[thread overview]
Message-ID: <1611274735-303873-1-git-send-email-komlodi@xilinx.com> (raw)

Hi all,

This series adds memattrs on MicroBlaze transactions.

It does so by adding support for the use-non-secure property on MicroBlaze CPUs.
From there, we can then determine if the transaction should be secure or not,
and memory attributes can be set accordingly.

Thanks!
Joe

Joe Komlodi (3):
  target/microblaze: Add use-non-secure property
  target/microblaze: use MMUAccessType instead of int in mmu_translate
  target/microblaze: Add security attributes on memory transactions

 target/microblaze/cpu.c    | 48 +++++++++++++++++++++++++++++++++++++++++++++-
 target/microblaze/cpu.h    | 14 +++++++++++++-
 target/microblaze/helper.c | 26 ++++++++++++++++++++++---
 target/microblaze/mmu.c    |  2 +-
 target/microblaze/mmu.h    |  2 +-
 5 files changed, 85 insertions(+), 7 deletions(-)

-- 
2.7.4



             reply	other threads:[~2021-01-22  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  0:18 Joe Komlodi [this message]
2021-01-22  0:18 ` [PATCH v1 1/3] target/microblaze: Add use-non-secure property Joe Komlodi
2021-01-26 11:16   ` Edgar E. Iglesias
2021-01-22  0:18 ` [PATCH v1 2/3] target/microblaze: use MMUAccessType instead of int in mmu_translate Joe Komlodi
2021-01-22 20:54   ` Richard Henderson
2021-01-26 11:16   ` Edgar E. Iglesias
2021-01-22  0:18 ` [PATCH v1 3/3] target/microblaze: Add security attributes on memory transactions Joe Komlodi
2021-01-26 11:16   ` Edgar E. Iglesias

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=1611274735-303873-1-git-send-email-komlodi@xilinx.com \
    --to=joe.komlodi@xilinx.com \
    --cc=edgari@xilinx.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).