similar to: Xen port for MIPS

hi all, I was following Xen beginners Guid. I downloaded , burnt on cd and installed Debian squeeze on 64 bit x86 machine. my problem is that i''m stuck at ''setup the linux bridge '' step. whenever I issue the command " aptitude install bridge-utils", its output told me that there is no package exist which could be matched with bridge-utils. I''ve checked

Hi all,  I''m new in xen-user list so forgive me for my ignorance or any awkward question. I ''ve source code of linux-2.6-xen ( a xen linux kernel) and I want to build dom0 kernel for mips architecture. from xen .org I came to know xen offers  x86, x86_64, IA64, ARM, and  other CPU architectures.  I want to now what are exactly other CPU architectures. does it support mips?  and

Hello list, I cannot get make-kpkg to build a Xenlinux type kernel into a Debian kernel binary on my Debian Squeeze x86_64 system. I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches for this custom kernel. I am trying to use the make-kpkg command to build a working linux-image-2.6.34.4-xen-amd64 package for my system. The sources are vanilla (available from kernel.org) with

Hi, After the discussions of the last week about the topic of dom0 support, and being fairly sure there is no working solution in any distribution, I've been shown a working dom0 with Ubuntu, with 2.6.24-20. I actually did not believe this would work, and stated I'd not believe it until seeing it - and I saw it some minutes later, Ubuntu 7.10 booting dom0 with 2.6.24-20. No idea what

Hi, Im trying to install Netware and Windows 2008 server but im having problems with it reading the ISO. Im guessing this is because im running version 3.2.1 debian packages so i want to upgrade to unstable and use the 3.4 deb packages. My problem is that there isn''t a kernel package so when booting you cant boot into xenified kernel mode. If i try and use a kernel from the

[Added CC:virtualization at lists.linux-foundation.org] On Mon, Feb 18, 2008 at 11:28:41AM +0800, Dong, Eddie wrote: > Hi, Tony & all: > Recently Xen-IA64 community is considering to add paravirt_ops > support to keep sync with X86 and reduce maintenance effort. With > pv_ops, sensitive instructions or some high level primitive > functionalities (such as MMU ops) are replaced

[Added CC:virtualization at lists.linux-foundation.org] On Mon, Feb 18, 2008 at 11:28:41AM +0800, Dong, Eddie wrote: > Hi, Tony & all: > Recently Xen-IA64 community is considering to add paravirt_ops > support to keep sync with X86 and reduce maintenance effort. With > pv_ops, sensitive instructions or some high level primitive > functionalities (such as MMU ops) are replaced

Hi, I noticed that klibc started crashing on 64-bit MIPS and in my quest to fix the bug I got a bit carried away and fixed a few other things as well. Here are various miscellaneous MIPS patches, although the first patch is the important one. Thanks, James *** BLURB HERE *** James Cowgill (5): mips64: compile with -mno-abicalls mips: use -Ttext-segment when linking shared library

On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote: > 2) the changelog _completely_ fails to explain the sync 0x11 and sync > 0x12 semantics nor does it provide a publicly accessible link to > documentation that does. Ralf pointed me at: https://imgtec.com/mips/architectures/mips64/ > 3) it really should have explained what you did with >

On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote: > 2) the changelog _completely_ fails to explain the sync 0x11 and sync > 0x12 semantics nor does it provide a publicly accessible link to > documentation that does. Ralf pointed me at: https://imgtec.com/mips/architectures/mips64/ > 3) it really should have explained what you did with >

Hi William, As Bruno mentioned in his email, support for MIPS64 hasn't been added yet. Do you have any plans how you want to proceed? As you can see in the source code, a lot of things were implemented without 64-bit support in mind although we knew at some point we would need to support it. I am a little worried that you or I might have to make quite a few changes to what is already there

Hi, To my understanding, ll/bc can translate to any target machine code that make cross-compiling easy. $llc -march=mipsel -mcpu=mips64 test.ll generate test.s(MIPS ASM) There must be a tool turns test.s to mips ELF file to make this whole thing done completely. What is it? -- Best Regards, Yu Rong Tan

Hi Matheus, Thank you for your information! Do you known where do download MIPS ABI/EABI document? Thanks in advance! -- Best Regards, Yu Rong Tan On Thu, Jun 12, 2014 at 7:14 PM, Matheus Almeida <Matheus.Almeida at imgtec.com> wrote: > An assembler is the tool you're after. [And a linker if you want to have an executable in the end]. > > You can specify -filetype=obj to

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r cfb49fe940fd -r 81f75ed45ec2 tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 17:05:18 2011 -0700 @@ -29,12 +29,18 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if [

clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 2dedc6136d7cfbac8348652c543887964d92393c) Native: All ok Cross compiling to MIPS: All ok clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum: f286149dbb2ea7e194c5c3719b6cded476f6e65f) All ok (aside from non-regression failures in check-all). There were two kinds of check-all failure: * mips64 sanitizers. Not a regression since

The micro mips processor assembly language is basically 100% the same as mips32/mips64. There are some assembler directives you add but for a base port, but that is all you need to do. However, the binary instruction encoding is entirely different. There are a combination of 16 and 32 bit instruction encodings. The question is, what's the best way to handle this? Extending tablegen ?

Hi, I'm seeming new regressions form 4.0.0 for mips big endian: DataFlowSanitizer-mips64 :: custom.cc DataFlowSanitizer-mips64 :: propagate.c SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc

From: Dejan Latinovic <Dejan.Latinovic at imgtec.com> --- usr/include/arch/mips64/klibc/archconfig.h | 3 + usr/include/arch/mips64/klibc/archsetjmp.h | 39 ++++++ usr/include/arch/mips64/machine/asm.h | 76 ++++++++++ usr/include/fcntl.h | 2 +- usr/include/sys/md.h | 1 + usr/include/sys/resource.h | 4 +-

Hi Eric, The main thing we need to fix is that the selection between ELF32/ELF64 needs to depend on the ABI being N64 and not on whether we used a mips-linux-gnu triple versus a mips64-linux-gnu triple. So 'clang -target mips-linux-gnu' -mips64r2 -mabi=64' should produce an ELF64 and 'clang -target mips64-linux-gnu -mips32r2 -mabi=32' should produce an ELF32. In terms of code,

Hi, I am a Xen newbie and have been trying to get Xen-3.4.1 working on my Ubuntu Lucid (kernel version 2.6.32-21) system, using kernel 2.6.18.8 as dom0. In attempting this, I ran into the following issue. On booting into Xen, I get these errors: Mounting none on /dev failed. No such device. ... Gave up waiting for root device. ... Alert! Could not mount /dev/sda1 as root device. Dropping to a