similar to: [PATCH] Implementing "late pin, early unpin" for x86_64 xenlinux

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;

Hi, Patch below is needed to make my system work stable in PAE mode. Havn''t seen problems without PAE, not sure whenever thats just pure luck or whenever there is a bug in my PAE xenlinux kernel. To me it looks like a generic bug though. I''ve actually trapped into problems with unpin only: A process exits, somewhere in exit_mm() the page tables are unpinned, shortly thereafter

With this patch, x86 and x86-64 share ioport.c, fixing LTP iopl and ioperm testcase failures (on both). We found an iopl testcase failing even on x86 xenlinux. Now x86-64 xenlinux should have the same results regarding the LTP testcases (as far as we tested). Signed-off-by: Li B Xin <li.b.xin@intel.com> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Jun --- Intel Open Source

Yes, like real Linux/ia64, it is not possible to run the same Xenlinux bits both on ski and on real hardware. A different configuration and build is required. The config difference is the same as it was with the privified xenlinux... I think you did that successfully before (with privified xenlinux) so give that config file a try and if it doesn''t work, let me know. BTW, I think I know

BTW, the xenlinux-2.6.11.bk''s version is: ChangeSet@1.2085, 2005-05-12 11:10:24-06:00, djm@kirby.fc.hp.com More work on hyperprivops Signed-off-by: Dan Magenheimer <dan.magenheimer@hp.com> Thanks, Kevin >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tian, Kevin >Sent: Friday,

Hi, > It turns out that the bochs and vbox drivers automatically reserved and > unreserved the BO from within their pin and unpin functions. The other > drivers; ast, hibmc and mgag200; performed reservation explicitly. With the > GEM VRAM conversion, automatic BO reservation within pin and unpin functions > accidentally got lost. So for bochs and vbox, ttm_bo_validate() worked on

virtio-gpu objects never move around, so effectively they are pinned all the time. This makes the the implementation pretty easy ;) Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_prime.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_prime.c b/drivers/gpu/drm/virtio/virtgpu_prime.c index

Hi, > I think would be good to have a lockdep_assert_held here for the ww_mutex. > > Also general thing: _reserved is kinda ttm lingo, for dma-buf reservations > we call the structure tracking the fences+lock the "reservation", but the > naming scheme used is _lock/_unlock. > > I think would be good to be consistent with that, and use _locked here. > Especially

[ This is ancient code. - dan ] fs/fs_context.c 168 { 169 int ret; 170 171 struct fs_parameter param = { 172 .key = key, 173 .type = fs_value_is_flag, 174 .size = v_size, 175 }; 176 177 if (value) { --> 178 param.string =

The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the GEM VRAM pin/unpin functions that do not reserve the BO during validation. The mgag200 driver requires this behavior for its cursor handling. The patch also converts the driver to use the new interfaces. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/drm_gem_vram_helper.c | 75

Hi. I forward ported XenLinux/IA64 domU portion and put it at http://people.valinux.co.jp/~yamahata/xen-ia64/20080207/xen_ia64-20080207.patch This patch is for 551e4fb2465b87de9d4aa1669b27d624435443bb of git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git It boots as domU and disk/network work. This patch is for those who are interested in XenLinux/IA64 upstream merge activity. Many

Hi, Keir, Any comments upon following patch? ;-) We need it to further check in a specific configuration file (likely xen0_defconfig_ia64tiger) later to run xen on IA64 tiger box. Currently we have no generic one for all IA64 boxes. Let''s know if better way to do it. Currently custom with tiger box can only get that file out of the tree. Thanks, Kevin >-----Original Message-----

Signed-off-by: Karol Herbst <karolherbst at gmail.com> --- src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp index 4c92a1efb5..bd60a84998 100644 ---

On Mon, May 20, 2019 at 06:19:00PM +0200, Daniel Vetter wrote: > On Thu, May 16, 2019 at 06:27:45PM +0200, Thomas Zimmermann wrote: > > The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the > > GEM VRAM pin/unpin functions that do not reserve the BO during validation. > > The mgag200 driver requires this behavior for its cursor handling. The > >

Is now time for accepting new features? Here''s updated S3 patch set for Xen/dom0, based on latest 15017 changeset. Comments welcomed. ========================================= Changes since last version: - Rebase to latest 15017 - X86-64 support - Force lazy context sync before cpu goes down - S5 poweroff support - Several bug fixes observed when running on different machines

Hi, all, Attached patch set is the first support to S3 (suspend to ram) on Xen environment. We know that 3.0.5 is feature freeze now, and thus this version is just for trial and review first. X86-64 is to go (failed to compile), but we have a preliminary support in house which is however on an old version and not very stable yet. It''s supposed to be out with next version. Totally

Keir Fraser wrote: > On 29 Mar 2006, at 17:09, Nakajima, Jun wrote: > >> Are you doing live migration? In the default setup for domUs, the >> shadow code is never used. > > The mini patches for Linux we submitted to lkml depend on shadow mode. > > -- Keir > So this is _not_ for 3.0.2? I expect some hiccups with that if domUs start using other than log-dirty

Am 20.05.19 um 18:26 schrieb Daniel Vetter: > [CAUTION: External Email] > > On Mon, May 20, 2019 at 06:19:00PM +0200, Daniel Vetter wrote: >> On Thu, May 16, 2019 at 06:27:45PM +0200, Thomas Zimmermann wrote: >>> The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the >>> GEM VRAM pin/unpin functions that do not reserve the BO during validation.

A kernel test bot reported a problem with the locktorture testcase that was triggered by the GEM VRAM helpers. ... [ 10.004734] RIP: 0010:ttm_bo_validate+0x41/0x141 [ttm] ... [ 10.015669] ? kvm_sched_clock_read+0x5/0xd [ 10.016157] ? get_lock_stats+0x11/0x3f [ 10.016607] drm_gem_vram_pin+0x77/0xa2 [drm_vram_helper] [ 10.017229]

A kernel test bot reported a problem with the locktorture testcase that was triggered by the GEM VRAM helpers. ... [ 10.004734] RIP: 0010:ttm_bo_validate+0x41/0x141 [ttm] ... [ 10.015669] ? kvm_sched_clock_read+0x5/0xd [ 10.016157] ? get_lock_stats+0x11/0x3f [ 10.016607] drm_gem_vram_pin+0x77/0xa2 [drm_vram_helper] [ 10.017229]