From: Davide Libenzi <davidel@xmailserver.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Zach Brown <zach.brown@oracle.com>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: [patch 12/13] signal/timer/event fds v10 - eventfd wire up x86_64 arch ...
Date: Fri, 27 Apr 2007 14:37:29 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704271436210.13605@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <20070427141941.a7891c62.akpm@linux-foundation.org>
On Fri, 27 Apr 2007, Andrew Morton wrote:
> General point: the first hunk here which wires up the 32-bit entry point
> should arguably be part of the "wire up i386" patch, not the "wire up
> x86_64" patch.
>
> This is not a clear-cut thing. The problem with the approach you've taken
> here is that if we wire up i386 and not x86_64's i386 table (for example)
> there are ways in which intervening patches can accidentally get i386 and
> x86_64 emulation's syscall tables out of sync. And, of course, 32-bit
> applications will run on i386 but won't run on x86_64 or vice-versa.
>
> So I think the best way to avoid all such problems is to always wire up
> i386 and x86_64 (both 32- and 64-bit) in the same patch.
Makes perfect sense to me. Since you've done it in -mm, I'll use your tree
as a reference from now on.
- Davide
prev parent reply other threads:[~2007-04-27 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 22:46 Davide Libenzi
2007-04-27 21:19 ` Andrew Morton
2007-04-27 21:37 ` Davide Libenzi [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=Pine.LNX.4.64.0704271436210.13605@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suparna@in.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=zach.brown@oracle.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®