Extend memory transaction attributes with process identifier to allow per-request address translation logic to use requester_id / process_id to identify memory mapping (e.g. enabling IOMMU w/ PASID translations). Signed-off-by: Tomasz Jeznach <tjeznach@rivosinc.com> Reviewed-by: Frank Chang <frank.chang@sifive.com> Reviewed-by: Jason Chien <jason.chien@sifive.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Message-ID: <20241016204038.649340-2-dbarboza@ventanamicro.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
		
			
				
	
	
		
			81 lines
		
	
	
		
			2.8 KiB
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			81 lines
		
	
	
		
			2.8 KiB
		
	
	
	
		
			C
		
	
	
	
	
	
/*
 | 
						|
 * Memory transaction attributes
 | 
						|
 *
 | 
						|
 * Copyright (c) 2015 Linaro Limited.
 | 
						|
 *
 | 
						|
 * Authors:
 | 
						|
 *  Peter Maydell <peter.maydell@linaro.org>
 | 
						|
 *
 | 
						|
 * This work is licensed under the terms of the GNU GPL, version 2 or later.
 | 
						|
 * See the COPYING file in the top-level directory.
 | 
						|
 *
 | 
						|
 */
 | 
						|
 | 
						|
#ifndef MEMATTRS_H
 | 
						|
#define MEMATTRS_H
 | 
						|
 | 
						|
/* Every memory transaction has associated with it a set of
 | 
						|
 * attributes. Some of these are generic (such as the ID of
 | 
						|
 * the bus master); some are specific to a particular kind of
 | 
						|
 * bus (such as the ARM Secure/NonSecure bit). We define them
 | 
						|
 * all as non-overlapping bitfields in a single struct to avoid
 | 
						|
 * confusion if different parts of QEMU used the same bit for
 | 
						|
 * different semantics.
 | 
						|
 */
 | 
						|
typedef struct MemTxAttrs {
 | 
						|
    /* Bus masters which don't specify any attributes will get this
 | 
						|
     * (via the MEMTXATTRS_UNSPECIFIED constant), so that we can
 | 
						|
     * distinguish "all attributes deliberately clear" from
 | 
						|
     * "didn't specify" if necessary.
 | 
						|
     */
 | 
						|
    unsigned int unspecified:1;
 | 
						|
    /*
 | 
						|
     * ARM/AMBA: TrustZone Secure access
 | 
						|
     * x86: System Management Mode access
 | 
						|
     */
 | 
						|
    unsigned int secure:1;
 | 
						|
    /*
 | 
						|
     * ARM: ArmSecuritySpace.  This partially overlaps secure, but it is
 | 
						|
     * easier to have both fields to assist code that does not understand
 | 
						|
     * ARMv9 RME, or no specific knowledge of ARM at all (e.g. pflash).
 | 
						|
     */
 | 
						|
    unsigned int space:2;
 | 
						|
    /* Memory access is usermode (unprivileged) */
 | 
						|
    unsigned int user:1;
 | 
						|
    /*
 | 
						|
     * Bus interconnect and peripherals can access anything (memories,
 | 
						|
     * devices) by default. By setting the 'memory' bit, bus transaction
 | 
						|
     * are restricted to "normal" memories (per the AMBA documentation)
 | 
						|
     * versus devices. Access to devices will be logged and rejected
 | 
						|
     * (see MEMTX_ACCESS_ERROR).
 | 
						|
     */
 | 
						|
    unsigned int memory:1;
 | 
						|
    /* Requester ID (for MSI for example) */
 | 
						|
    unsigned int requester_id:16;
 | 
						|
 | 
						|
    /*
 | 
						|
     * PID (PCI PASID) support: Limited to 8 bits process identifier.
 | 
						|
     */
 | 
						|
    unsigned int pid:8;
 | 
						|
} MemTxAttrs;
 | 
						|
 | 
						|
/* Bus masters which don't specify any attributes will get this,
 | 
						|
 * which has all attribute bits clear except the topmost one
 | 
						|
 * (so that we can distinguish "all attributes deliberately clear"
 | 
						|
 * from "didn't specify" if necessary).
 | 
						|
 */
 | 
						|
#define MEMTXATTRS_UNSPECIFIED ((MemTxAttrs) { .unspecified = 1 })
 | 
						|
 | 
						|
/* New-style MMIO accessors can indicate that the transaction failed.
 | 
						|
 * A zero (MEMTX_OK) response means success; anything else is a failure
 | 
						|
 * of some kind. The memory subsystem will bitwise-OR together results
 | 
						|
 * if it is synthesizing an operation from multiple smaller accesses.
 | 
						|
 */
 | 
						|
#define MEMTX_OK 0
 | 
						|
#define MEMTX_ERROR             (1U << 0) /* device returned an error */
 | 
						|
#define MEMTX_DECODE_ERROR      (1U << 1) /* nothing at that address */
 | 
						|
#define MEMTX_ACCESS_ERROR      (1U << 2) /* access denied */
 | 
						|
typedef uint32_t MemTxResult;
 | 
						|
 | 
						|
#endif
 |