From: Eduardo Habkost <ehabkost@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, glommer@gmail.com, tglx@linutronix.de,
mingo@elte.hu, ehabkost@redhat.com, jeremy@goop.org,
avi@qumranet.com, anthony@codemonkey.ws,
virtualization@lists.linux-foundation.org, rusty@rustcorp.com.au,
ak@suse.de, chrisw@sous-sol.org, rostedt@goodmis.org,
hpa@zytor.com, zach@vmware.com, roland@redhat.com,
mtosatti@redhat.com
Subject: [PATCH 0/4] paravirt_ops-64 compile fixes
Date: Mon, 21 Jan 2008 19:48:49 -0200 [thread overview]
Message-ID: <1200952133-31581-1-git-send-email-ehabkost@redhat.com> (raw)
This series contain fixes to make the paravirt_ops code compile and boot
on x86_64.
This is a follow-up for the previous series from Glauber.
next reply other threads:[~2008-01-21 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 21:48 Eduardo Habkost [this message]
2008-01-21 21:48 ` [PATCH 1/4] Add missing semicolon to SWAPGS macro Eduardo Habkost
2008-01-21 21:48 ` [PATCH 2/4] include/asm-x86/paravirt.h: x86_64 mmu operations Eduardo Habkost
2008-01-21 21:48 ` [PATCH 3/4] Don't set pagetable_setup_{start,done} hooks on x86_64 Eduardo Habkost
2008-01-21 21:48 ` [PATCH 4/4] Fill in missing pv_mmu_ops entries for PAGETABLE_LEVELS >= 3 Eduardo Habkost
2008-01-22 12:02 ` [PATCH 0/4] paravirt_ops-64 compile fixes Ingo Molnar
2008-01-22 12:34 ` Eduardo Pereira Habkost
2008-01-22 17:55 ` Jeremy Fitzhardinge
2008-01-22 18:50 ` [PATCH 1/2] Allow enabling PARAVIRT without any guest implementation Eduardo Pereira Habkost
2008-01-22 18:52 ` [PATCH 2/2] Remove depends on X86_32 from PARAVIRT & PARAVIRT_GUEST Eduardo Pereira Habkost
2008-01-22 19:47 ` [PATCH 0/4] paravirt_ops-64 compile fixes Ingo Molnar
2008-01-22 20:05 ` 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=1200952133-31581-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=chrisw@sous-sol.org \
--cc=glommer@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).