mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: mathieu.desnoyers@polymtl.ca
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: [PATCH 4/5] x86/paravirt: add forward-decl for task_struct
Date: Thu, 16 Apr 2009 23:39:33 -0700	[thread overview]
Message-ID: <1239950374-1252-5-git-send-email-jeremy@goop.org> (raw)
In-Reply-To: <1239950374-1252-1-git-send-email-jeremy@goop.org>

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
---
 arch/x86/include/asm/paravirt_types.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/x86/include/asm/paravirt_types.h b/arch/x86/include/asm/paravirt_types.h
index 9121aed..e174549 100644
--- a/arch/x86/include/asm/paravirt_types.h
+++ b/arch/x86/include/asm/paravirt_types.h
@@ -42,6 +42,7 @@
 
 struct page;
 struct thread_struct;
+struct task_struct;
 struct desc_ptr;
 struct tss_struct;
 struct mm_struct;
-- 
1.6.0.6


  parent reply	other threads:[~2009-04-17  6:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  6:39 [PATCH RFC] WIP pvops trace events Jeremy Fitzhardinge
2009-04-17  6:39 ` [PATCH 1/5] x86/paravirt: split paravirt definitions into paravirt_types.h Jeremy Fitzhardinge
2009-04-17  6:39 ` [PATCH 2/5] x86/pvops: add tracing for all significant pvops entrypoints Jeremy Fitzhardinge
2009-04-17  6:39 ` [PATCH 3/5] x86/paravirt: update tracing for start/end context switch Jeremy Fitzhardinge
2009-04-17  6:39 ` Jeremy Fitzhardinge [this message]
2009-04-17  6:39 ` [PATCH 5/5] x86/pvops: move tracing around to match CREATE_PVOPS_TRACE_POINTS Jeremy Fitzhardinge
2009-04-17  8:43 ` [PATCH RFC] WIP pvops trace events Ingo Molnar
2009-04-17 13:49   ` Jeremy Fitzhardinge
2009-04-17 15:55     ` Ingo Molnar

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=1239950374-1252-5-git-send-email-jeremy@goop.org \
    --to=jeremy@goop.org \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®