All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	"trinity@vger.kernel.org" <trinity@vger.kernel.org>
Subject: Re: [PATCH] wire up support for the Alpha architecture
Date: Mon, 14 Oct 2013 11:46:58 -0400	[thread overview]
Message-ID: <20131014154658.GB9525@redhat.com> (raw)
In-Reply-To: <20131014154338.GL10491@mudshark.cambridge.arm.com>

On Mon, Oct 14, 2013 at 04:43:39PM +0100, Will Deacon wrote:
 > On Mon, Oct 14, 2013 at 04:39:16PM +0100, Dave Jones wrote:
 > > On Mon, Oct 14, 2013 at 04:09:52PM +0100, Will Deacon wrote:
 > > 
 > >  > Crikey, Alpha's syscall table is a right mess.
 > > 
 > > I don't know anything about alpha, but does the kernel actually
 > > implement those OSF syscalls ? If not, it's unlikely we're going to
 > > implement them in trinity, so we could probably do the same thing we did on ia64, and
 > > 
 > > #define SYSCALL_OFFSET 300 and skip all those ni_syscall entries.
 > > 
 > > Or am I missing something ?
 > 
 > Well, fork() is still syscall number 2, for example. I don't think we can
 > tidy this up with a simple offset unfortunately :(

Ah, I missed that. Now I see why you said it was a mess. Ok, I'll apply your patch as is.

thanks,

	Dave


      reply	other threads:[~2013-10-14 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 17:43 [PATCH] wire up support for the Alpha architecture Vince Weaver
2013-09-10 18:38 ` Dave Jones
2013-10-10 23:21 ` Dave Jones
2013-10-11  2:38   ` Vince Weaver
2013-10-11 11:04     ` Will Deacon
2013-10-14 15:09       ` Will Deacon
2013-10-14 15:39         ` Dave Jones
2013-10-14 15:43           ` Will Deacon
2013-10-14 15:46             ` Dave Jones [this message]

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=20131014154658.GB9525@redhat.com \
    --to=davej@redhat.com \
    --cc=trinity@vger.kernel.org \
    --cc=vincent.weaver@maine.edu \
    --cc=will.deacon@arm.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 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.