lkml.org 
[lkml]   [2016]   [Dec]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel
    On Thu, Dec 15, Vitaly Kuznetsov wrote:

    > vmbus_wait_for_unload() may be receiving a message (not necessarily the
    > CHANNELMSG_UNLOAD_RESPONSE, we may see some other message) on the same
    > CPU it runs and in this case wrmsrl() makes sense. In other cases it
    > does nothing (neither good nor bad).

    If that other cpu has interrupts disabled it may not process a pending
    msg (the response may be stuck in the host queue?), and the loop can not
    kick the other cpus queue if a wrmsrl is just valid for the current cpu.
    If thats true, the response will not arrive in the loop.

    Olaf
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2016-12-15 14:52    [W:3.784 / U:0.160 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site