search for: __sun__

Hi, on my system (Linux 2.6.18.8 - ia64), if a domain write on the xencons before xenconsole is initialized the domain gets back what it wrote. This patch fixes this issue by making raw the pty slave very early. (I suppose it doesn''t happen with linux as a guest because it takes a little bit of time before writing to xencons). Tristan. _______________________________________________

Folks, First, let me thank everyone involved for making QEMU available on the Solaris platform. It''s turning out to be really handy.... Here at work we''re required to use GroupWise calendaring (at least for the time being), and I''m trying to get a bit more organized, so thought I''d start (again) using a Palm handheld to take my calendar, etc. with me. The new

....1/src/unix/X11' make: *** [R] Error 2 Solution: ************************************************* --- src/unix/X11/rbitmap.c.jpeg-patch Mon Oct 2 16:18:16 2000 +++ src/unix/X11/rbitmap.c Mon Oct 2 16:40:36 2000 @@ -231,6 +231,9 @@ #ifdef HAVE_JPEG #include <jpeglib.h> +#if __sun__ & __i386 +#include <setjmp.h> +#endif /* Here's the extended error handler struct */> version _ ************************************************ with this patch R compiles and passes "make test", the full version is: > version _...

...LIBC -isystem /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/posix -isystem /usr/src/xen-3.3.0/stubdom/../tools/xenstore -isystem /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/x86 -isystem /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/x86/x86_32 -U __linux__ -U __FreeBSD__ -U __sun__ -nostdinc -isystem /usr/src/xen-3.3.0/stubdom/../extras/mini-os/include/posix -isystem /usr/src/xen-3.3.0/stubdom/cross-root-i686/i686-xen-elf/include -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include -isystem /usr/src/xen-3.3.0/stubdom/lwip/src/include -isystem /usr/src/xen-3.3.0/stubdom/lwi...

One of my test domUs is a opensuse 10.3 PV domain, and it has a /boot/grub/menu.lst file. pygrub is used as bootloader. With xVM 3.1.4, the arrow keys can be used in the pygrub screen. With xVM 3.3-unstable, the arrow keys don''t work for me any more. What I''ve found out so far is that: - gnome-terminal, xterm or dtterm are running with "vt100 application key

