From: Ingo Molnar <mingo@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
David Long <dave.long@linaro.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] uprobes: preparations for arm port
Date: Thu, 7 Nov 2013 16:16:01 +0100 [thread overview]
Message-ID: <20131107151601.GA5163@gmail.com> (raw)
In-Reply-To: <20131107143432.GA6240@redhat.com>
* Oleg Nesterov <oleg@redhat.com> wrote:
> On 11/07, Ingo Molnar wrote:
> >
> > * Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > > --- a/arch/powerpc/include/asm/uprobes.h
> > > +++ b/arch/powerpc/include/asm/uprobes.h
> > > @@ -37,6 +37,7 @@ typedef ppc_opcode_t uprobe_opcode_t;
> > > struct arch_uprobe {
> > > union {
> > > u8 insn[MAX_UINSN_BYTES];
> > > + u8 ixol[MAX_UINSN_BYTES];
> > > u32 ainsn;
> > > };
> > > };
> >
> > > --- a/arch/x86/include/asm/uprobes.h
> > > +++ b/arch/x86/include/asm/uprobes.h
> > > @@ -35,7 +35,10 @@ typedef u8 uprobe_opcode_t;
> > >
> > > struct arch_uprobe {
> > > u16 fixups;
> > > - u8 insn[MAX_UINSN_BYTES];
> > > + union {
> > > + u8 insn[MAX_UINSN_BYTES];
> > > + u8 ixol[MAX_UINSN_BYTES];
> > > + };
> > > #ifdef CONFIG_X86_64
> > > unsigned long rip_rela_target_address;
> > > #endif
> >
> > Btw., at least on the surface, the powerpc and x86 definitions seem rather
> > similar, barring senseless variations. Would it make sense to generalize
> > the data structure a bit more?
>
> Heh. You know, I have another patch, see below. It was not tested yet,
> it should be splitted into 3 changes, and we need to cleanup copy_insn()
> first. I didn't sent it now because I wanted to merge the minimal
> changes which allow us to avoid the new arm arch_upobe_* hooks. And of
> course it needs the review.
>
> But in short, I do not think we should try to unify/generalize
> insn/ixol.
That's OK.
> For the moment, please ignore the patch which adds the new ->ixol
> member.
I didn't actually disagree with it so I pulled it - I was just wondering
about those cleanliness details.
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-07 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 19:19 [GIT PULL] uprobes: preparations for arm port Oleg Nesterov
2013-11-07 5:36 ` Srikar Dronamraju
2013-11-07 7:48 ` Ingo Molnar
2013-11-07 7:51 ` Ingo Molnar
2013-11-07 14:34 ` Oleg Nesterov
2013-11-07 15:16 ` Ingo Molnar [this message]
2013-11-07 16:27 ` Oleg Nesterov
2013-11-07 19:40 ` [PATCH 0/1] uprobes: Fix the memory out of bound overwrite in copy_insn() Oleg Nesterov
2013-11-07 19:40 ` [PATCH 1/1] " Oleg Nesterov
2013-11-08 16:24 ` Oleg Nesterov
2013-11-13 10:38 ` Srikar Dronamraju
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=20131107151601.GA5163@gmail.com \
--to=mingo@kernel.org \
--cc=ananth@in.ibm.com \
--cc=dave.long@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=srikar@linux.vnet.ibm.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