From: "H. Peter Anvin" <hpa@zytor.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Roland McGrath <roland@redhat.com>,
Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"Lu, Hongjiu" <hongjiu.lu@intel.com>,
"Lachner, Peter" <peter.lachner@intel.com>
Subject: Re: [patch] x86: ptrace and core-dump extensions for xstate
Date: Thu, 04 Feb 2010 14:18:09 -0800 [thread overview]
Message-ID: <4B6B47A1.3050606@zytor.com> (raw)
In-Reply-To: <1265321114.2768.256.camel@sbs-t61.sc.intel.com>
On 02/04/2010 02:05 PM, Suresh Siddha wrote:
>
> So in the example you provided before:
>
> struct iovec iov = { mybuffer, mylength };
> ret = ptrace(PTRACE_GETREGSET, NT_X86_XSTATE, &iov);
>
> You wanted to propose common data format (iov) for all of the NT_* ?
>
How about encoding the regset number into the command, e.g.
ptrace(PTRACE_GETREGS(NT_X86_XSTATE), length, buffer)
... where we have ...
#define PTRACE_GETREGS(r) (((r) << 16) | PTRACE_GETREGS_CMD)
... or something like that?
-hpa
next prev parent reply other threads:[~2010-02-04 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 2:00 [patch] x86: ptrace and core-dump extensions for xstate Suresh Siddha
2010-02-02 2:33 ` [tip:x86/ptrace] " tip-bot for Suresh Siddha
2010-02-03 23:08 ` [patch] " Roland McGrath
2010-02-03 23:45 ` Lu, Hongjiu
2010-02-04 2:02 ` Roland McGrath
2010-02-04 2:05 ` Lu, Hongjiu
2010-02-04 2:16 ` Roland McGrath
2010-02-04 2:22 ` Lu, Hongjiu
2010-02-04 4:54 ` Roland McGrath
2010-02-04 5:01 ` Lu, Hongjiu
2010-02-04 5:18 ` Roland McGrath
2010-02-04 5:32 ` Lu, Hongjiu
2010-02-04 20:28 ` Suresh Siddha
2010-02-04 20:55 ` Roland McGrath
2010-02-04 22:05 ` Suresh Siddha
2010-02-04 22:18 ` H. Peter Anvin [this message]
2010-02-05 19:47 ` Lu, Hongjiu
2010-02-05 21:15 ` Roland McGrath
2010-02-05 21:39 ` Suresh Siddha
2010-02-09 17:28 ` Oleg Nesterov
2010-02-05 21:02 ` Roland McGrath
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=4B6B47A1.3050606@zytor.com \
--to=hpa@zytor.com \
--cc=hongjiu.lu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peter.lachner@intel.com \
--cc=roland@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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.