linux-kernel - Re: [PATCH] locking/pvqspinlock: Wait early if vcpu is preempted

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170105082324.GF2098@gmail.com>
Date:   Thu, 5 Jan 2017 09:23:24 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com>
Cc:     linux-kernel@...r.kernel.org, mingo@...hat.com,
        peterz@...radead.org, longman@...hat.com
Subject: Re: [PATCH] locking/pvqspinlock: Wait early if vcpu is preempted

* Pan Xinhui <xinhui.pan@...ux.vnet.ibm.com> wrote:

> If prev node is not in runnig state or its cpu is preempted, we need
> wait early in pv_wait_node. After commit "sched/core: Introduce the
> vcpu_is_preempted(cpu) interface" kernel has knowledge of one vcpu is
> running or not. So lets use it.

That's not how we reference upstream commits. I had to search the git log the hard 
way to figure out that it's commit d9345c65eb79 ...

Also, once you look at that commit you'll see how sloppy the capitalization in 
your changelog is. I fixed that up for all the original commits in the hope of you 
learning from those mistakes - but that was last year and the experiment failed.

Thanks,

	Ingo