All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Komlodi <komlodi@google.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, peterx@redhat.com, david@redhat.com,
	 peter.maydell@linaro.org, marcel.apfelbaum@gmail.com,
	mst@redhat.com,  philmd@linaro.org, roqueh@google.com,
	slongfield@google.com,  komlodi@google.com
Subject: [RFC PATCH 3/5] memattrs: Add user-defined attribute
Date: Tue, 27 Feb 2024 22:24:15 +0000	[thread overview]
Message-ID: <20240227222417.929367-4-komlodi@google.com> (raw)
In-Reply-To: <20240227222417.929367-1-komlodi@google.com>

These are used to represent implementation-specific data.
These are based off of AMBA-AXI user signals, but can be used in any
implementation.

The length of 4-bits is arbitrary.

Signed-off-by: Joe Komlodi <komlodi@google.com>
---
 include/exec/memattrs.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/exec/memattrs.h b/include/exec/memattrs.h
index 942b721be8..a38645f881 100644
--- a/include/exec/memattrs.h
+++ b/include/exec/memattrs.h
@@ -64,6 +64,8 @@ typedef struct MemTxAttrs {
     unsigned int target_tlb_bit0:1;
     unsigned int target_tlb_bit1:1;
     unsigned int target_tlb_bit2:1;
+    /* User-defined bits represent data that is implementation defined. */
+    unsigned int user_defined:4;
 } MemTxAttrs;
 
 /* Bus masters which don't specify any attributes will get this,
-- 
2.44.0.rc0.258.g7320e95886-goog



  parent reply	other threads:[~2024-02-27 22:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27 22:24 [RFC PATCH 0/5] memattrs: target/arm: add user-defined and requester ID memattrs Joe Komlodi
2024-02-27 22:24 ` [RFC PATCH 1/5] target/arm: Add requester ID to memattrs Joe Komlodi
2024-02-27 22:24 ` [RFC PATCH 2/5] memattrs: Fix target_tlb_bit whitespace Joe Komlodi
2024-02-27 22:24 ` Joe Komlodi [this message]
2024-02-28 11:47   ` [RFC PATCH 3/5] memattrs: Add user-defined attribute Alex Bennée
2024-02-27 22:24 ` [RFC PATCH 4/5] target/arm: Add user-defined memattrs Joe Komlodi
2024-02-27 22:24 ` [RFC PATCH 5/5] hw/pci: " Joe Komlodi
2024-02-28 14:21 ` [RFC PATCH 0/5] memattrs: target/arm: add user-defined and requester ID memattrs Peter Maydell
2024-02-29  4:52   ` Joe Komlodi
2024-02-29  9:57     ` Peter Maydell
2024-02-29 17:15       ` Joe Komlodi

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=20240227222417.929367-4-komlodi@google.com \
    --to=komlodi@google.com \
    --cc=david@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=roqueh@google.com \
    --cc=slongfield@google.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 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.