From: "Christoph Egger" <Christoph.Egger@amd.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Anil Madhavapeddy <anil@xensource.com>
Subject: Re: [PATCH 1/3] Add support for OpenBSD
Date: Wed, 18 Oct 2006 09:57:59 +0200 [thread overview]
Message-ID: <200610180958.00983.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C15CEAC6.2BFE%Keir.Fraser@cl.cam.ac.uk>
On Thursday 19 October 2006 09:41, Keir Fraser wrote:
> On 18/10/06 8:25 am, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
> >> We have that already in arch/x86/Rules.mk. If that was working, I doubt
> >> Christoph would have gone to the trouble of hacking up the SSP goop.
> >
> > I did this work in August. There wasn't anything SSP-related there. So
> > without SSP support, I got into linking errors.
> > Now that the work is done, why shouldn't it go in?
>
> Uncertainty about new compiler-assisted stuff that I don't believe will
> catch any bugs in Xen. Linux guys have clearly reached the same conclusion.
> Given we even turn off frame pointers in non-debug builds, is it likely
> we'll take this? :-)
Linux guys also came to the conclusion, kernel debuggers are useless
to catch any bugs. On the other side, how many use the kgdb patch?
So, even if my SSP patch won't go in, how many will use it?
Hmm... now I feel, this ends up in a debate on principles. :-)
next prev parent reply other threads:[~2006-10-18 7:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 14:30 [PATCH 1/3] Add support for OpenBSD Christoph Egger
2006-10-18 15:24 ` Keir Fraser
2006-10-17 16:02 ` Christoph Egger
2006-10-18 16:11 ` Keir Fraser
2006-10-18 16:17 ` Anil Madhavapeddy
2006-10-18 16:27 ` Keir Fraser
2006-10-18 7:25 ` Christoph Egger
2006-10-19 7:41 ` Keir Fraser
2006-10-18 7:57 ` Christoph Egger [this message]
2006-10-19 8:00 ` Keir Fraser
2006-10-19 8:50 ` Anil Madhavapeddy
2006-10-18 16:34 ` Anil Madhavapeddy
2006-10-18 16:39 ` Keir Fraser
2006-10-18 17:47 ` Brendan Cully
2006-10-18 18:13 ` Ian Pratt
2006-10-18 19:22 ` Brendan Cully
2006-10-18 17:08 ` John Clemens
2006-10-18 18:19 ` Keir Fraser
2006-10-18 16:01 ` Anil Madhavapeddy
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=200610180958.00983.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=anil@xensource.com \
--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.