lkml.org 
[lkml]   [2009]   [May]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Where do we stand with the Xen patches?
>> Aside from some whitespace issues around some Impact: lines, I 
>> don't know of any outstanding problems. (I just pushed an updates
>> to these branches to fix those, and fold a change to address
>> Jesse's comment.)
>>
>> Please tell me if you have any further issues which prevents you
>> from pulling these changes. Otherwise I'd appreciate it if you
>> pulled them soon, as we're already on -rc5, and I have more
>> changes I'd like to prep for the next merge window.
>
>As in the past, my main worry is performance overhead of paravirt in
>general.
>
>The patches that dont affect any native kernel fast path are
>probably OK (but still pending final review).
>
>Regarding patches that do change the fastpath i'll do a round of
>measurements of CONFIG_PARAVIRT against !CONFIG_PARAVIRT kernels,
>and make up my mind based on that.
>
>You could accelerate this by sending some "perf stat" hard numbers
>to give us an idea about where we stand today.
>
> Ingo

maybe this is iust a stupid comment (please forgive, iŽm no advanced kernel
hacker), but canŽt the code inserted by the patches and which changes the
fastpath just #IFDEF`ed at the critical offsets ? (as building a dom0 kernel is
just another build target, isn`t it ?)

regards
roland
______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-05-17 20:39    [W:0.048 / U:1.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site