From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
dan@codesourcery.com, gdb-patches@sourceware.org,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: PATCH: Enable x86 XML target descriptions
Date: Mon, 22 Feb 2010 22:21:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002221421k47a298f7obe9709fa4eac7e4e@mail.gmail.com> (raw)
In-Reply-To: <4B83017D.5080002@zytor.com>
On Mon, Feb 22, 2010 at 2:13 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 02/22/2010 02:07 PM, H.J. Lu wrote:
>>
>> Oops. Wrong kernel source. The idea is the same. It is the CS.L bit
>> for 64-bit mode. That is
>>
>> /* Value of CS register:
>> 1. 64bit: 0x33.
>> 2. 32bit: 0x23.
>> */
>>
>
> That's not the CS.L bit; that's the selector value (which is currently
> the only thing exported.) The future extension should export the
> descriptor information instead of relying on fixed values.
>
Yes, for the time being, gdb checks CS value before the new
ptrace option is added to kernel. After that, gdb will be changed
to check the the CS.L bit first and fail back to CS value.
--
H.J.
next prev parent reply other threads:[~2010-02-22 22:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 20:03 H.J. Lu
2010-02-17 14:59 ` H.J. Lu
2010-02-17 15:23 ` Mark Kettenis
2010-02-17 15:42 ` H.J. Lu
2010-02-17 15:46 ` Daniel Jacobowitz
2010-02-17 16:19 ` Mark Kettenis
2010-02-18 5:44 ` H.J. Lu
2010-02-18 15:37 ` H.J. Lu
2010-02-18 23:01 ` H.J. Lu
2010-02-22 13:42 ` Mark Kettenis
2010-02-22 14:17 ` H.J. Lu
2010-02-22 15:01 ` Mark Kettenis
2010-02-22 15:27 ` H.J. Lu
2010-02-22 15:30 ` Daniel Jacobowitz
2010-02-22 15:39 ` H.J. Lu
2010-02-28 20:30 ` Mark Kettenis
2010-02-28 20:58 ` H.J. Lu
2010-02-28 22:23 ` Daniel Jacobowitz
2010-02-22 14:41 ` Daniel Jacobowitz
2010-02-22 15:34 ` H.J. Lu
2010-02-22 15:52 ` Daniel Jacobowitz
2010-02-22 15:58 ` H.J. Lu
2010-02-22 16:10 ` Daniel Jacobowitz
2010-02-22 16:58 ` Mark Kettenis
2010-02-22 17:03 ` Daniel Jacobowitz
2010-02-22 19:52 ` Mark Kettenis
2010-02-22 21:06 ` H.J. Lu
2010-02-22 21:31 ` Mark Kettenis
2010-02-22 21:41 ` H.J. Lu
2010-02-22 22:05 ` H. Peter Anvin
2010-02-22 22:07 ` H.J. Lu
2010-02-22 22:15 ` H. Peter Anvin
2010-02-22 22:21 ` H.J. Lu [this message]
2010-02-28 20:12 ` Mark Kettenis
2010-02-22 21:04 ` H.J. Lu
2010-02-28 21:16 ` H.J. Lu
2010-03-01 14:49 ` Mark Kettenis
2010-03-01 17:07 ` Daniel Jacobowitz
2010-03-01 17:09 ` H.J. Lu
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=6dc9ffc81002221421k47a298f7obe9709fa4eac7e4e@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hpa@zytor.com \
--cc=mark.kettenis@xs4all.nl \
--cc=suresh.b.siddha@intel.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