From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch
Date: Fri, 12 Jun 2009 09:55:15 -0700 [thread overview]
Message-ID: <4A328873.4000802@goop.org> (raw)
In-Reply-To: <20090612112933.GA14930@elte.hu>
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
next prev parent reply other threads:[~2009-06-12 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 19:20 [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 1/5] x86/paravirt: split paravirt definitions into paravirt_types.h Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 2/5] x86: split out core __math_state_restore Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 3/5] x86-32: make sure clts is batched during context switch Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 4/5] x86-64: move unlazy_fpu() into lazy cpu state part of " Jeremy Fitzhardinge
2009-06-11 19:20 ` [PATCH 5/5] x86-64: move clts into batch cpu state updates when preloading fpu Jeremy Fitzhardinge
2009-06-12 11:29 ` [PATCH 0/5] x86/paravirt: clean up paravirt.h and optimise FPU context switch Ingo Molnar
2009-06-12 16:55 ` Jeremy Fitzhardinge [this message]
2009-06-12 12:37 ` Ingo Molnar
2009-06-12 16:08 ` Jeremy Fitzhardinge
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=4A328873.4000802@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/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