Home
last modified time | relevance | path

Searched full:be (Results 1 – 25 of 7304) sorted by relevance

12345678910>>...293

/openbmc/qemu/backends/
H A Diommufd.c26 static const char *iommufd_fd_name(IOMMUFDBackend *be) in iommufd_fd_name() argument
28 return object_get_canonical_path_component(OBJECT(be)); in iommufd_fd_name()
33 IOMMUFDBackend *be = IOMMUFD_BACKEND(obj); in iommufd_backend_init() local
35 be->fd = -1; in iommufd_backend_init()
36 be->users = 0; in iommufd_backend_init()
37 be->owned = true; in iommufd_backend_init()
42 IOMMUFDBackend *be = IOMMUFD_BACKEND(obj); in iommufd_backend_finalize() local
44 if (be->owned) { in iommufd_backend_finalize()
45 close(be->fd); in iommufd_backend_finalize()
46 be->fd = -1; in iommufd_backend_finalize()
[all …]
/openbmc/u-boot/doc/
H A DREADME.POST17 Also, standalone POST tests shall be supported.
28 2) The results of tests shall be saved so that it will be possible to
31 3) The following POST tests shall be developed for MPC823E-based
45 4) The LWMON board shall be used for reference.
50 The whole project can be divided into two independent tasks:
56 A new optional module will be added to U-Boot, which will run POST
61 The list of available POST tests will be configured at U-Boot build
63 tests. All POST tests will be divided into the following groups:
73 time and can be run on the regular basis (e.g. CPU test)
78 and cannot be run regularly (e.g. strong memory test, I2C test)
[all …]
/openbmc/openbmc/poky/meta/recipes-core/glibc/ldconfig-native-2.12.1/
H A Dendian-ness_handling.patch18 +int be;
19 +static uint16_t read16(uint16_t x, int be)
21 + if (be)
26 +static uint32_t read32(uint32_t x, int be)
28 + if (be)
33 +static uint64_t read64(uint64_t x, int be)
35 + if (be)
48 + be = (elf_header->e_ident[EI_DATA] == ELFDATA2MSB);
50 + if (read16(elf_header->e_type, be) != ET_DYN)
54 + read16(elf_header->e_type, be));
[all …]
H A Dldconfig-handle-.dynstr-located-in-separate-segment.patch41 switch (read32(segment->p_type, be))
45 - loadaddr = read32(segment->p_vaddr, be) - read32(segment->p_offset, be);
66 if (read32(dyn_entry->d_tag, be) == DT_STRTAB)
68 - dynamic_strings = (char *) (file_contents + read32(dyn_entry->d_un.d_val, be) - loadaddr);
77 + i < read16(elf_header->e_phnum, be); i++, segment++)
79 + if (read32(segment->p_type, be) == PT_LOAD
80 + && read32(dyn_entry->d_un.d_val, be) >= read32(segment->p_vaddr, be)
81 + && (read32(dyn_entry->d_un.d_val, be) - read32(segment->p_vaddr, be)
82 + < read32(segment->p_filesz, be)))
84 + loadoff = read32(segment->p_vaddr, be) - read32(segment->p_offset, be);
[all …]
H A Dendian-ness_handling_fix.patch28 dynamic_addr = read64(segment->p_offset, be);
29 - dynamic_size = read32(segment->p_filesz, be);
30 + dynamic_size = read64(segment->p_filesz, be);
38 - if (!*osversion && read32(segment->p_filesz, be) >= 32 && read32(segment->p_align, be) >= 4)
39 + if (!*osversion && read64(segment->p_filesz, be) >= 32 && read64(segment->p_align, be) >= 4)
42 + read64(segment->p_offset, be));
43 - Elf64_Addr size = read32(segment->p_filesz, be);
44 + Elf64_Xword size = read64(segment->p_filesz, be);
46 while (read32(abi_note [0], be) != 4 || read32(abi_note [1], be) != 16
47 || read32(abi_note [2], be) != 1
/openbmc/qemu/tests/functional/
H A Dtest_x86_cpu_model_versions.py15 # This library is distributed in the hope that it will be useful,
42 # aliases must not be static
49 "Haswell-noTSX shouldn't be versioned")
51 "Broadwell-noTSX shouldn't be versioned")
53 "Nehalem-IBRS shouldn't be versioned")
55 "Westmere-IBRS shouldn't be versioned")
57 "SandyBridge-IBRS shouldn't be versioned")
59 "IvyBridge-IBRS shouldn't be versioned")
61 "Haswell-noTSX-IBRS shouldn't be versioned")
63 "Haswell-IBRS shouldn't be versioned")
[all …]
/openbmc/bmcweb/
H A DDEVELOPING.md7 As OpenBMC is intended to be deployed on an embedded system, care should be
13 - Application startup time should be less than 1 second on target hardware
18 Care should be taken to ensure that all code is written to be asynchronous in
21 should be avoided if possible, and instead use async tasks within boost::asio.
25 Secure coding practices should be followed in all places in the webserver
29 - All buffer boundaries must be checked before indexing or using values
30 - All pointers and iterators must be checked for null before dereferencing
31 - All input from outside the application is considered untrusted, and should be
35 - Where applicable, noexcept methods should be preferred to methods that use
37 - Explicitly bounded types should be preferred over implicitly bounded types
[all …]
/openbmc/qemu/chardev/
H A Dchar-fe.c13 * The above copyright notice and this permission notice shall be included in
19 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
33 int qemu_chr_fe_write(CharBackend *be, const uint8_t *buf, int len) in qemu_chr_fe_write() argument
35 Chardev *s = be->chr; in qemu_chr_fe_write()
44 int qemu_chr_fe_write_all(CharBackend *be, const uint8_t *buf, int len) in qemu_chr_fe_write_all() argument
46 Chardev *s = be->chr; in qemu_chr_fe_write_all()
55 int qemu_chr_fe_read_all(CharBackend *be, uint8_t *buf, int len) in qemu_chr_fe_read_all() argument
57 Chardev *s = be->chr; in qemu_chr_fe_read_all()
98 int qemu_chr_fe_ioctl(CharBackend *be, int cmd, void *arg) in qemu_chr_fe_ioctl() argument
100 Chardev *s = be->chr; in qemu_chr_fe_ioctl()
[all …]
/openbmc/openbmc/poky/bitbake/lib/toaster/bldcontrol/
H A Dbbcontroller.py23 def __init__(self, be): argument
25 self.connection = bb.server.xmlrpcclient._create_server(be.bbaddress,
26 int(be.bbport))[0]
60 This is used to retrieve, for example, the currently running BE from inside
61 the toaster UI, or find a new BE to start a new build in it.
63 The return object MUST always be a BuildEnvironmentController.
68 be = BuildEnvironment.objects.filter(Q(**kwargs))[0]
69 if be.betype == BuildEnvironment.TYPE_LOCAL:
70 return LocalhostBEController(be)
72 raise Exception("FIXME: Implement BEC for type %s" % str(be.betype))
[all …]
/openbmc/qemu/host/include/ppc/host/crypto/
H A Daes-round.h24 /* Bytes in memory are host-endian; bytes in register are @be. */
25 static inline AESStateVec aes_accel_ld(const AESState *p, bool be) in aes_accel_ld() argument
29 if (be) { in aes_accel_ld()
50 static void aes_accel_st(AESState *p, AESStateVec r, bool be) in aes_accel_st() argument
52 if (be) { in aes_accel_st()
97 aesenc_MC_accel(AESState *ret, const AESState *st, bool be) in aesenc_MC_accel() argument
101 t = aes_accel_ld(st, be); in aesenc_MC_accel()
104 aes_accel_st(ret, t, be); in aesenc_MC_accel()
109 const AESState *rk, bool be) in aesenc_SB_SR_AK_accel() argument
113 t = aes_accel_ld(st, be); in aesenc_SB_SR_AK_accel()
[all …]
/openbmc/qemu/docs/system/
H A Dgeneric-loader.rst15 The loader device allows memory values to be set from the command line. This
16 can be done by following the syntax below::
19 [,data-be=<data-be>][,cpu-num=<cpu-num>]
25 The value to be written to the address. The maximum size of the data
29 The length of the data in bytes. This argument must be included if
32 ``<data-be>``
33 Set to true if the data to be stored on the guest should be written
37 The number of the CPU's address space where the data should be
42 will be parsed as decimal. To use hex values the user should prefix the number
52 The loader device allows the CPU's PC to be set from the command line. This
[all …]
/openbmc/docs/designs/
H A Dguard-on-bmc.md6 the system downtime can be prevented by isolating the faulty components. This
8 The defective components can be kept isolated until a replacement. Most of the
9 actions required to isolate the parts will be dependant on the architecture and
31 them out of service. The list of faulty but guarded components can be stored in
33 record or manage the record will be decided by the respective component. Some of
35 the fans can be managed by the fan control application, or the guard on the
36 power components can be managed by the power management application.
38 These records will be created when an error is encountered on an element that
39 can be isolated. The decision to create a record is based on the type of error,
42 is named as Guard Record. The guard record will be deleted after a repair action
[all …]
H A Dvoltage-regulator-configuration.md16 However, this default configuration sometimes must be modified by firmware. A
17 new application is needed to configure regulators. It should be data-driven to
36 The default configuration values often need to be changed later. This can be due
43 problem may be resolved in newer versions of the hardware, but firmware still
47 - Improve manufacturing yields. Sometimes regulator configuration values must be
49 voltage may need to be increased to overcome minor manufacturing defects.
103 A new application named `phosphor-regulators` will be created to configure
104 voltage regulators. The application will be located in the proposed new
113 changes for all regulators. The JSON file will be specific to a system type, so
114 it will be stored in the GitHub repository for the appropriate build layer (such
[all …]
H A Dvpd-collection.md18 - Some of the VPD information such as FRU part number, serial number need to be
30 The VPD data itself may reside on an EEPROM (typical) or may be synthesized out
40 Each keyword can be used to contain specific data about the FRU. For example,
42 instance of a part. Keywords themselves can be combined or grouped into records.
43 For example, a single record can be used to group keywords that have similar
71 BMC applications need to be able to read VPD for FRUs to determine, for ex.,
74 Some of the VPD will need to be exchanged with the host.
82 - If a FRU does not have a VPD store such as an EEPROM, the BMC should be able
83 to synthesize VPD for such FRUs. Details on VPD synthesis will be in its own
86 - The BMC should be able to recollect VPD for FRUs that can be hotplugged or
[all …]
/openbmc/pldm/tools/fw-update/
H A DREADME.md25 - Provide name for the PLDM FW update package, output will be written to a file
28 - The file path of at least one image file must be provided
29 - In case there are more than one images, they should be specified in the _same
35 Some fields corresponding to the PLDM firmware update package must be specified
38 PLDM firmware update package has to be generated - one or more platform specific
39 metadata JSON files can be reused. The key names used in the metadata JSON
50 - whether those fields need to be specified in the JSON, or are generated by the
58 - PackageHeaderIdentifier: Supported, must be specified in metadata file
59 - PackageHeaderFormatRevision: Supported, must be specified in metadata file
70 - PackageVersionString: Supported, must be specified in metadata file
[all …]
/openbmc/qemu/hw/xen/
H A Dxen_devconfig.c10 char *fe, char *be, int len) in xen_config_dev_dirs() argument
19 snprintf(be, len, "%s/backend/%s/%d/%d", dom, btype, xen_domid, vdev); in xen_config_dev_dirs()
23 xenstore_mkdir(be, XS_PERM_READ); in xen_config_dev_dirs()
27 static int xen_config_dev_all(char *fe, char *be) in xen_config_dev_all() argument
35 xenstore_write_str(fe, "backend", be); in xen_config_dev_all()
38 xenstore_write_str(be, "domain", qemu_name ? qemu_name : "no-name"); in xen_config_dev_all()
39 xenstore_write_int(be, "online", 1); in xen_config_dev_all()
40 xenstore_write_int(be, "state", XenbusStateInitialising); in xen_config_dev_all()
41 xenstore_write_int(be, "frontend-id", xen_domid); in xen_config_dev_all()
42 xenstore_write_str(be, "frontend", fe); in xen_config_dev_all()
[all …]
/openbmc/docs/designs/oem/ibm/
H A Dsystem-power-mode.md30 monitoring the systems thermal sensors. For certain error conditions it may be
32 state. After recovery, the OCC will be put back into the ACTIVE state. Anytime
40 Current Customer Settable System Power Modes that will be sent to the OCCs:
47 committee and will be used if/when approved.
57 Defaults will need to be configurable by the system owner (via JSON file)
61 The new code would be part of the openpower-occ-control repository. New code
62 will be triggered by the following:
65 - OCC Active sensor is enabled (may be covered in above bullet)
78 Default values will also be defined for Power Mode and Idle Power Saver
80 parameters, these default values will be used. If/when the customer does set any
[all …]
/openbmc/qemu/include/crypto/
H A Daes-round.h30 static inline void aesenc_MC(AESState *r, const AESState *st, bool be) in aesenc_MC() argument
33 aesenc_MC_accel(r, st, be); in aesenc_MC()
34 } else if (HOST_BIG_ENDIAN == be) { in aesenc_MC()
51 const AESState *rk, bool be) in aesenc_SB_SR_AK() argument
54 aesenc_SB_SR_AK_accel(r, st, rk, be); in aesenc_SB_SR_AK()
55 } else if (HOST_BIG_ENDIAN == be) { in aesenc_SB_SR_AK()
72 const AESState *rk, bool be) in aesenc_SB_SR_MC_AK() argument
75 aesenc_SB_SR_MC_AK_accel(r, st, rk, be); in aesenc_SB_SR_MC_AK()
76 } else if (HOST_BIG_ENDIAN == be) { in aesenc_SB_SR_MC_AK()
90 static inline void aesdec_IMC(AESState *r, const AESState *st, bool be) in aesdec_IMC() argument
[all …]
/openbmc/openbmc/poky/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/
H A Dwpa_supplicant.conf9 # NOTE! This file may contain password information and should probably be made
14 # to be changed. This can happen if wpa_supplicant is run in the background.
18 # This option can be used to allow wpa_supplicant to overwrite configuration
21 # wpa_cli/wpa_gui to be able to store the configuration changes permanently.
36 # will be created for UNIX domain sockets for listening to requests from
38 # The socket file will be named based on the interface name, so multiple
39 # wpa_supplicant processes can be run at the same time if more than one
44 # Access control for the control interface can be configured by setting the
47 # configuration and open raw sockets) and still allow GUI/CLI components to be
48 # run as non-root users. However, since the control interface can be used to
[all …]
/openbmc/docs/designs/mctp/
H A Dmctp-userspace.md45 The lower interface would be plugged in to one of a number of hardware-specific
46 binding implementations. Most of these would be included in the library source
47 tree, but others can be plugged-in too, perhaps where the physical layer
50 The reason for a library is to allow the same MCTP implementation to be used in
51 both OpenBMC and host firmware; the library should be bidirectional. To allow
52 this, the library would be written in portable C (structured in a way that can
53 be compiled as "extern C" in C++ codebases), and be able to be configured to
54 suit those runtime environments (for example, POSIX IO may not be available on
55 all platforms; we should be able to compile the library to suit). The licence
57 may be best.
[all …]
/openbmc/qemu/docs/devel/
H A Dmulti-process.rst8 may lack features or be considerably different from what is described
22 QEMU can be susceptible to security attacks because it is a large,
24 Many of these features can be configured out of QEMU, but even a reduced
33 QEMU can be broadly described as providing three main services. One is a
34 VM control point, where VMs can be created, migrated, re-configured, and
44 host processes. Each of these processes can be given only the privileges
45 it needs to provide its service, e.g., a disk service could be given
46 access only to the disk images it provides, and not be allowed to
48 this service would not be able to use this exploit to access files or
57 emulation. i.e., the control process would also be the CPU emulation
[all …]
/openbmc/phosphor-mrw-tools/docs/
H A Dmrw-xml-requirements.md13 The system inventory can be generated from the MRW XML. The inventory typically
17 To specify a target in the MRW should be in the inventory:
21 **Note**: The BMC and cores will be automatically added without the need to set
26 The BMC device tree can be generated from the MRW XML. For the full device tree
27 to be generated, all of the corresponding devices and connections must be
29 XML representations, there are only a few attributes that need to be set. If a
30 new part is being modeled, initial values for some attributes may need to be
51 into the XML representation and don't need to be updated when the device is
67 To enable a BMC MAC module, its ethernet master unit in the MRW must be
69 need to be set.
[all …]
/openbmc/openbmc/meta-arm/documentation/
H A Dreleases.md5 …be problematic if mimicked with the compatible layers. Companies, like Arm, may not wish to releas…
8 …features) to be included in LTS named branches (not just bug fixes). This will allow for a more st…
14 …be completed in time, upstreaming via the LTS branch can occur. This follows the normal process ab…
17 …ode will be compiled as part of the CI process of the gerrit code review. Also, testing on virtual…
20 …anches for meta-arm will be released as close as possible to the release of the YP LTS release. Me…
22 …be two active development branches at any given time: master and the most recent Long Term Stable …
24 …ncide with Yocto Project releases. These non-LTS branches will be bug fix only and will be EOLed o…
30 …nches are now frozen and will not accept new patches (but will continue to be present for referenc…
34 …ith the Yocto Project version number will be added. For example, `4.3`. Also, this tag version n…
40 …ut is generally encouraged to be as close to these releases as possible. Similarily, it is recomm…
/openbmc/qemu/docs/interop/
H A Dqcow2.rst34 Length of the backing file name in bytes. Must not be
41 Must not be less than 9 (i.e. 512 byte clusters).
44 as the maximum cluster size and won't be able to open images
48 must be at least 14 (i.e. 16384 byte clusters).
74 starts. Must be aligned to a cluster boundary.
78 starts. Must be aligned to a cluster boundary.
88 starts. Must be aligned to a cluster boundary.
100 may be inconsistent, make sure to scan L1/L2
105 structure may be corrupt and the image must not
106 be written to (unless for regaining
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/
H A DREADME.md13 installed onto that item. A specific example of this would be a process that
16 A simple system design would be to include a single _ImageManager_ and two
22 to allow additional images to be added to the BMC, such as Object.Add() for REST
24 also be provided to facilitate removing images which are no longer needed.
25 Images maintained in the file system would be presented as a corresponding
27 `xyz.openbmc_project.Common.FilePath` interface would be provided to specify the
51 interface will be at the exact same path as the _ImageManager_'s
53 appropriate when the software image can be applied to exactly one device in the
72 each `Software.Version`. This allows the same software version to be contained
75 A reasonable algorithm might be:
[all …]

12345678910>>...293