From: Michael Neuling <mikey@neuling.org>
To: Pedro Alves <palves@redhat.com>
Cc: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
avagin@openvz.org, oleg@redhat.com, linux-kernel@vger.kernel.org,
michael@ellerman.id.au, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH V2 2/3] powerpc, ptrace: Enable support for transactional memory register sets
Date: Fri, 16 May 2014 10:26:53 +1000 [thread overview]
Message-ID: <1400200013.3797.89.camel@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <5374AE24.1030302@redhat.com>
> So in sum, it very much looks like the intention is for
> PTRACE_GETREGSET/PTRACE_SETREGSET to return ENODEV in the
> case the regset doesn't exist on the running machine, and then
> it looks like at least x86 works that way.
Good point... agreed. We should ENODEV when we don't have TM hardware
(like POWER7).
Mikey
next prev parent reply other threads:[~2014-05-16 0:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:54 [PATCH V2 0/3] Add new PowerPC specific ELF core notes Anshuman Khandual
2014-05-05 7:54 ` [PATCH V2 1/3] elf: Add some new PowerPC specifc note sections Anshuman Khandual
2014-05-05 7:54 ` [PATCH V2 2/3] powerpc, ptrace: Enable support for transactional memory register sets Anshuman Khandual
2014-05-13 17:13 ` Pedro Alves
2014-05-14 5:46 ` Anshuman Khandual
2014-05-14 11:15 ` Pedro Alves
[not found] ` <CAEjGV6y8-zOtOgxcg-6viNQh-RuzQCAy8JvJ+m-dc7XQnAkJmA@mail.gmail.com>
2014-05-14 11:22 ` Pedro Alves
2014-05-15 8:25 ` Anshuman Khandual
2014-05-15 12:08 ` Pedro Alves
2014-05-16 0:26 ` Michael Neuling [this message]
2014-05-19 9:12 ` Anshuman Khandual
2014-05-19 11:46 ` Anshuman Khandual
2014-05-19 14:43 ` Pedro Alves
2014-05-20 8:14 ` Anshuman Khandual
2014-05-20 10:33 ` Pedro Alves
2014-05-22 5:08 ` Anshuman Khandual
2014-05-23 13:57 ` Anshuman Khandual
2014-05-13 17:21 ` Pedro Alves
2014-05-14 5:49 ` Anshuman Khandual
2014-05-22 5:30 ` Michael Ellerman
2014-05-05 7:54 ` [PATCH V2 3/3] powerpc, ptrace: Enable support for miscellaneous registers Anshuman Khandual
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=1400200013.3797.89.camel@ale.ozlabs.ibm.com \
--to=mikey@neuling.org \
--cc=avagin@openvz.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=palves@redhat.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
all inboxes | Powered by JetHome®