search for: tcr

This patch fixes size of ttbcr register (TCR_EL1 in case of AArch64) and it''s programming considering size in case of context switch. Currently ttbcr is defined as 32b register but for AArch64 TCR_EL1 size is 64b. Signed-off-by: Anup Patel <anup.patel@linaro.org> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro....

Smooth review. The case was approved unanimously by the members present. This is the summary of actions: . Advice to the team to follow on issue djr-02, clarifying the rationale for -p vs -a. . TCR - Add a format specifier (e.g. -F gnuplot) to show-usage . Two spec updates: - EOF of the VLAN PPA hack removal - Clarify mac_intr_t . Opinion fodder about the extensibility of the attributes, to add future support for flows based on IPv6 flowid. Kais.

My new PC has an internal 16-in-1 card reader connected via USB 2.0. The device is the Techsolo TCR-1640 (http://www.techsolo.de/product/cardreader/tcr_1640/index.php). I boot from a compact flash inserted in it and I can mount and unmount the same CF once the system has booted and has mounted the root partition from my graid3 array. The problem arise when I replace the inserted CF with another o...

...slightly confused here, just to be clear: you're planning to go ObjC -> LLVM (via Clang or whatever) -> C, then use the 360 SDK compiler to build that, right? If that's the case, I think it'd be a better option than to use LLVM to directly generate XEXs, and you won't give the TCR guys fits (I checked the BAS TCRs, none of them say you can't do that, but the platform has some requirements regarding binary code that I doubt you'll get right without a lot of effort). If that is the pipeline you had in mind, have you attempted to run a Hello World app yet? Ran into any...

...slightly confused here, just to be clear: you're planning to go ObjC -> LLVM (via Clang or whatever) -> C, then use the 360 SDK compiler to build that, right? If that's the case, I think it'd be a better option than to use LLVM to directly generate XEXs, and you won't give the TCR guys fits (I checked the BAS TCRs, none of them say you can't do that, but the platform has some requirements regarding binary code that I doubt you'll get right without a lot of effort). If that is the pipeline you had in mind, have you attempted to run a Hello World app yet? Ran into any...

...slightly confused here, just to be clear: you're planning to go ObjC -> LLVM (via Clang or whatever) -> C, then use the 360 SDK compiler to build that, right? If that's the case, I think it'd be a better option than to use LLVM to directly generate XEXs, and you won't give the TCR guys fits (I checked the BAS TCRs, none of them say you can't do that, but the platform has some requirements regarding binary code that I doubt you'll get right without a lot of effort). If that is the pipeline you had in mind, have you attempted to run a Hello World app yet? Ran into any...

...BLE_X86 0x2 ... And each model would define its own structure. On ARM 'format' could be a simple u32 defining a variant, LPAE 32/64 or short descriptor. It could also contain additional capabilities. Then depending on the variant, 'config' would be: struct pg_config_v7s { le32 tcr; le32 prrr; le32 nmrr; le32 asid; }; struct pg_config_lpae { le64 tcr; le64 mair; le32 asid; /* And maybe TTB1? */ }; struct pg_config_arm { le32 variant; union ...; }; I am really uneasy with describing all those nasty architectural details in the virtio-iommu specific...

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,

...0000000000000000 SPRG0 0000000000000000 SPRG1 0000000000000000 SPRG2 0000000000000000 SPRG3 0000000000000000 SPRG4 0000000000000000 SPRG5 0000000000000000 SPRG6 0000000000000000 SPRG7 0000000000000000 CSRR0 0000000000000000 CSRR1 0000000000000000 MCSRR0 0000000000000000 MCSRR1 0000000000000000 TCR 0000000000000000 TSR 0000000000000000 ESR 0000000000000000 DEAR 0000000000000000 PIR 0000000000000000 DECAR 0000000000000000 IVPR 0000000000000000 EPCR 0000000000000000 MCSR 0000000000000000 SPRG8 0000000000000000 EPR 0000000000000000 MCAR 0000000000000000 PID1 0000000000000000 PID...

Hello, I am trying to boot Arndale board with Julien''s new XenARM patch series. But I have got "Data Abort" while in booting. My environment is: - Arndale Board - Xen-4.3-unstable from branch "arm" in git://xenbits.xen.org/people/julieng/xen-unstable.git - Dom0 Kernel from branch "dev-arndale-dom0-3.9" in

Hi Rich I'm noe getting the below logs after running libguestfs-test-tool.. SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin SELinux: sh: getenforce: command not found guestfs_get_append: (null) guestfs_get_autosync: 1 guestfs_get_backend: direct

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I

Folks, I just posted an updated Crossbow virtualization architecture document. The new revision is available at: http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf The main changes are the addition of support for multiple MAC addresses per client, and an explicit separation between consolidation private and project private MAC API entry points. See in particular the