[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4A328873.4000802@goop.org>
Date: Fri, 12 Jun 2009 09:55:15 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Ingo Molnar <mingo@...e.hu>
CC: the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU
context switch
On 06/12/09 04:29, Ingo Molnar wrote:
> I havent checked all headers but do we now use the principle that we
> only include paravirt_types.h into other headers - and paravirt.h
> only into .c code that makes use of methods?
>
No, not really. The headers which currently define the native versions
of the inline functions need to include paravirt.h (as they currently
do). In fact, there are very few places which actually care about the
definitions in paravirt_types.h as opposed to the inline functions; the
main reason for the split was to do make paravirt tracing possible (but
that's not ready yet, as we haven't come to a satisfactory conclusion
about the rcu include in tracepoint.h).
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists