From: "Christoph Egger" <Christoph.Egger@amd.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH][TOOLS] ioemu: Build fixes for BSD and bug fixes from BSD
Date: Thu, 27 Sep 2007 16:35:41 +0200 [thread overview]
Message-ID: <200709271635.41212.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C3217A8E.16136%Keir.Fraser@cl.cam.ac.uk>
On Thursday 27 September 2007 16:19:42 Keir Fraser wrote:
> On 27/9/07 12:35, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> > Attached patch makes ioemu build on *BSD.
> > It also applies bug fixes from *BSD for Linux and *BSD :-)
> >
> > Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
> >
> > P.S.: Could someone with contact to qemu people make this patch
> > go upstream to qemu, please?
>
> Why the setenv PTHREAD_DIAGASSERT? There is very little pthread usage at
> all in ioemu. In fact basically none.
Oh, a debugging leftover. You may kill that.
> And why do you need to fiddle with {get,set}rlimit()? Is ioemu stack usage
> excessive?
The resource limits on BSD are more limited than on Linux.
Look:
NetBSD: ulimit -a
-----------------
time(cpu-seconds) unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 262144
stack(kbytes) 2048
lockedmem(kbytes) 1111329
memory(kbytes) 3333988
nofiles(descriptors) 64
processes 160
sbsize(bytes) unlimited
-----------------
OpenBSD: ulimit -a
--------------------
time(cpu-seconds) unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 524288
stack(kbytes) 4096
lockedmem(kbytes) 335258
memory(kbytes) 1004356
nofiles(descriptors) 128
processes 128
----------------------
Linux: ulimit -a
-----------------------
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 20
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
-----------------------
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2007-09-27 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 11:35 [PATCH][TOOLS] ioemu: Build fixes for BSD and bug fixes from BSD Christoph Egger
2007-09-27 14:19 ` Keir Fraser
2007-09-27 14:35 ` Christoph Egger [this message]
2007-09-27 15:39 ` Keir Fraser
2007-09-28 8:07 ` Christoph Egger
2007-09-28 10:31 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200709271635.41212.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.