...domain); for (i=0 ; i< num_vbds; i++) { + char details[20]; + vbd = xenstat_domain_vbd(domain,i); - - print("VBD %4d [%2x:%2x] OO: %8llu RD: %8llu WR: %8llu\n", - xenstat_vbd_dev(vbd), - MAJOR(xenstat_vbd_dev(vbd)), MINOR(xenstat_vbd_dev(vbd)), + +#ifdef __sun__ + details[0] = ''\0''; +#else + snprintf(details, 20, "[%2x:%2x] ", MAJOR(xenstat_vbd_dev(vbd)), + MINOR(xenstat_vbd_dev(vbd))); +#endif + + print("VBD %4d %s OO: %8llu RD: %8llu WR: %8llu\n", + xenstat_vbd_dev(vbd), details, xens...

ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a Solarisism. Luckily, getCurrentExecutablePath isn't being currently used anywhere in lli. ACTION: Wrap the method contents with #ifdef __sun__ ... #else return ""; #endif. If this functionality is actually desired, it would be more portable to hack up main() to join getcwd() with basename(argv[0]) to find the desired pathname. PATCH: Apply from llvm top-level directory with "patch -p0." -- Casey Carter Casey at...

...x86_64-linux-gnu/<version>/include/stddef.h But the real problem goes here: $XEN_SRC/stubdom/Makefile: # Do not use host headers and libs GCC_INSTALL = $(shell gcc -print-search-dirs | sed -n -e ''s/install: \(.*\)/\1/p'') TARGET_CPPFLAGS += -U __linux__ -U __FreeBSD__ -U __sun__ TARGET_CPPFLAGS += -nostdinc TARGET_CPPFLAGS += -isystem $(CURDIR)/$(MINI_OS)/include/posix TARGET_CPPFLAGS += -isystem $(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/include TARGET_CPPFLAGS += -isystem $(GCC_INSTALL)include TARGET_CPPFLAGS += -isystem $(CURDIR)/lwip/src/include TARGET_CPPFLAGS += -isy...

Hi, All Intel QA conducted a full validation for xen 4.1 rc1, it includes VT-x, VT-d, SRIOV, RAS, TXT and xl tools testing. 24 issues were exposed. Refer the bug list, please. We already assigned 14 bugs to Intel developers (which has an ''Intel'' tag in the bug title), most of the rest 10 bugs are related xl command. For the these bugs, need community''s help to fix

..._ && defined(__linux__) #define ASMCALLSUFFIX "@PLT" #else #define ASMCALLSUFFIX #endif Which causes a link failure due to the non-PLT relocation that results. I'm not sure if this should be #if defined(__PIC__) && __PIC__ && (defined(__linux__) || defined(__sun__)) or #if defined(__PIC__) && __PIC__ && !defined(__APPLE__) or if it should be a configure test, which might be safer. Are there any x86 platforms (other than apple) that don't need PLT-indirect calls? 2. GenLibDeps.pl was changed in r73228 to remove the -g option from nm...

...fine ASMCALLSUFFIX "@PLT" > #else > #define ASMCALLSUFFIX > #endif > > Which causes a link failure due to the non-PLT relocation that > results. I'm not sure if this should be > #if defined(__PIC__) && __PIC__ && (defined(__linux__) || > defined(__sun__)) > > or > > #if defined(__PIC__) && __PIC__ && !defined(__APPLE__) > > or if it should be a configure test, which might be safer. Are there > any x86 platforms (other than apple) that don't need PLT-indirect calls? > > 2. GenLibDeps.pl was changed in...

...7 +281,7 @@ static void attr_addstr(int attr, const static void attr_addstr(int attr, const char *str) { attron(attr); - addstr(str); + addstr((char *)str); attroff(attr); } @@ -1035,7 +1036,9 @@ int main(int argc, char **argv) nonl(); keypad(stdscr, TRUE); halfdelay(5); +#ifndef __sun__ use_default_colors(); +#endif init_pair(1, -1, COLOR_YELLOW); do { diff --git a/tools/xenstore/xenstored_core.c b/tools/xenstore/xenstored_core.c --- a/tools/xenstore/xenstored_core.c +++ b/tools/xenstore/xenstored_core.c @@ -1688,7 +1688,7 @@ static void write_pidfile(const char *pi i...

Ian, this one is special just for you. I''m sending it as an attachment because my email client will mangle it. This patch will remove the cmake dependency from xen prior to autoconf stubdom This patch applies ontop of [VTPM v7 3/8] vtpm/vtpmmgr and required libs to stubdom/Makefile You can apply it to your tree by doing the following: git rebase -i <VTPM v7 3/8 revision>

I''ve removed all the LIBLEAF bits in this version, but kept passing the libfsimage plugin location via compiler command line. If there''s a better way to do this, I''m certainly open to it. But looking at it further today I think this isn''t too horrible. Matt

...t;FSIMAGE_FSDIR"); + const char *isadir = ""; struct dirent *dp = NULL; struct dirent *dpp; DIR *dir = NULL; @@ -130,8 +131,26 @@ static int load_plugins(void) int err; int ret = -1; +#if defined(FSIMAGE_FSDIR) if (fsdir == NULL) fsdir = FSIMAGE_FSDIR; +#elif defined(__sun__) + if (fsdir == NULL) + fsdir = "/usr/lib/fs"; + + if (sizeof(void *) == 8) + isadir = "64/"; +#elif defined(__ia64__) + if (fsdir == NULL) + fsdir = "/usr/lib/fs"; +#else + if (fsdir == NULL) { + if (sizeof(void *) == 8) + fsdir = "/usr/lib64/fs"; + e...

Hi all, Although [smp_]read_barrier_depends() became part of READ_ONCE() in commit 76ebbe78f739 ("locking/barriers: Add implicit smp_read_barrier_depends() to READ_ONCE()"), it still limps on in the Linux memory model with the sinister hope of attracting innocent new users so that it becomes impossible to remove altogether. Let's strike before it's too late: there's only

Hi all, This is version three of the patches I previously posted here: v1: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ v2: https://lore.kernel.org/r/20200630173734.14057-1-will at kernel.org Changes since v2 include: * Actually add the barrier in READ_ONCE() for Alpha! * Implement Alpha's smp_load_acquire() using __READ_ONCE(), rather than the other

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The

Hi everyone, This is the long-awaited version two of the patches I previously posted in November last year: https://lore.kernel.org/lkml/20191108170120.22331-1-will at kernel.org/ I ended up parking the series while the READ_ONCE() implementation was being overhauled, but with that merged during the recent merge window and LTO patches being posted again [1], it was time for a refresh. The