From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: patches@x86-64.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH] [5/12] x86_64: Make patching more robust, fix paravirt issue
Date: Sat, 18 Aug 2007 11:49:46 +0200 [thread overview]
Message-ID: <200708181149.48217.ak@suse.de> (raw)
In-Reply-To: <46C637B7.30200@goop.org>
> This patch breaks Xen booting.
Check the latest git head. Does it still break?
-Andi
next prev parent reply other threads:[~2007-08-18 9:50 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 12:41 [PATCH] [0/12] x86 Late merge bug fixes for 2.6.23 Andi Kleen
2007-08-09 12:41 ` [PATCH] [1/12] x86: Work around mmio config space quirk on AMD Fam10h Andi Kleen
2007-08-10 10:19 ` [patches] " Joachim Deguara
2007-08-12 9:25 ` Linus Torvalds
2007-08-12 10:03 ` Andi Kleen
2007-08-12 19:15 ` Linus Torvalds
2007-08-13 3:06 ` Dave Jones
2007-08-13 3:26 ` Linus Torvalds
2007-08-13 3:38 ` dean gaudet
2007-08-09 12:41 ` [PATCH] [2/12] x86_64: Calgary - Fix mis-handled PCI topology Andi Kleen
2007-08-09 12:41 ` [PATCH] [3/12] x86_64: Don't mark __exitcall as __cold Andi Kleen
2007-08-09 12:41 ` [PATCH] [4/12] x86_64: Disable CLFLUSH support again Andi Kleen
2007-08-09 12:54 ` [patches] " Jan Beulich
2007-08-09 13:11 ` Muli Ben-Yehuda
2007-08-09 13:12 ` Andi Kleen
2007-08-09 13:29 ` [patches] " Jan Beulich
2007-08-09 16:24 ` Muli Ben-Yehuda
2007-08-09 12:41 ` [PATCH] [5/12] x86_64: Make patching more robust, fix paravirt issue Andi Kleen
2007-08-18 0:05 ` Jeremy Fitzhardinge
2007-08-18 0:11 ` Chris Wright
2007-08-18 9:49 ` Andi Kleen [this message]
2007-08-18 20:32 ` Chris Wright
2007-08-18 20:55 ` Linus Torvalds
2007-08-18 21:31 ` Chris Wright
2007-08-18 22:28 ` [PATCH] x86: skip paravirt patching when appropriate Chris Wright
2007-08-19 3:08 ` Zachary Amsden
2007-08-19 5:55 ` Zachary Amsden
2007-08-18 21:58 ` [PATCH] [5/12] x86_64: Make patching more robust, fix paravirt issue Jeremy Fitzhardinge
2007-08-20 1:50 ` Rusty Russell
2007-08-20 2:07 ` Chris Wright
2007-08-20 6:15 ` Jeremy Fitzhardinge
2007-08-21 7:30 ` Glauber de Oliveira Costa
2007-08-21 11:23 ` Andi Kleen
2007-08-21 12:26 ` Glauber de Oliveira Costa
2007-08-09 12:41 ` [PATCH] [6/12] x86_64: Early segment setup for VT Andi Kleen
2007-10-11 21:30 ` H. Peter Anvin
2007-08-09 12:41 ` [PATCH] [7/12] x86_64: really stop MCEs during code patching Andi Kleen
2007-08-09 12:41 ` [PATCH] [8/12] x86_64: Use global flag to disable broken local apic timer on AMD CPUs Andi Kleen
2007-08-09 16:46 ` Cal Peake
2007-08-09 16:50 ` Andi Kleen
2007-08-09 12:41 ` [PATCH] [9/12] x86_64: Avoid NMI Watchdog and/or long wait in setup_APIC_timer Andi Kleen
2007-08-09 12:41 ` [PATCH] [10/12] x86_64: Add warning in Documentation that zero-page is not a stable ABI Andi Kleen
2007-08-09 12:41 ` [PATCH] [11/12] x86_64: vdso.lds in arch/x86_64/vdso/.gitignore Andi Kleen
2007-08-09 12:41 ` [PATCH] [12/12] x86_64: Fix start_kernel warning Andi Kleen
2007-08-09 13:06 ` [PATCH] [0/12] x86 Late merge bug fixes for 2.6.23 Muli Ben-Yehuda
2007-08-09 13:12 ` Andi Kleen
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=200708181149.48217.ak@suse.de \
--to=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 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.