From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: teawater@gmail.com
Cc: dje@google.com, msnyder@vmware.com, gdb-patches@sourceware.org,
dan@codesourcery.com, mark.kettenis@xs4all.nl,
eliz@gnu.org
Subject: Re: [Fwd: Re: [RFA 3/5] Prec: x86 segment register support: target]
Date: Fri, 30 Apr 2010 09:36:00 -0000 [thread overview]
Message-ID: <201004300933.o3U9XXat025217@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <o2kdaef60381004292329l206de963ta71e7572e3de455a@mail.gmail.com> (message from Hui Zhu on Fri, 30 Apr 2010 14:29:09 +0800)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
> From: Hui Zhu <teawater@gmail.com>
> Date: Fri, 30 Apr 2010 14:29:09 +0800
>
> On Thu, Mar 25, 2010 at 10:14, Hui Zhu <teawater@gmail.com> wrote:
> > On Thu, Mar 25, 2010 at 02:44, Doug Evans <dje@google.com> wrote:
> >>
> >> On Mon, Mar 22, 2010 at 7:59 PM, Hui Zhu <teawater@gmail.com> wrote:
> >> > On Tue, Mar 23, 2010 at 02:47, Doug Evans <dje@google.com> wrote:
> >> >> On Mon, Mar 22, 2010 at 11:26 AM, Michael Snyder <msnyder@vmware.com> wrote:
> >> >>> I'd just like to point out that while all this sounds great,
> >> >>> it shouldn't be a prerequisite to the original task of just
> >> >>> getting prec to record the segments and offsets correctly.
> >> >>>
> >> >>> Maybe we should split these two tasks, so that Teawater can
> >> >>> go ahead and accomplish his.
> >> >>
> >> >> To the extent that they can be split, IWBN alright.
> >> >>
> >> >> I wonder if the interface is sufficient though (setting aside where to
> >> >> put it and how it will look).
> >> >> Any particular o/s might not provide sufficient hooks of course.
> >> >> linux's modify_ldt, AIUI, let's one change more than just foo_base.
> >> >> NativeClient http://code.google.com/p/nativeclient/ uses it, for example.
> >> >>
> >> >
> >> > Thanks Doug.
> >> >
> >> > I suggest we support segment base step by step.
> >> > When the OS that support it will show the xxx_base to user, the
> >> > unsupport OS will show nothing.
> >> >
> >> > What do you think about it?
> >>
> >> Is supporting segment base sufficient?
> >> Or do you also need to support, e.g., segment limit and flags too?
> >> There may be more, but they're the two that come to mind.
> >> [That's what I was referring to regarding whether the interface was sufficient.]
> >
> > Prec just need the base to get the insn memory operate address. Do
> > you think we need other message of segment?
> >
> > If need, do we need divide all message like eflags?
> >
> > Thanks,
> > Hui
> >
>
> Hi all,
>
> X86 looks stab now. Shall we wake up this patch?
Thanks for the reminder.
Let me first ask a question. What do people expect out of this? Do
they really want support for fully segmented code, or is it just for
small deviations like accessing per-thread storage through %fs/%gs?
next prev parent reply other threads:[~2010-04-30 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 18:26 Michael Snyder
2010-03-22 18:47 ` Doug Evans
2010-03-23 3:00 ` Hui Zhu
2010-03-24 18:44 ` Doug Evans
2010-03-25 2:14 ` Hui Zhu
2010-04-30 6:29 ` Hui Zhu
2010-04-30 9:36 ` Mark Kettenis [this message]
2010-04-30 11:07 ` Hui Zhu
2010-05-05 2:47 ` Hui Zhu
2010-05-10 2:14 ` 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=201004300933.o3U9XXat025217@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