lkml.org 
[lkml]   [2013]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [Xen-devel] [PATCH v2 0/2] xen: vnuma introduction for pv guest
    From
    Date
    On mar, 2013-11-19 at 10:38 -0500, Konrad Rzeszutek Wilk wrote:
    > On Mon, Nov 18, 2013 at 03:25:48PM -0500, Elena Ufimtseva wrote:
    > > The patchset introduces vnuma to paravirtualized Xen guests
    > > runnning as domU.
    > > Xen subop hypercall is used to retreive vnuma topology information.
    > > Bases on the retreived topology from Xen, NUMA number of nodes,
    > > memory ranges, distance table and cpumask is being set.
    > > If initialization is incorrect, sets 'dummy' node and unsets
    > > nodemask.
    > > vNUMA topology is constructed by Xen toolstack. Xen patchset is
    > > available at https://git.gitorious.org/xenvnuma/xenvnuma.git:v3.
    >
    > Yeey!
    >
    :-)

    > One question - I know you had questions about the
    > PROT_GLOBAL | ~PAGE_PRESENT being set on PTEs that are going to
    > be harvested for AutoNUMA balancing.
    >
    > And that the hypercall to set such PTE entry disallows the
    > PROT_GLOBAL (it stripts it off)? That means that when the
    > Linux page system kicks in (as it has ~PAGE_PRESENT) the
    > Linux pagehandler won't see the PROT_GLOBAL (as it has
    > been filtered out). Which means that the AutoNUMA code won't
    > kick in.
    >
    > (see http://article.gmane.org/gmane.comp.emulators.xen.devel/174317)
    >
    > Was that problem ever answered?
    >
    I think the issue is a twofold one.

    If I remember correctly (Elena, please, correct me if I'm wrong) Elena
    was seeing _crashes_ with both vNUMA and AutoNUMA enabled for the guest.
    That's what pushed her to investigate the issue, and led to what you're
    summing up above.

    However, it appears the crash was due to something completely unrelated
    to Xen and vNUMA, was affecting baremetal too, and got fixed, which
    means the crash is now gone.

    It remains to be seen (I think) whether that also means that AutoNUMA
    works. In fact, chatting about this in Edinburgh, Elena managed to
    convince me pretty badly that we should --as part of the vNUMA support--
    do something about this, in order to make it work. At that time I
    thought we should be doing something to avoid the system to go ka-boom,
    but as I said, even now that it does not crash anymore, she was so
    persuasive that I now find it quite hard to believe that we really don't
    need to do anything. :-P

    I guess, as soon as we get the chance, we should see if this actually
    works, i.e., in addition to seeing the proper topology and not crashing,
    verify that AutoNUMA in the guest is actually doing is job.

    What do you think? Again, Elena, please chime in and explain how things
    are, if I got something wrong. :-)

    Regards,
    Dario

    --
    <<This happens because I choose it to happen!>> (Raistlin Majere)
    -----------------------------------------------------------------
    Dario Faggioli, Ph.D, http://about.me/dario.faggioli
    Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2013-11-19 20:01    [W:2.639 / U:0.220 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site