similar to: Handling PCI/ROM space

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

On 2009-01-24 19:27, Ingo Molnar wrote: > * Török Edwin <edwintorok at gmail.com> wrote: > >> #define put_user(x, ptr) \ >> ({ \ >> - int __ret_pu; \ >> + __typeof__(*(ptr)) __ret_pu; \ >> > > This does not look right. We can sometimes have

Hi there, sorry for rather long mail. Two verbose dmesgs and `pciconf -vl` outputs attached. trying to set up new machine based on ASUS P4BGL-MX motherboard, I'd encountered hangs after detecting pcib1 (ICH2). MB has rl 8100 ethernet chip onboard. This is for 4.8-R; however, machine hangs in very similar way also with 4.4-R and 5.1-R. Matrix of hangs: Onboard Ether External Ether Result

Hi, there's a regression going from 6.2 to 6.3, where it will panic upon booting the kernel within vm_fault. This problem has been discussed before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of May. It affects multiple (but identical) systems, here's an verbose boot leading to the panic. Please note that 6.2 was running fine on these machines, they also boot

I'm trying to get stable booted on a little ITX board off of a CF card, but it hangs as it's trying to run init. Here's what the boot looks like. SMAP type=01 base=0000000000000000 len=000000000009fc00 SMAP type=01 base=000000000009fc00 len=0000000000000400 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000ffff0000 len=0000000000010000 SMAP type=01

I purchased the 256 MB A-DATA flash drive (USB 2.0 SpeedDrive), but the system can't query its size. Here is corresponding parts of system messages (boot -v): >>>>>>>>>>> Aug 5 12:53:57 goshik /kernel: Copyright (c) 1992-2003 The FreeBSD Project. Aug 5 12:53:57 goshik /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 5

Hello, I have the following hardware configuration. Tyan 2466N motherboard, 1.03 BIOS, 2 Athlon-MP 1800+ CPUs, 512MB registered ECC DRAM, Onboard 3Com NIC (xl type) Radeon 8500 AGP video card Adaptec 3210S SCSI RAID controller Comtrol RocketPort 8 port PCI serial card I have started to experience some odd system lockups in the past couple months, and it seems to be getting worse. I particular,

On Mi, 2015-11-18 at 00:11 -0500, Sasha Levin wrote: > This is a first go at adding support for the modern (based on the 1.0 virtio > spec) virtio-pci implementation. > To sum it up: this is a lightly tested version for feedback about the design > and to weed out major bugs people notice. Feedback is very welcome! /me goes undust the kvmtool patches for seabios. (see

Hi, probably just nothing to worry about, but I get the following warnings when building 1.1.7 on OpenBSD 4.4 on i386. If I remove the --with-bsdauth config option, they all disappear. I won't use it anyway, but maybe there are others. $ dmesg OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008 deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R)

Master definition of VMI interface, including calls, constants, and interface version. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.16-rc5/include/asm-i386/mach-vmi/paravirtualInterface.h =================================================================== --- linux-2.6.16-rc5.orig/include/asm-i386/mach-vmi/paravirtualInterface.h 2006-03-08 10:08:45.000000000 -0800 +++

Master definition of VMI interface, including calls, constants, and interface version. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.16-rc5/include/asm-i386/mach-vmi/paravirtualInterface.h =================================================================== --- linux-2.6.16-rc5.orig/include/asm-i386/mach-vmi/paravirtualInterface.h 2006-03-08 10:08:45.000000000 -0800 +++

* Török Edwin <edwintorok at gmail.com> wrote: > On 2009-01-23 20:27, Török Edwin wrote: > >>> > >>> > >> i'd not mind it at all if the kernel could be built with other open-source > >> compilers too. > >> > >> Now in this case the patch you suggest might end up hurting the end result > >> so it's

On 2009-01-23 20:27, Török Edwin wrote: >>> >>> >> i'd not mind it at all if the kernel could be built with other open-source >> compilers too. >> >> Now in this case the patch you suggest might end up hurting the end result >> so it's not an unconditional 'yes'. But ... how much it actually matters >> depends on

Hello, I'm having problems getting my samba setup to work at a little LAN i partially maintain. I've been reading quite a lot about what I could think of being related to my problems/setup, and I've also googled my ass off :( So here I am, resorting to you guys in hope of help =] Sorry to say, but I don't have much experience, and therefore I'm a bit lost at the moment. Not

On 2009-01-23 20:30, Ingo Molnar wrote: > * Török Edwin <edwintorok at gmail.com> wrote: > > >> Having said that, llvm-gcc is not yet able to compile the full Linux >> kernel on its own [for example the boot code, due to asm(".code16gcc")], >> but with LLVM 2.4 it was possible to build "arch=UM", and "arch=X86" (by >> using

The VMI ROM detection and code patching mechanism is illustrated in setup.c. There ROM is a binary block published by the hypervisor, and and there are certainly implications of this. ROMs certainly have a history of being proprietary, very differently licensed pieces of software, and mostly under non-free licenses. Before jumping to the conclusion that this is a bad thing, let us consider more

The VMI ROM detection and code patching mechanism is illustrated in setup.c. There ROM is a binary block published by the hypervisor, and and there are certainly implications of this. ROMs certainly have a history of being proprietary, very differently licensed pieces of software, and mostly under non-free licenses. Before jumping to the conclusion that this is a bad thing, let us consider more

Good morning, I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and usable. Just wondering if anyone knows of any issues with this NIC chipset and/or with the motherboard chipset. The motherboard is a Biostar GeForce 6100 AM2 using an nVidia nForce 410 chipset and nVidia GeForce 6100 vide chipset. I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT (from

Index: linux-2.6.16-rc5/Documentation/vmi_spec.txt =================================================================== --- linux-2.6.16-rc5.orig/Documentation/vmi_spec.txt 2006-03-09 23:33:29.000000000 -0800 +++ linux-2.6.16-rc5/Documentation/vmi_spec.txt 2006-03-10 12:55:29.000000000 -0800 @@ -0,0 +1,2197 @@ + + Paravirtualization API Version 2.0 + + Zachary Amsden, Daniel Arai, Daniel Hecht,