From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"Marcin 'Qrczak' Kowalczyk" <qrczak@knm.org.pl>,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: _proxy_pda still makes linking modules fail
Date: Mon, 12 Mar 2007 16:45:58 +0100 [thread overview]
Message-ID: <20070312154558.GA16327@one.firstfloor.org> (raw)
In-Reply-To: <45F56785.5070002@goop.org>
On Mon, Mar 12, 2007 at 07:45:25AM -0700, Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> >> Rusty's pda->per_cpu patch will deal with this once and for all; have
> >>
> >
> > Not on x86-64.
> >
>
> Have you considered dropping pda in x86-64? Segment based percpu
> doesn't really have any disadvantages.
Maybe.
>
> >> you picked it up yet?
> >>
> >
> > Not yet.
> >
>
> There will be interactions with my paravirt+xen patches, so I'm
> wondering if I should rebase onto those patches, or should we apply them
> later and fix everything up?
Applying them later is probably better
-Andi
next prev parent reply other threads:[~2007-03-12 15:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 0:57 _proxy_pda still makes linking modules fail Marcin 'Qrczak' Kowalczyk
2007-03-10 15:03 ` Adrian Bunk
2007-03-11 14:06 ` Marcin 'Qrczak' Kowalczyk
2007-03-12 1:19 ` Andi Kleen
2007-03-12 0:25 ` Jeremy Fitzhardinge
2007-03-12 9:48 ` Andi Kleen
2007-03-12 14:45 ` Jeremy Fitzhardinge
2007-03-12 15:45 ` Andi Kleen [this message]
2007-03-12 21:58 ` Rusty Russell
2007-03-13 6:23 ` Rusty Russell
2007-03-13 9:04 ` Paul Mackerras
2007-03-13 15:31 ` Jeremy Fitzhardinge
2007-03-13 23:50 ` Paul Mackerras
2007-03-14 1:12 ` Rusty Russell
2007-03-13 15:57 ` Andi Kleen
2007-03-14 2:17 ` Rusty Russell
2007-03-12 18:47 ` Marcin 'Qrczak' Kowalczyk
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=20070312154558.GA16327@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qrczak@knm.org.pl \
--cc=rusty@rustcorp.com.au \
/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.