similar to: bigphysarea patch on xen capable linux

Hi Folks, I need some large chunk of physical memory, so I allocate it early using alloc_bootmem_low_pages and use it later (akin to bigphysarea patch). The trouble I am having is the following. Suppose the virtual address for the memory area is 0xc14d6000. After xen_create_contiguous_region call, I do a virt_to_bus and the bus address comes out to be 0x18000000. So far so good. However,

Hi, I am trying to install a broadcom ethernet controller into Dom0 (RHEL 5)...I have compiled the broadcom sources with Xen kernel sources... First, I have used the private pool in kernel memory mode, i.e. the module will try to assemble a physically contiguous of memory using the kernel page allocator. This memory block is then administered by the mpool allocation functions. Note that once a

Hi Christoph, On Wed, Aug 19, 2020 at 8:57 AM Christoph Hellwig <hch at lst.de> wrote: > > Add a new API to allocate and free pages that are guaranteed to be > addressable by a device, but otherwise behave like pages allocated by > alloc_pages. The intended APIs to sync them for use with the device > and cpu are dma_sync_single_for_{device,cpu} that are also used for >

We have seen a series of messages when running xm-test lately on a SLES 9 SP2 32-bit box with 4GB of RAM, PAE enabled Xen build. I don''t know whether this defect of just an informational message. (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page extents. (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page extents. (XEN)

On Wed, Feb 11, 2015 at 2:21 AM, Alexandre Courbot <gnurou at gmail.com> wrote: > Let GK20A's instmem take advantage of the IOMMU if it is present. Having > an IOMMU means that instmem is no longer allocated using the DMA API, > but instead obtained through page_alloc and made contiguous to the GPU > by IOMMU mappings. > > Signed-off-by: Alexandre Courbot <acourbot

U-boot for the arndale board splits the memory in 8 contiguous banks and rewrites the memory node. So most of the memory is lost. As the frametable is only able to handle contiguous memory, use the first contiguous banks and warn if some of the memory banks are not used. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- xen/arch/arm/setup.c | 23 +++++++++++++++++------ 1 file

I have always needed the rm_nx_xd patch to boot Xen / Dom0 on the ES7000 x86_64 but the system boots without any issues on plain vanilla Linux 2.6. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: Thursday, August 18, 2005 4:49 AM > To: Nakajima, Jun > Cc: Jerone Young;

From: Thierry Reding <treding at nvidia.com> Depending on the kernel configuration, early ARM architecture setup code may have attached the GPU to a DMA/IOMMU mapping that transparently uses the IOMMU to back the DMA API. Tegra requires special handling for IOMMU backed buffers (a special bit in the GPU's MMU page tables indicates the memory path to take: via the SMMU or directly to the

From: Thierry Reding <treding at nvidia.com> Depending on the kernel configuration, early ARM architecture setup code may have attached the GPU to a DMA/IOMMU mapping that transparently uses the IOMMU to back the DMA API. Tegra requires special handling for IOMMU backed buffers (a special bit in the GPU's MMU page tables indicates the memory path to take: via the SMMU or directly to the

On Wed, 25 Apr 2018, David Rientjes wrote: > On Wed, 25 Apr 2018, Mikulas Patocka wrote: > > > From: Mikulas Patocka <mpatocka at redhat.com> > > Subject: [PATCH] fault-injection: introduce kvmalloc fallback options > > > > This patch introduces a fault-injection option "kvmalloc_fallback". This > > option makes kvmalloc randomly fall back to

On Wed, 25 Apr 2018, Randy Dunlap wrote: > On 04/25/2018 01:02 PM, Mikulas Patocka wrote: > > > > > > From: Mikulas Patocka <mpatocka at redhat.com> > > Subject: [PATCH v4] fault-injection: introduce kvmalloc fallback options > > > > This patch introduces a fault-injection option "kvmalloc_fallback". This > > option makes kvmalloc

From: Thierry Reding <treding at nvidia.com> Depending on the kernel configuration, early ARM architecture setup code may have attached the GPU to a DMA/IOMMU mapping that transparently uses the IOMMU to back the DMA API. Tegra requires special handling for IOMMU backed buffers (a special bit in the GPU's MMU page tables indicates the memory path to take: via the SMMU or directly to the

On Tue, 24 Apr 2018, Michal Hocko wrote: > > > Wouldn't it be equally trivial to simply enable the fault injection? You > > > would get additional failure paths testing as a bonus. > > > > The RHEL and Fedora debugging kernels are compiled with fault injection. > > But the fault-injection framework will do nothing unless it is enabled by > > a

On Wed, May 30, 2018 at 11:30:25AM +0100, Robin Murphy wrote: > On 30/05/18 09:03, Thierry Reding wrote: > > From: Thierry Reding <treding at nvidia.com> > > > > Depending on the kernel configuration, early ARM architecture setup code > > may have attached the GPU to a DMA/IOMMU mapping that transparently uses > > the IOMMU to back the DMA API. Tegra

Hi folks, I've finished off Xen dma support for pv_ops, and dom0 now boots! I've had an uptime of 40 minutes so far with it. Under intensive disk load it locks up with a soft lockup, but still, this is good progress. I've pushed the current bits to the "WIP" (work-in-progress) branch at the usual git repo, git://et.redhat.com/linux-2.6-dom0-pvops.git with gitweb at

Hi folks, I've finished off Xen dma support for pv_ops, and dom0 now boots! I've had an uptime of 40 minutes so far with it. Under intensive disk load it locks up with a soft lockup, but still, this is good progress. I've pushed the current bits to the "WIP" (work-in-progress) branch at the usual git repo, git://et.redhat.com/linux-2.6-dom0-pvops.git with gitweb at

Hi folks, I've finished off Xen dma support for pv_ops, and dom0 now boots! I've had an uptime of 40 minutes so far with it. Under intensive disk load it locks up with a soft lockup, but still, this is good progress. I've pushed the current bits to the "WIP" (work-in-progress) branch at the usual git repo, git://et.redhat.com/linux-2.6-dom0-pvops.git with gitweb at

On 30/05/18 09:03, Thierry Reding wrote: > From: Thierry Reding <treding at nvidia.com> > > Depending on the kernel configuration, early ARM architecture setup code > may have attached the GPU to a DMA/IOMMU mapping that transparently uses > the IOMMU to back the DMA API. Tegra requires special handling for IOMMU > backed buffers (a special bit in the GPU's MMU page

On Wed, May 30, 2018 at 02:30:51PM +0100, Robin Murphy wrote: > On 30/05/18 14:00, Thierry Reding wrote: > > On Wed, May 30, 2018 at 11:30:25AM +0100, Robin Murphy wrote: > > > On 30/05/18 09:03, Thierry Reding wrote: > > > > From: Thierry Reding <treding at nvidia.com> > > > > > > > > Depending on the kernel configuration, early ARM

On Fri, 20 Apr 2018, Matthew Wilcox wrote: > On Thu, Apr 19, 2018 at 12:12:38PM -0400, Mikulas Patocka wrote: > > Unfortunatelly, some kernel code has bugs - it uses kvmalloc and then > > uses DMA-API on the returned memory or frees it with kfree. Such bugs were > > found in the virtio-net driver, dm-integrity or RHEL7 powerpc-specific > > code. > > Maybe