From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dan@codesourcery.com
Cc: teawater@gmail.com, gdb-patches@sourceware.org, dje@google.com,
msnyder@vmware.com, eliz@gnu.org
Subject: Re: [RFA] i386 segment base support
Date: Thu, 20 May 2010 14:44:00 -0000 [thread overview]
Message-ID: <201005201439.o4KEdTqF031135@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20100520125437.GU8410@caradoc.them.org> (message from Daniel Jacobowitz on Thu, 20 May 2010 08:54:37 -0400)
> Date: Thu, 20 May 2010 08:54:37 -0400
> From: Daniel Jacobowitz <dan@codesourcery.com>
>
> On Thu, May 20, 2010 at 10:19:54AM +0200, Mark Kettenis wrote:
> > Sorry, but we still need to discuss what programming model you intend
> > to support before I will consider looking at diffs.
> >
> > Currently, on i386, GDB supports a fully flat 32-bit model, with one
> > small exception on platforms that support thread-local-storage. In
> > that model you can assume that all the segment bases are 0 except for
> > %gs. If that's all that people are interested in, I don't think we
> > should bother with segment bases for %cs, %ds, %es, %fs and %ss.
> >
> > If people want to support fully segmented memory in GDB, then what you
> > propose is probably not enough, at least not for 32-bit mode.
>
> This position confuses me. Isn't "very limited support for segmented
> memory" better than "no support for segmented memory"?
I'm not taking a position here. I'm trying to figure out what people
want out of this. If it is only about supporting TLS for Linux
userland binaries we can have a radically simpler solution than when
people want full fledged kernel-style segment register manipulating
code to work as well.
next prev parent reply other threads:[~2010-05-20 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 7:45 Hui Zhu
2010-05-20 8:40 ` Mark Kettenis
2010-05-20 12:54 ` Hui Zhu
2010-05-20 14:41 ` Daniel Jacobowitz
2010-05-20 14:44 ` Mark Kettenis [this message]
2010-05-20 15:30 ` Daniel Jacobowitz
2010-05-21 5:29 ` Hui Zhu
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=201005201439.o4KEdTqF031135@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dan@codesourcery.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox