On 8/21/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 21, 2007 at 04:30:10AM -0300, Glauber de Oliveira Costa wrote:
> > On 8/20/07, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> > > Chris Wright wrote:
> > > > That did get backed out (at least the part that broke paravirt patching)
>
On Tue, Aug 21, 2007 at 04:30:10AM -0300, Glauber de Oliveira Costa wrote:
> On 8/20/07, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> > Chris Wright wrote:
> > > That did get backed out (at least the part that broke paravirt patching)
> > > in 602033ed5907a59ce86f709082a35be047743a86. Linus' t
On 8/20/07, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> Chris Wright wrote:
> > That did get backed out (at least the part that broke paravirt patching)
> > in 602033ed5907a59ce86f709082a35be047743a86. Linus' tree should be
> > working fine right now with d34fda4a84c18402640a1a2342d6e6d9829e6
Chris Wright wrote:
> That did get backed out (at least the part that broke paravirt patching)
> in 602033ed5907a59ce86f709082a35be047743a86. Linus' tree should be
> working fine right now with d34fda4a84c18402640a1a2342d6e6d9829e6db7
> committed, and can be further refined with the patch below th
* Rusty Russell ([EMAIL PROTECTED]) wrote:
> Then back out 19d36ccdc34f5ed444f8a6af0cbfdb6790eb1177 too, which broke
> lguest booting, and this tried to fix.
That did get backed out (at least the part that broke paravirt patching)
in 602033ed5907a59ce86f709082a35be047743a86. Linus' tree should be
On Fri, 2007-08-17 at 17:05 -0700, Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> > Commit 19d36ccdc34f5ed444f8a6af0cbfdb6790eb1177 "x86: Fix alternatives
> > and kprobes to remap write-protected kernel text" uses code which is
> > being patched for patching.
> >
> > In particular, paravirt_ops d
Andi Kleen wrote:
>> This patch breaks Xen booting.
>>
>
> Check the latest git head. Does it still break?
Yes, that's with latest git head.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
* Linus Torvalds ([EMAIL PROTECTED]) wrote:
> On Sat, 18 Aug 2007, Chris Wright wrote:
> > >
> > > Check the latest git head. Does it still break?
> >
> > Yeah, this is the latest git. The broken commit is Rusty's patch which,
> > after Linus reverted the write-protected remap changes, is no lon
On Sat, 18 Aug 2007, Chris Wright wrote:
> >
> > Check the latest git head. Does it still break?
>
> Yeah, this is the latest git. The broken commit is Rusty's patch which,
> after Linus reverted the write-protected remap changes, is no longer
> necessary. AFAICT patching is writing garbage i
* Andi Kleen ([EMAIL PROTECTED]) wrote:
> > This patch breaks Xen booting.
>
> Check the latest git head. Does it still break?
Yeah, this is the latest git. The broken commit is Rusty's patch which,
after Linus reverted the write-protected remap changes, is no longer
necessary. AFAICT patchin
> This patch breaks Xen booting.
Check the latest git head. Does it still break?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
* Jeremy Fitzhardinge ([EMAIL PROTECTED]) wrote:
> This patch breaks Xen booting. I get infinite recursive faults during
> patching when this patch is present. If I boot with
> "noreplace-paravirt" it works OK, and it works as expected if I back
> this patch out. I haven't tracked down the exact
Andi Kleen wrote:
> Commit 19d36ccdc34f5ed444f8a6af0cbfdb6790eb1177 "x86: Fix alternatives
> and kprobes to remap write-protected kernel text" uses code which is
> being patched for patching.
>
> In particular, paravirt_ops does patching in two stages: first it
> calls paravirt_ops.patch, then it f
13 matches
Mail list logo