similar to: linux: GFP_DMA/GFP_DMA32

These are the diffs against the pristine versions of arch/x86_64/kernel/[aperture.c,pci-gart.c] to better show the changes necessary to adapt those files to Xen. They were included with the patch and should not be applied again. -Mark Langsdorf AMD, Inc. --- pristine-linux-2.6.12/arch/x86_64/kernel/aperture.c 2005-06-17 12:48:29.000000000 -0700 +++

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,

Sender: ak@brahms.suse.de To: Adrian Bunk <bunk@stusta.de> Cc: linux-kernel@vger.kernel.org, virtualization@lists.osdl.org Subject: Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386 References: <20051118014055.GK11494@stusta.de> From: Andi Kleen <ak@suse.de> Date: 18 Nov 2005 17:05:07 +0100 In-Reply-To: <20051118014055.GK11494@stusta.de> Message-ID:

Sender: ak@brahms.suse.de To: Adrian Bunk <bunk@stusta.de> Cc: linux-kernel@vger.kernel.org, virtualization@lists.osdl.org Subject: Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386 References: <20051118014055.GK11494@stusta.de> From: Andi Kleen <ak@suse.de> Date: 18 Nov 2005 17:05:07 +0100 In-Reply-To: <20051118014055.GK11494@stusta.de> Message-ID:

Xenlinux uses a special architecture-dependent bit in the page table, called PG_arch_1 to indicate that a page is "foreign" (PG_foreign). It also apparently uses it to determine if a page is pinned (PG_pinned). Linux/ia64 (and apparently Linux/ppc and Linux/ppc64) use the PG_arch_1 bit for other purposes. On Linux/ia64, it is used to determine if the instruction cache needs to be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been trying to get nouveau working on a Geforce 6600LE in a dual-core G5 PowerMac system. For various reasons, it's not working. The first problem I encountered was the lack of virt_to_bus on 64-bit PPC. After talking to benh on IRC, I created the attached patch. nouveau.ko can at least load on PPC64 now. :) However, during X-server

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine

On Fri, 26 Apr 2019, Halil Pasic wrote: > static struct ccw_device * io_subchannel_allocate_dev(struct subchannel *sch) > { [..] > + cdev->private = kzalloc(sizeof(struct ccw_device_private), > + GFP_KERNEL | GFP_DMA); Do we still need GFP_DMA here (since we now have cdev->private->dma_area)? > @@ -1062,6 +1082,14 @@ static int io_subchannel_probe(struct subchannel

On Fri, 26 Apr 2019, Halil Pasic wrote: > static struct ccw_device * io_subchannel_allocate_dev(struct subchannel *sch) > { [..] > + cdev->private = kzalloc(sizeof(struct ccw_device_private), > + GFP_KERNEL | GFP_DMA); Do we still need GFP_DMA here (since we now have cdev->private->dma_area)? > @@ -1062,6 +1082,14 @@ static int io_subchannel_probe(struct subchannel

On Fri, 26 Apr 2019 20:32:39 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On s390, protected virtualization guests have to use bounced I/O > buffers. That requires some plumbing. > > Let us make sure, any device that uses DMA API with direct ops > correctly is spared from the problems, that a hypervisor attempting > I/O to a non-shared page would bring. > >

On Fri, 26 Apr 2019 20:32:39 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On s390, protected virtualization guests have to use bounced I/O > buffers. That requires some plumbing. > > Let us make sure, any device that uses DMA API with direct ops > correctly is spared from the problems, that a hypervisor attempting > I/O to a non-shared page would bring. > >

> http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00238.html > > > > > > The issue is that PG_arch_1 is reserved for arch-specific > > usage, the paravirtualization changes for Xenlinux utilize > > it (to mark foreign pages) because it was otherwise unused > > in Linux/x86. But Xen is no longer an arch. > > > > Grep''ing

https://bugs.freedesktop.org/show_bug.cgi?id=56340 Priority: medium Bug ID: 56340 Assignee: nouveau at lists.freedesktop.org Summary: [Ubuntu 10.04.4 LTS 32-bit] Severe instability of VIA Technologies Apollo MVP3 chipset and NVIDIA RIVA TNT2 M64 graphics QA Contact: xorg-team at lists.x.org

>From: Isaku Yamahata >Sent: 2006年3月14日 10:12 >> > > Comments, Keir (or others)? >> > >> > Sounds like the proper fix. I''ll leave it to Christian and others >> > involved in the Linux upstreaming effort to have the final word. >> >> Comments, Christian (or others)? Any chance this will get into >> 3.0.2? Certainly it should

kmemdup is introduced to duplicate a region of memory in a neat way. Rather than kmalloc/kzalloc + memcpy, which the programmer needs to write the size twice (sometimes lead to mistakes), kmemdup improves readability, leads to smaller code and also reduce the chances of mistakes. Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy. Signed-off-by: Fuqian Huang <huangfq.daxian

kmemdup is introduced to duplicate a region of memory in a neat way. Rather than kmalloc/kzalloc + memcpy, which the programmer needs to write the size twice (sometimes lead to mistakes), kmemdup improves readability, leads to smaller code and also reduce the chances of mistakes. Suggestion to use kmemdup rather than using kmalloc/kzalloc + memcpy. Signed-off-by: Fuqian Huang <huangfq.daxian

On Mon, 8 Dec 2014 15:05:58 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > This will make it easy for transports to validate features and return > failure. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > include/linux/virtio_config.h | 3 ++- > drivers/lguest/lguest_device.c | 4 +++- >

On Mon, 8 Dec 2014 15:05:58 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > This will make it easy for transports to validate features and return > failure. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > include/linux/virtio_config.h | 3 ++- > drivers/lguest/lguest_device.c | 4 +++- >